Just realized that this way may be a nice way to solve the point of this tread in a totally different way. I mean practically doing the opposite of what you did with 14357 ISO with any another windows release. In theory one can have a single iso that can install any, say 14393 windows flavor, from starter to server datacenter, w/o having to mess with multiple DISM indexes and w/o "acrobatics" needed to remove the main .mum from an already staged installation. I think I'll look in to this in the next days.
What next? Hard to say without official image. All three are Preview now. For reconstruction, 19044.x is the worst. 20348.1 is possible. But no Client. (Hence, no compatible way to port packages between Client and Server.) 22xxx.x is unknown.
There is 17784. I can't make a License package cause miss 1068 csvlk folders. And still no success editing manifests to use later versions of csvlk I have uploaded the packages of 2019 to same link couple of pages before, where 2022 are. Can put working VHD there For 20348 I surrender, after success with Turbine and TurbineCore, I can't do anything to restore ServerHyperCore With 1904x Branding for SN is a hard nut, but I hope to do it myself Status of 21390 is not clear, don't want to spend time yet. Same with 22000 Technically they are seen how to do. But the build still may change
Would be very usefull if you can teach how to solve Bluetooth in 20348. Switching to non-updatable client is not an option.
I guess (not discussed that with PMs), that it is convenient for PSS and PFEs to solve deployment problems. Also now they see potential risks and partially cut it in Win11
To save space, and to get rid of 2048 MB limit. But Microsoft does not teach us about psf. And we can not compress it into a cab greater than 2048 MB. So, my thinking is to 1. extract cab and psf to a folder 2. split the folder to multi folders. e.g. Code: Cab_1_for_KB5003188_PSFX Cab_2_for_KB5003188_PSFX Cab_3_for_KB5003188_PSFX Cab_4_for_KB5003188_PSFX 3. compress each splitted folder into one classic cab. e.g. Code: Cab_1_for_KB5003188_PSFX.cab Cab_2_for_KB5003188_PSFX.cab Cab_3_for_KB5003188_PSFX.cab Cab_4_for_KB5003188_PSFX.cab 4. create a folder in LCU name. e.g. Windows10.0-KB5003188-x64_PSFX 5. cut and paste update.mum and update.cat into Windows10.0-KB5003188-x64_PSFX 6. make cabinet.cablist.ini in Windows10.0-KB5003188-x64_PSFX cabinet.cablist.ini Code: [CabName] Cabinet1 = Cab_1_for_KB5003188_PSFX.cab Cabinet2 = Cab_2_for_KB5003188_PSFX.cab Cabinet3 = Cab_3_for_KB5003188_PSFX.cab Cabinet4 = Cab_4_for_KB5003188_PSFX.cab 7. Compress Windows10.0-KB5003188-x64_PSFX into Windows10.0-KB5003188-x64_PSFX.cab Code: cabinet.cablist.ini Cab_1_for_KB5003188_PSFX.cab Cab_2_for_KB5003188_PSFX.cab Cab_3_for_KB5003188_PSFX.cab Cab_4_for_KB5003188_PSFX.cab update.cat update.mum PS. Personaly, I prefer esd. (Because it is convenient for my frequent custom update.)
4 components needed for full 19044 21H2 EnterpriseS: 1. Microsoft-Windows-Branding-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.xxxx for ProductName Windows 10 Enterprise LTSC 202x in registry Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "CompositionEditionID"="EnterpriseS" "EditionID"="IoTEnterpriseS" "ProductName"="Windows 10 IoT Enterprise LTSC 2021" and Code: C:\ProgramData\regid.1991-06.com.microsoft\regid.1991-06.com.microsoft_Windows-10-Enterprise-LTSC-202x.swidtag 2. Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~xx-XX~10.0.19041.xxxx (for 202x License Agreement) Code: C:\Windows\System32\xx-XX\Licenses\OEM\EnterpriseS\license.rtf 3. Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.xxxx (for 19041.xxxx 32-bit Calculator) Code: C:\Windows\System32\win32calc.exe 4. C:\Windows\Branding (splitted in system core package, and language pack.) (for ProductName display to user. e.g. Windows 10 IoT Enterprise LTSC by winver.) Check upcoming LCU, and you'll see when it is ready. No need to guess.
One weird question. Q: Why 19044 EnterpriseS has Reserved Storage which is used for SAC UUP upgrade? EnterpriseS (5 years support) Product policy Code: ServicingStack-License-ReservedStorageAllowed 1 IoTEnterpriseS (10 years support) Product policy Code: ServicingStack-License-ReservedStorageAllowed 0 PS. 17763 EnterpriseS (10 years support) does not have it.
Q: Is it good to do updated image reconstruction? A: No. It won't be able to update with original LCU (based on my repeated experiments 'till now). Hint: Any reconstruction which is not with full initial packages is not able to update with original LCU from 18362 forward.
What can we do with baseless patch? The 19041.1147 one has gone from UUPdump site. The very first LCU for 19044 EnterpriseS. Anyone has got these two files to share? (I never thought it'd be removed from the site so soon and deleted them from my hdd to save space. And the extraction tool is not able to extract complete system.)