Adding these EnterpriseS packages, Registry entries and sku Then I "set-productkey" I am able to set Pro to EnterpriseS edition using Code: dism /scratchdir:temp /image:mount /set-edition:EnterpriseS Windows update works
Yes, your own style. Congrats. But I am curious why you add those registry which will be added when the packages were installed? It seems that you did not set Product for EnterpriseS. Under such a case, it won't update EnterpriseS. Have you checked it is 19044.1149?
This is the script of spoiler #3 Code: @echo off dism /online /get-currentedition echo. echo. echo. echo. echo.Activation expiration date is: echo. cscript /Nologo "C:\Windows\System32\slmgr.vbs" /xpr echo. echo. echo. pause
Reconstructed 19041.1 EnterpriseS updated with original 19044.1149 updates 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.19044.1149 Current edition is: Current Edition : EnterpriseS The operation completed successfully. C:\windows\system32>dism /English /image:K: /get-targeteditions Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.1149 Editions that can be upgraded to: Target Edition : IoTEnterpriseS The operation completed successfully. C:\windows\system32>
Q: What are the packages we are in short of for perfect 19044 21H2 LTSC ATM? A: Two small packages. 1. Win32Calc package - 32-bit Calculator 2. Branding package - defines CompositionEditionID\EditionID\ProductName e.g. CompositionEditionID = EnterpriseS (Parent SKU) EditionID = EnterpriseS (Virtual SKU) ProductName = Windows 10 Enterprise LTSC 2019 (17763.1)