[ARCHIVED] Windows Editions Reconstruction Project

wimlib-imagex info install.wim 1

Code:

Information for Image 1
-----------------------
Index:                  1
Name:                   Windows 10
Description:            Windows 10
Directory Count:        19077
File Count:             93710
Total Bytes:            16055407604
Hard Link Bytes:        7005478091
Creation Time:          Wed May 12 18:24:22 2021 UTC
Last Modification Time: Fri May 14 17:10:40 2021 UTC
Architecture:           x86_64
Product Name:           Microsoft?Windows?Operating System
Edition ID:             Core
Installation Type:      Client
Product Type:           WinNT
Product Suite:          Terminal Server
Languages:              xx-XX
Default Language:       xx-XX
System Root:            WINDOWS
Major Version:          10
Minor Version:          0
Build:                  21382
Service Pack Build:     1
Service Pack Level:     0
Flags:                  Core
WIMBoot compatible:     no

Q: Which is more reliable about "Edition idetification" of official install.wim?

Edition ID: Core

Code:

for /f "tokens=3 delims=: " %%x in ('files\wimlib-imagex info install.wim 1 ^| findstr /i /C:"Edition ID"') do (set SOURCE=%%x)

or

Flags: Core

Code:

for /f "tokens=2 delims=: " %%x in ('files\wimlib-imagex info install.wim 1 ^| findstr /i /C:"Flags"') do (set SOURCE=%%x)

 

Fact:
Core is allowed to upgrade in place to other higher editions from within itself. Which means what? There are more than one editions in the image.

Q: Core is the smallest image?
A: No. On the contrary, Core is the biggest image among all editions. And the older build, the more editions, the bigger.


PS,
In reality, Core for China is the biggest.

 

This is 15063 Windows 10 S image

dism /english /image:Z:\1 /get-currentedition

Code:

C:\WINDOWS\system32>dism /english /image:Z:\1 /get-currentedition

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.15063.0

Current edition is:

Current Edition : Cloud

The operation completed successfully.

Q: Which way is the most reliable to check which editions are existent in an image?

this command?

dism /english /image:Z:\1 /get-targeteditions

Code:

C:\WINDOWS\system32>dism /english /image:Z:\1 /get-targeteditions

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.15063.0

Editions that can be upgraded to:

Target Edition : Education
Target Edition : Enterprise
Target Edition : ProfessionalEducation
Target Edition : Professional

The operation completed successfully.

Fact:
Aforementioned command shows only the default Target editions for the Sourse edition. There may be other edition(s) for some Target edition to upgrade.

Here is my Never-Go-Wrong method: I check "Microsoft-Windows-Editions-BlaBlaBla-Package"

e.g. 15063 Windows 10 S amd64

Code:

Microsoft-Windows-Editions-Cloud-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
Microsoft-Windows-Editions-Education-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
Microsoft-Windows-Editions-Enterprise-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
Microsoft-Windows-Editions-EnterpriseG-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
Microsoft-Windows-Editions-Professional-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
Microsoft-Windows-Editions-ProfessionalEducation-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum

At last, I know what to remove for a Standalone 15063 Windows 10 S:

To remove these 5 editions, NOT 4.

Code:

Microsoft-Windows-Editions-Education-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
Microsoft-Windows-Editions-Enterprise-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
Microsoft-Windows-Editions-EnterpriseG-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
Microsoft-Windows-Editions-Professional-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
Microsoft-Windows-Editions-ProfessionalEducation-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum

 

What is targeteditions? Ultimately decided by EditionMatrix.xml.

 

Thanks. Good finding.

But it is good for static knowledge only. Not enough for dynamic auto-detection of an image.

 

Code:

<update name="Microsoft-Windows-ServerCore-WOW64-Package">
      <selectable disposition="absent">
        <detectNone default="true" />
      </selectable>
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-ServerCore-WOW64-Package" version="10.0.x.x" processorArchitecture="xxx" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-ServerCore-WOW64-Payload-Package">
      <selectable disposition="absent">
        <detectNone default="true" />
      </selectable>
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-ServerCore-WOW64-Payload-Package" version="10.0.x.x" processorArchitecture="xxx" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>

I don’t understand more and more, what is the purpose of adding these?
<selectable disposition="absent">
<detectNone default="true" />
</selectable>
It turned out to be like this, and I didn't find any use.

 

<selectable disposition="absent"> --> shown on Roles and Features menu

Code:

absent = No
staged = yes (Selectable)

<detectNone default="true" /> --> Enabled or Disabled

Code:

true = Enabled
false = Disabled

 

As I understand it, this position has nothing to do with Features. For example, the correct interpretation of the Features ServerCore-WOW64 is shown in the figure:

 

You have to research the very true relationship between them.

 

Don’t you feel similar to this one? When removing the shadow part

 

I have no comment on unknown things.

Besides that, don't you think they are different?

 

The network is unstable and keeps dropping. good night.

 

Microsoft-Windows-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~10.0.20344.1 (15 KB)
Microsoft-Windows-ServerCore-WOW64-Payload-Package~31bf3856ad364e35~amd64~~10.0.20344.1 (164 MB)

Microsoft does not define their relationship in the former as usual. Instead, Microsoft defines it in the latter.

 

Good night.

 

Reserved.

 

i tested out the 10s 15063 in vmware just for fun. ran the update and went to a new build. it did not change to 10 s mode why?

 

Congrats.

But, relax, no one can open it without your Crystal Ball.

 

Reserved.

 

Q: What is the difference between old and new update technology?
A:

old, target package
new, use new mum and PSFX format to prevent user from tampering package

 

Reserved.