[GUIDE] [DISCUSSION] Windows Editions Reconstructions

Q: How to reconstruct an image exactly the same as official?
Or
Q: How to reconstruct LTSC without unwanted\redundant Apps?

 

win10 updates are supporting versions as below:

<assemblyIdentity name="Microsoft-Windows-CoreCountrySpecificEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-CoreEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-CoreNEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-EnterpriseEvalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-EnterpriseGEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-EnterpriseSEvalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-EnterpriseSNEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-EnterpriseSNEvalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-PPIProEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-ProfessionalNEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-ServerAzureCorEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-ServerDatacenterACorEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-ServerDatacenterNanoEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-ServerStandardACorEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-ServerStandardNanoEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-UtilityVMEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<assemblyIdentity name="Microsoft-Windows-WinPE-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />

there is no (for example) enterprise n or education above, but every month microsoft releases mvs consumer and business isos which have (for example) enterprise n or education.

how to understand this?

 

@xinso, finally.
Use windows10.0-kb5046714-x64 license.

 

You need to login to view this posts content.

 

Yes, the license only.

 

I have no idea about WinSXSv1.

 

Yeah, it's another way. Good job. But you still don't know\get the method I mentioned to combine 22000.1 "LTSC License" and 22000.1 "AC License" in one package.

"Add" 19041 License "folder", and "Combine" 22000 AC License "package", different outcome when "sysprep" or "rearm".

 

Yes, thanks.
I'm confused about that combination.
Actually I just realized that what you meant was a combination.
What is AC? Enlighten me, please.

 

[LTSC]
EnterpriseS\EnterpriseSN\IoTEnterpriseS\IoTEnterpriseSK = Long Term Servicing Channel (5 or 10 years)

[AC]
Core\Professional = Annual Channel (24 or 30 months)

And PPIPro (Windows Team), another Channel.
And CMGE EnterpriseG? (Contracts between Microsoft and CMIT)

[Hint]
PPIPro is based on top of Enterprise. But PPIPro is not limited by AC update. It has its own update life cycle.

 

Ah, I already understand what you mean. Later it will be like a pro or enterprise license which is a collection of licenses for various SKUs. Is it really like that?

 

If you meant "Parent" and "Virtual" editions, yes.

 

What I mean by this is that in the end there will be a package containing a collection of various SKU licenses.

Spoiler: Combine Pro and EnterpriseS

<update name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-CloudEdition-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-CloudEdition-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalEducation-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalEducation-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalWorkstation-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalWorkstation-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-Education-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Education-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalCountrySpecific-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalCountrySpecific-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalSingleLanguage-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalSingleLanguage-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-ServerRdsh-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ServerRdsh-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-Professional-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Professional-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package">
<package contained="false" integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>

 

Yes. But that structure will show AC Edition IDs, not LTSC. Correct Edition ID needs both "License" and "EditionMatrix.xml" to work together.

(dism /online /get-currentedition)

[Hint]
License is controlled by "License" package.
EditionMatrix.xml is controlled by "Editions" package.
Both matched = Edition ID displayed
Both mismatched = No ID

[Hint]
It depends on "build". e.g.

Check if your 22000 LTSC would show correct Edition ID by "dism /online /get-currentedition".
I answer for you: Yes, even not matched. e.g. 22000.1 License + 22000.3260 Edition.

Check if your 22621 LTSC would show correct Edition ID by "dism /online /get-currentedition".
I answer for you: No, if not matched. e.g. 22621.1 License + 22621.4541 Edition.

 

Editions package content manifest file only.
So, we will need many specific edition packages to get the combination. Is it right?

 

Spoiler: get current and target editions

 

Patiently waitng for zwl29107's new 25398 CUs.

 

To be honest, I can't quite understand your sentences.

For WinX on 22000.1 LTSC, this is the way I use.
Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum

Code:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved.">
  <assemblyIdentity name="Microsoft-Windows-EnterpriseS-SPP-Components-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Microsoft-Windows-EnterpriseS-SPP-Components-Package" releaseType="Feature Pack">
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
  </package>
</assembly>

+

Code:

    <update name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-License-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-License-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
      </package>
    </update>

---> 22000.1 Enterprise License that supports Windows 11 WinX menu

Code:

Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-License-Package