[ARCHIVED] Windows Editions Reconstruction Project

The 17763.1 IoTEnterprise LTSC IS Enterprise LTSC. And the vNEXT one is upcoming...

 

Is there an easy way like this to make Windows 10 starter?

 

It's useless to make 19041 Starter which is not supported by updates.

 

You need to login to view this posts content.

 

No, I mean 15063 starter. I tried the first and second post, but i don't understand which of the edition files should be downloaded.

 

It is neither activatable nor supported by official updates.(too complicated for a novice.)

zhanglin is the right person for you, he is good at combo image. And he can switch any edition to any other of the combo image.

If you want mine which is single edition, updatable (offline only) and permanently activated, ask LostED if he has the copy.

 

Q: What is "Microsoft-WID-Package" shown in Server image creation processes?
A: Microsoft-Windows-Internal-Database-Package. Its Feature Name is Windows-Internal-Database.

 

Practically, you don't need re-construction script. Instead you can manually do it to a mounted image.

 

You need to login to view this posts content.

 

To do what?

 

To make an Enterprise LTSC install iso

 

"To make an Enterprise LTSC iso on boot.wim and winre.wim" does not make sense to me = I don't understand

Do you mean "To make an Enterprise LTSC iso on WinPE and WinRe environment"? If so, why?

 

You need to login to view this posts content.

 

To make a WinRE.wim to use on MSMG ToolKit_v11.2 and add it on the Windows RE Tools partition, for exemple.

 

You need to login to view this posts content.

 

I am not good at winpe\winre. Ask MSMG.

 

You need to login to view this posts content.

 

Drivers for Server 2022 Desktop Experience

Code:

Microsoft-Windows-Server-Modular-Drivers-Package~31bf3856ad364e35~amd64~~10.0.20298.1
Server-Drivers-General
Server-Drivers-Printers

Microsoft-Windows-ServerCore-Server-Common-Features-Package~31bf3856ad364e35~amd64~~10.0.20298.1
ServerCore-Drivers-General
ServerCore-Drivers-General-WOW64

 

Hi my friend,

I understand it wrong? Are you saying that IoTEnterprise LTSC is the same as Enterprise LTSC? So you use the same SKU folder?

And How do you create the System32\spp\Tokens\skus using DISM?

 

Online:
dism /online /add-package:z:\Microsoft-Windows-Security-SPP-Component-SKU-ServerDatacenter-Package~31bf3856ad364e35~amd64~~10.0.16299.15.cab

Offline:
dism /image:C:\MOUNT /add-package:z:\Microsoft-Windows-Security-SPP-Component-SKU-ServerDatacenter-Package~31bf3856ad364e35~amd64~~10.0.16299.15.cab



17763.1 does not have C:\Windows\System32\spp\Tokens\skus\IoTEnterpriseS. ONLY EnterpriseS.

i.e.

17763.1 EnterpriseS iso = C:\Windows\System32\spp\Tokens\skus\EnterpriseS
17763.1 IoTEnterpriseS iso = C:\Windows\System32\spp\Tokens\skus\EnterpriseS



One Edition (Core, Pro, etc.) is determined by these packages, EnterpriseS for example.

1.
Microsoft-Windows-Branding-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab

2.
Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab
Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~ar-SA~10.0.17763.1.cab

3.
a. 14393.0\17763.1
Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab

C:\Windows\System32\spp\Tokens\skus\EnterpriseS

b. 18362.1 onwards
Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.18362.1.cab
+
Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.18362.1.cab

C:\Windows\System32\spp\Tokens\skus\EnterpriseS
C:\Windows\System32\spp\Tokens\skus\IoTEnterpriseS

PS.
I had downloaded original 17763.1 OEM IoTEnterpriseS iso. But deleted as soon as I compared its hash. (the very same as EnterpriseS iso)