[ARCHIVED] Windows Editions Reconstruction Project

Because I don’t know "Microsoft-Windows-21H2Enablement-Payload-Package" for the time being, in order to enable 21H2, it can be changed to this.

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-21H2Enablement-Package" version="10.0.19041.1023" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Microsoft-Windows-21H2Enablement" releaseType="Feature Pack">
    <update name="Microsoft-Windows-20H2Enablement">
      <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
        <mum2:noAutoMerge />
      </mum2:customInformation>
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-20H2Enablement-Payload-Package" version="10.0.19041.843" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-21H1Enablement">
      <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
        <mum2:noAutoMerge />
      </mum2:customInformation>
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-21H1Enablement-Payload-Package" version="10.0.19041.843" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-21H2Enablement">
      <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
        <mum2:noAutoMerge />
      </mum2:customInformation>
    </update>
  </package>
</assembly>

 

Yes, I know what you meant: To install your modded package, and it is 21H2 and 19044 without the need to install those 21h2 packages manually.

Yes, those 21H2 packages install according to the registry string - Either Real or Fake:

Code:

    <update name="Microsoft-Windows-21H2Enablement">

 

Yes, the purpose of this is to learn how to enable the "not enabled" feature.

Code:

      <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
        <mum2:noAutoMerge />
      </mum2:customInformation>

Without this, 21H2 will not be enabled after installation

 

Good. But "showing" new build only, not "enabled" new Feature.

 

Windows 10 19043.1023+all 21H2 packages=19044.1023 21H2

Spoiler: Win10 21H2

No new features, just for show.

 

Differences between ThinPC and POSReady x86

Packages-ThinPC-Diff.txt (2 KB)
Packages-POSReady-Diff.txt (114 KB)

 

Good morning my friend...

What are you talking about here? MDL or NS?

 

You need to login to view this posts content.

 

Thanks you my friend I will try, and also I add it on my personal "XinsoLearning" Notepad++ file for future references...

Regards!
@JeepWillys58

 

Guys,

Just to help a novice apprentice of novice, could you tell me how you can edit the .mum file packages? Which editor do you use to see instructions for these files? I'm really stupid with that kind of thing, sorry if my questions are too basic for you, but none of us were born programmed to know everything...

Except those who were born within the mainframe Matrix like @xinso and @Tarsynear...

 

Reserved.

 

I would like to be a novice like you...someday...

 

Unfortunately no. The reason is the same as in the case of Thin PC.

 

With license switch you can use Server certs on 32-bit client Windows.

 

Reserved.

 

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.

 

Reserved.

 

You need to login to view this posts content.