edition specific 7548 xx-xx is without <applicable disposition="staged"> <detectUpdate> <parent name="Microsoft-Windows-21H2Enablement" /> </detectUpdate> </applicable>
Then you use this way: Delete four ESU packages from these two mum of the 5 ESU Editions, then save. e.g. Professional 1. Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.19041.7548.mum Code: <update name="6964de5c19c21a39bc3637741e5fecae"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Client-License-Clip-Consumer-ESU-Package" version="10.0.19041.7417" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="c091245cb2c11a3680878db141acbb38"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Client-License-Clip-Consumer-ESU-Exe-Package" version="10.0.19041.7417" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="8efe68f83098fe3c1cc4c05d601724e5"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Client-License-Clip-ESU-Package" version="10.0.19041.7548" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="c07eb1f59c3465138ab72b76b6e2a673"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Security-SPP-ExtendedSecurityUpdatesAI-Package" version="10.0.19041.7548" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> 2. Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~pl-PL~10.0.19041.7548.mum Code: <update name="27168418f839cee90c1d7e1defc58fd5"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Client-License-Clip-Consumer-ESU-Package" version="10.0.19041.6033" processorArchitecture="amd64" language="pl-PL" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="e38655e926e821890d2011664ad8168e"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Client-License-Clip-Consumer-ESU-Exe-Package" version="10.0.19041.6575" processorArchitecture="amd64" language="pl-PL" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="9fdddfa2174953968d53d6921bd5e642"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Client-License-Clip-ESU-Package" version="10.0.19041.6807" processorArchitecture="amd64" language="pl-PL" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="b4f85b52183e4f7e0a57c46736c1dfa2"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Security-SPP-ExtendedSecurityUpdatesAI-Package" version="10.0.19041.7181" processorArchitecture="amd64" language="pl-PL" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> ---> Windows10.0-KB5099539-x64-19041.7548-ESU-Disabled-by-ESU-Removal.esd PS: 5 ESU Editions 1. CoreCountrySpecific 2. Core 3. CoreN 4. Professional 5. ProfessionalN
Oh, yes. If you do Professional only, just delete them from Professional. I do 5 AC Editions, so I have to delete them from 5 AC Editions. Anyway, no matter how many Editions, we have to "expand" CU and "decompress" all files to modify. Clear.
what do you mean by decompress all files? expand is enough to modify .mum. manifest files need decompressing
As you said: manifest files need decompressing. So? Decompress is Decompress and Expand is Expand. [Best policy for Construction] Decompress package(s) and Expand all files. OK. Wish you success. Q: The two ways, both work for me. Why Way1 won't work for you? Way1: Windows10.0-KB5099539-x64-19041.7548-ESU-Disabled-by-21H2-Enablement.esd Way2: Windows10.0-KB5099539-x64-19041.7548-ESU-Disabled-by-ESU-Removal.esd I prefer Way2. The most clean.
1. Windows Update (Microsoft) won't pusy updates to "illegal" AC. 2. 5,603,128 KB? You can compare two images with and without \Resetbase. 3. See? Your own patched SSU won't work (for yourself). Would there be something wrong with your device or system? Sometimes, we have to treat Windows with Microsoft way. Let Microsoft deal with Windows for us. BTW. Don't make script with UUP links. Why? The UUP links will get invalid sooner or later. Proof? You can test 15063.0.
MUCS is based on stagesxs - not stagesxs (many files that exist in stagesxs are not required) you teached me to study sessions.xml (that's why i don't like explodesxs - exe file with no fodmetadata, no language features, no fods and visual redistributable is required)