[ARCHIVED] Windows Editions Reconstruction Project

You need to login to view this posts content.

 

You need to login to view this posts content.

 

SKUwich to client, install whatever you want, SKUwitch back to server.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

In official image, there are "Temp" folder in \Windows and \Windows\WinSxS.

Q: For Construction base image, are they both required?

 

Test Construction without both Temp folders based on #11766.

[19041.1 Windows 10 Enterprise LTSC arm64 en-US]

Code:

========================================================================================================
19041.1 Windows 10 Enterprise LTSC arm64 en-US has been successfully constructed on 2023/6/4
========================================================================================================

Mission took 0:13:42.51 (822.51s total)

They are generated by Construction.


[19041.1 Windows 10 Enterprise LTSC amd64 en-US]

Code:

No need to test because my amd64 base image does not have them.

[19041.1 Windows 10 Enterprise LTSC x86 en-US]

Code:

========================================================================================================
19041.1 Windows 10 Enterprise LTSC x86 en-US has been successfully constructed on 2023/6/4
========================================================================================================

Mission took 0:11:20.68 (680.68s total)

They are generated by Construction.


Q: What about other builds?

 

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.

 

Q: What's the leanest structure of Windows10\11?
A: Starter.

e.g. 22621 Microsoft-Windows-EditionPack-Starter-Package which is composed of two packages.

Code:

Microsoft-Windows-Desktop-BCDTemplate-Client-Package
Microsoft-Windows-NetFx4-US-OC-Package

 

xinso

Tell the whole story e.g. #11769 Embedded depends on SKUSwitch & Customized Windows11.0-KB5026443-x64-S-Next.esd

EnterpriseS & IoTEnterpriseS cannot be updated officially on Windows 11 22631.1 full stop

xinso please stop spreading misinformation by making EnterpriseS & IoTEnterpriseS look like they can be updated officially

 

You need to login to view this posts content.

 

I've never said that 22621 IoTEnterpriseS can be updated with official CU or through Windows Update. Instead, I always elaborated that custom image needs custom update.

"Customized" Windows11.0-KB5026443-x64-S-Next.esd as you quoted, isn't it?

Now that you frame what I did is misinformation, any reason for me to tell the whole story about my customized Windows11.0-KB5026443-x64-S-Next.esd? Let alone it is not " SKUSwitch", instead, it is "constructed in official structure".

 

You have made it look like 22621 IoTEnterpriseS can be updated in #11770 pic's

 

You need to login to view this posts content.

 

Post official Microsoft-Windows-EditionSpecific-EnterpriseS-Package or link for 22621

 

You need to login to view this posts content.

 

Customized Microsoft-Windows-EditionSpecific-EnterpriseS-Package & Windows11.0-KB5026443-x64-S-Next.esd

 

i missed nothing.
A noob wouldn't know the meaning of screenshot #4 .