[GUIDE] [DISCUSSION] Windows Editions Reconstructions

so long without new experimental build - maybe this week...

 

intcssdw (sl8 intel audio driver) by dependencies on 226xx where audio works

 

Can you post the link to download Bedi script v7.44? Thank you.

 

W7W10, link to download Bedi script v7.44: forums.mydigitallife.net/posts/1899336
Thanks to Ace2.

 

intcssdw (sl8 intel audio driver) by dependencies on 1904x where audio doesn't work



comparing to 226xx runlevels and globmerger not on the list

 

Is there any event log error of this driver on 19041?

 

code 37



Device INTELAUDIO\CTLR_DEV_E428&LINKTYPE_05&DEVTYPE_05&VEN_8086&DEV_AE35&SUBSYS_308810EC&REV_0001\5&2c9025ed&0&0500DIF_000B&UIF_0001 had a problem starting.

Driver Name: oem37.inf
Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}
Service: IntcSSdw
Lower Filters:
Upper Filters:
Problem: 0x25
Problem Status: 0xC000000D

 

Check eventvwr or smth to find the full log

 

You need to login to view this posts content.

 

Windows 11 EnterpriseS 28000.2525 multilang 38
To get the link, send a message only.

size gb 2,5 28000.2525-milti-s.esd (mode recovery)

Defender, WebViewer, and WinRE are removed.

Notepad, MS Paint, PowerShell, SnippingTool, and VBScript are included.

The default SKU is en-us; you can change it via Windows or DISM.

 

on 226xx same errors in event viewer as https://forums.mydigitallife.net/th...s-reconstructions.88605/page-277#post-1917070, but audio works (so the problem lies elsewhere)

 

[20348.5386 Windows Server 2022 Datacenter Azure Edition (Desktop Experience) amd64 en-US]

Code:

------------------------------------------------------------
Set ServerTurbine key
------------------------------------------------------------

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.20348.5386

Starting to install product key...
Finished installing product key.

The operation completed successfully.

============================================================
Current Edition : ServerTurbine (VOLUME_KMSCLIENT)
============================================================

[20348.5386 Windows Server 2022 Datacenter Azure Edition amd64 en-US]

Code:

------------------------------------------------------------
Add Cumulative Update to ServerTurbineCor image
------------------------------------------------------------

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.20348.1

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.5386.1.25
[==========================100.0%==========================]
An error occurred - Package_for_RollupFix Error: 0x8007000d

Error: 13

The data is invalid.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

Q: Why?
A:

Code:

2026-07-22 16:55:59, Error                 CBS    Failed to stage execution package: Microsoft-Client-License-Flexible-Platform-Package~31bf3856ad364e35~amd64~zh-TW~10.0.20348.4893 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

--->
Microsoft-Windows-EditionPack-ServerTurbine-Package~31bf3856ad364e35~amd64~~10.0.20348.1.mum

Code:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved.">
  <assemblyIdentity name="Microsoft-Windows-EditionPack-ServerTurbine-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Microsoft-Windows-EditionPack-ServerTurbine" releaseType="Feature Pack">
    <update name="4832186a011c87c693169e239e0d998c">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Hotpatch-Payload-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="83c05787b3cf97dd4cec091eddff7f1b">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Hotpatch-Utility-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
  </package>
</assembly>

Microsoft-Windows-EditionPack-ServerTurbine-Package~31bf3856ad364e35~amd64~~10.0.20348.5386.mum

Code:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved.">
  <assemblyIdentity name="Microsoft-Windows-EditionPack-ServerTurbine-Package" version="10.0.20348.5386" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Microsoft-Windows-EditionPack-ServerTurbine" releaseType="Feature Pack">
    <update name="09425fc3eb9e392e379df5fd66702fd3">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Client-License-Flexible-Platform-Package" version="10.0.20348.5386" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
  </package>
</assembly>

 

Ever since MulanG came into our lives, everything has become easier.

MulanG with ko-KR

Spoiler

 

The same thing happened with my EntGN (19041). I tried various combinations of expand.exe, msdelta, dpx, and mspatcha versions, but it still failed. I have absolutely no idea what went wrong.

 

You have to add "EnterpriseGN" to related mum. e.g.
1. Update mum
2. Wrapper mum
3. Language pack mum

 

1 & 2, Done.
Number 3, it is already exist ini languagepack mum

Code:

    <update name="Microsoft-Windows-Editions-EnterpriseGN-Package">
      <package contained="true" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Editions-EnterpriseGN-Package" version="10.0.19041.7548" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>

 

https://forums.mydigitallife.net/th...s-reconstructions.88605/page-272#post-1915849

 

That's right. Using the June update patch worked well, but with the current update, it doesn't work at all.

 

Is it possible to have a normal OOBE with (without unattended) enterpriseG 28000.1?