Try on VMware to learn and make yourself familiar with it before going further step. 17763 is more easy for Windows Update. 17763 --> old update technology --> checking package only 20348 --> new update technology --> install new mum and update by new mum structure, plus PSFX update.
I made it. There're just a few quirks: Windows Edition name is empty when it's supposed to say "Windows 10 Professional" or "Windows Server 2022 Datacenter" Server Manager is not removed, but it's corrupted. It's unstable just like early Insider Preview builds. When I enable desktop watermark, it only says "Build 20348.fe_release.201507-1500", no Operating System name. No winver branding, as you said. It's worth trying on a VM. But I don't think it can be used as a daily Operating System.
Yes, it's coming. Please wait, it won't be long... You can start with OP's 19041.1 EnterpriseG which is available in both en-US and zh-CN. 22000 and 224xx (atm) is in same SKU structure as 19041. Easy to learn reconstruction. I can help with this EnterpriseG. As for 22000 LTSC, sorry, no, because it needs custom update.
Please explain more. Are you referring to using a Baseless LCU on the converted Windows Server 2022 to Windows 10 project or does your statement refer to any reconstructed build? Are you saying that once you use a baseless update, regular Windows Update (original updates) never works correctly again?
Is it possible to extract an installable x64 calculator cabinate (.cab) from your LTSC official build? Doesn't matter what language.
Based on my experiments, the baseless LCU makes the system more complicated and hence lesser possiblility to be original state, i.e. lesser possibility for a system to be supported by original LCU or Windows Update.
Thank you! That is very clear. The "'#4865 - Windows 10 Enterprise IoT vNext Client Edition Reconstruction Project" is created by using a baseless LCU. Question 1: Is there any hope for this project? The above project uses an adapted 17763.1 Win32Calc. My experiments in trying to apply Windows Update seems to show that the version of the adapted 17763.1 Win32Calc I have is what's stopping the original LCU. Question 2: Would you be able to supply a more skillfully created (better version) of the 17763.1 Win32Calc adapted to allow the above project to work with original LCU?
A1: I am not sure because I don't have it. But it seems not in Microsoft way. A2: Just use the 17763.1-based 19041.1 neutral package provided by the provider. And the client lanuage pack will install its appropriate language pack automatically while reconstruction.
To determine whether or not a reconstruction is accepted by Windows Update, now I learn to use "sfc /scannow". If no integrity violation found, yes. This 20348.1 ServerTurbine reconstruction with one 20348.51 package is fully supported by Windows Update. Code: Microsoft-Windows-Editions-ServerTurbine-Package~31bf3856ad364e35~amd64~~10.0.20348.51 The sfc /scannow should go 1, 2, .... , 99, 100% steadily and smoothly until no integrity violation found. Hint: You can use 20348.1 ServerDatacenter to test, because there are not many LCUs now. e.g. 17763.1 Win32Calc package for 20348.1 one, there is 20348.143 Win32Calc update. Code: Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.20348.143
EnterpriseG is made exclusively for zh-CN CMGE, never public release. CMGE_V0-G.1013.001_DELL.iso = 15063.0 (SAC) 16299.15 CMGE_V0-H.1020.iso = 17134.1 (SAC) CMGE_V2020-L.1207.iso = 17763.1 (LTSC, for EnterpriseS, not necessarily for EnterpriseG.) 18362 18363 19041 19042 19043 19044 (LTSC Client only) 20348 (LTSC Server only) 22000 (AC) vNext CMGE, 19044 or Windows 11?
Wow, on Server 2022 Datacenter Azure Edition with Desktop Experience, the Edge browsing MDL makes it up to 4.7 GB memory consumption. Idling without Edge: 4.4 GB OK. The 20348.1 ServerTurbine 2022 reconstruction with a 20348.51 package is fully accepted by Windows Update since 20348.75. PS: I use 20348.1 Certificates for KMS activation. So, (in case the LCU has update for the Certificates,) before runnung Windows Update, I have to revert the original Certificates which disable activation on non-Azure devices. Code: C:\windows\system32>dir /b I:\Windows\System32\spp\tokens\skus csvlk-pack ServerTurbine These two stored elsewhere. ServerTurbine-Activated (20348.1) ServerTurbine-Backup (Latest) Q: How to skip the non-existent package for a successful reconstruction of ServerTurbine 2022? I once shared the script, if you missed it, here is how-to: Microsoft-Windows-EditionPack-ServerTurbine-Package~31bf3856ad364e35~amd64~~10.0.20348.1.mum Original (not able to reconstruct) 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="ff2ba25614aabd08f1cd58b72ec16273"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Hotpatch-Targeting-Gated-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> Modified (able to reconstruct) 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> Before unmounting the image, I use this command line to revert it: Code: copy /y files\mum\*EditionPack-ServerTurbine*.mum %MT%\Windows\servicing\Packages >NUL 2>&1 If not reverted, Windows Update may fail.