[ARCHIVED] Windows Editions Reconstruction Project

You need to login to view this posts content.

 

Does this help you?

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v EditionSubManufacturer /t REG_SZ /d "xxxx" /f | Out-Null​

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

no modification required if you use mas 2.5
for ltsc 2024 / iot ltsc 2024

=> the two sku support GVLK

but better are iot longuer update

 

Officially, yes. But... update's target is IoT's "Parent", i.e. "Microsoft-Windows-EnterpriseSEdition". So, unless each edition is standalone, or EnterpriseS' activation is banned at EoS.

 

yes because iot and K variant are virtual sku

 

Can you do 2024-EnterpriseS HWID Digital Activation? Not KMS.

 

nope enterpriseS need valid retail key or mak key

for activation only standard kms or kms38 ( aka 2038 )

FYI for server 2025 ( standard kms or kms38 or permanant activation slic 2.7 use ezwindslic )

for moment slic 2.7 certificate not avaible

 

You need to login to view this posts content.

 

I remember you said that 2021EnterpriseS can add 2019EnterpriseS OEM files to achieve digital activation, it takes too long, I can't remember how to do it?

 

Yes and No.

 

That is to say, the SPP version must be within 190xx.1149.

 

Yes, it must be activated as of 19041.1149. But Spp is controlled by System, leave it alone.

Look back and follow carefully.

 

KEY:17763 or 19041?

17763 OEM:NONSLP
19041 Volume:MAK

25941.1000 EnterpriseS

Spoiler

 

You need to login to view this posts content.