OK. Now I see the difference between Windows11.0-kb5037898-x64-26120 Ge-Client-Server-Beta-Version-Enablement.cab and Enablement-Packages . If I install the Beta-enablement, I may face a problem with non-beta CUs, as they don't mention my Beta EditionPack If I don't use Beta-enablement, I can install both Stable and Beta CUs. Right? For EnterpriseSN I wasn't able to find any script for 26100, but I am not a big fan of N also ) Am a server guy, updatable Datacenter Full for AC builds is what I am really interested in/
A1. No. Don't install Preview\Beta CUs on LTSC. The issue is brought by 26120.712\750 "Preview\Beta CU" on all N editions, nothing to do with 26120 Enablement kb5037898. Rule for LTSC Update: Patch Tuesday. A2: I don't do it anymore.
Crystal clear now! If I made a mistake and installed preview for LTSC, I wait till next Patch Tuesday, update and forget about the problem.
Test 25398.887 update on reconstructed 25398.1 Windows 11 Enterprise amd64 en-US Code: ======================================================================================================== 25398.1 Windows 11 Enterprise (OEM_NONSLP with Edge with Store with NetFx3) amd64 en-US has been successfully reconstructed on 2024/6/8 ======================================================================================================== Mission took 0:20:19.27 (1219.27s total) [official Windows11.0-KB5037781-x64.msu] Code: C:\WINDOWS\system32>dism /english /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Current edition is: Current Edition : Enterprise The operation completed successfully. C:\WINDOWS\system32>dism /english /image:K: /add-package:z:\Windows11.0-KB5037781-x64.msu Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - [==========================100.0%==========================] [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /english /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.887 Current edition is: Current Edition : Enterprise The operation completed successfully. C:\WINDOWS\system32> [zwl29107 KB5037781-x64.esd] Code: C:\WINDOWS\system32>dism /english /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Current edition is: Current Edition : Enterprise The operation completed successfully. C:\WINDOWS\system32>dism /english /image:K: /add-package:z:\1 Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 2 - Adding package Package_for_ServicingStack_880~31bf3856ad364e35~amd64~~25398.880.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_880 requires the current servicing session to be reloaded. All the packages will be processed again. Processing 1 of 2 - Adding package Package_for_ServicingStack_880~31bf3856ad364e35~amd64~~25398.880.1.0 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.887.1.8 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /english /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.887 Current edition is: Current Edition : Enterprise The operation completed successfully. C:\WINDOWS\system32> [Credits] gailium119 zwl29107
Teacher @xinso - I need some advice When you click on "Turn windows features on or off" in Programs and Features - a pop-up will then display the features - which package/s is needed for this pop-up to work : maybe its something in the registry ? Many thanks
Client: Windows Feafures (OptionalFeatures.exe) Server Desktop Experience: Roles and Features (ServerManager.exe) It is controlled by appwiz.cpl. Then, by installation type, call either Client's OptionalFeatures.exe or Server Desktop's ServerManager.exe. Server Core + Client, lacking ServerManager. It can be achieved by Way 1: Install ServerManager Fod from UUP to use ServerManager. Way 2: Modify appwiz.cpl, OptionalFeatures.exe, and ServerManager.exe to redirect ServerManager shortcut links to OptionalFeatures.exe. PS: 1. On such a system, the easiest way to control Features is command line. 2. Installation Type, Client or Server. Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "InstallationType"="Client"
Server Core + Microsoft-Windows-Server-DesktopUX-Package = barebone Server Desktop Experience. For Server Core + Media features, check and install those Media Fetures dependencies and programs in Microsoft-Windows-Server-DesktopUX-Package (if they are not difined in manifest. If defined in manifest, no way.) If from Client, perhaps in these packages. Code: <update name="Microsoft-Windows-Client-Desktop-Required-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Client-Features-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Features-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Client-Features-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Features-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionPack-Core-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionPack-Core-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionPack-Core-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionPack-Core-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-RegulatedPackages-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-RegulatedPackages-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> Dependencies matter. Hard to separate. Microsoft places anything Microsoft does not want users to tamper in deployment manifest. Unless you know how to extract specific components and add by hand. The old Win7Lite component extractor has failed on the latest build. (I had deleted it, no way to show you.) You can check Media related packages from 10240\10586\14393, they are in Windows 8.1 structures. e.g. Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia~31bf3856ad364e35~amd64~~10.0.10240.16384.mum
In the past I've tried adding Microsoft-Windows-Server-DesktopUX-Package with sxsv2bugfixed but the package ends up being larger than the cab file limits and fails. Any suggestions or directions I'd really appreciate it. I've done the original guide but it's hard to tell what the best way(s) to do reconstruction are. I know it's lazy of me to not go through all 800+ pages to find the answer myself. But I am willing to follow directions by the one who seems to know all the ways Just saw your edit. Thanks for the guidance I'm going to give it a shot now I'll let you know how it goes.
You'd better go to LiteOS' "Server Core + GUI" thread. You don't need to install all packages in Server-DesktopUX-Package. You have to test by yourself until it works without GUI. I remember there is "Windows PE as AUDIO OS". Check it out. [Hint] Server-DesktopUX-Package = Client LTSC barebone. So, lots of them are useless to your purpose.