[ARCHIVED] Windows Editions Reconstruction Project

All packages are defined in all SKU mum. e.g. Cloud:
Microsoft-Windows-CloudEdition~31bf3856ad364e35~amd64~~10.0.15063.0.mum

Code:

<?xml version='1.0' encoding='utf-8' standalone='yes'?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v3" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved." manifestVersion="1.0">
  <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-CloudEdition" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
  <package identifier="Windows Cloud Edition" releaseType="Product">
    <update name="Microsoft-Windows-Foundation-Package">
      <package contained="false" integrate="visible">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Foundation-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
    <update name="Microsoft-Windows-EditionSpecific-Cloud-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-EditionSpecific-Cloud-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
    <update name="Microsoft-Windows-Client-Features-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Client-Features-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
    <update name="Microsoft-Windows-EditionPack-Professional-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-EditionPack-Professional-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
    <update name="Microsoft-Windows-EditionPack-Professional-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-EditionPack-Professional-WOW64-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
    <update name="Microsoft-Windows-RegulatedPackages-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-RegulatedPackages-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
    <update name="Microsoft-Windows-RegulatedPackages-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-RegulatedPackages-WOW64-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
    <update name="Microsoft-Windows-Holographic-Desktop-Merged-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Holographic-Desktop-Merged-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
    <update name="Microsoft-Windows-Holographic-Desktop-Merged-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Holographic-Desktop-Merged-WOW64-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
    <update name="Microsoft-Windows-Holographic-Desktop-Analog-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Holographic-Desktop-Analog-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.15063.0"/>
      </package>
    </update>
  </package>
</assembly>

For EnterpriseS(N), it has Common-RegulatedPackages. But there is not such packages shown in UUP because it is sub-package of RegulatedPackages.


Read C:\Windows\servicing\Sessions\Sessions.xml, one from any Non-N SKU , one from any N SKU. All SKU and all SKU packages are in there.

e.g. Non-N SKU Sessions.xml

Code:

<?xml version="1.0" encoding="utf-8" ?>
<Sessions>
<Session version="8.0" id="52976_2404546765" client="DISM Package Manager Provider" options="0" currentPhase="1" lastSuccessfulState="Complete" pendingFollower="false" retry="false" Queued="2017/03/18/13:51:24" Started="2017/03/18/13:51:24" Complete="2017/03/18/14:06:36" status="0x0">
    <Tasks>
        <Phase seq="1">
            <package id="Microsoft-Windows-StarterEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows Starter Edition" targetState="Installed" options="4"/>
            <package id="Microsoft-Windows-EnterpriseEvalEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows EnterpriseEval Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-ProfessionalCountrySpecificEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows ProfessionalCountrySpecific Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-EducationEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows Education Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-ProfessionalSingleLanguageEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows ProfessionalSingleLanguage Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-ProfessionalWorkstationEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows ProfessionalWorkstation Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-CoreSingleLanguageEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows CoreSingleLanguage Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows Professional Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-EnterpriseSEvalEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows EnterpriseSEval Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows EnterpriseG Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-ProfessionalEducationEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows ProfessionalEducation Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-PPIProEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows PPIPro Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows EnterpriseS Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-CoreCountrySpecificEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows CoreCountrySpecific Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-CloudEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows Cloud Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-EnterpriseEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows Enterprise Edition" targetState="Staged" options="4"/>
            <package id="Microsoft-Windows-CoreEdition~31bf3856ad364e35~amd64~~10.0.15063.0" name="Windows Core Edition" targetState="Staged" options="4"/>
        </Phase>
    </Tasks>
    <Actions>
        <Phase seq="1" rebootRequired="false" Resolved="2017/03/18/13:55:58" Staged="2017/03/18/14:00:24" Installed="2017/03/18/14:06:36">
            <Resolve package="Microsoft-Windows-StarterEdition~31bf3856ad364e35~amd64~~10.0.15063.0" update="Microsoft-Windows-Foundation-Package"/>
            <Resolve package="Microsoft-Windows-StarterEdition~31bf3856ad364e35~amd64~~10.0.15063.0" update="Microsoft-Windows-EditionSpecific-Starter-Package"/>
            <Resolve package="Microsoft-Windows-StarterEdition~31bf3856ad364e35~amd64~~10.0.15063.0" update="Microsoft-Windows-TaskFlowDataEngine-Package"/>
            <Resolve package="Microsoft-Windows-StarterEdition~31bf3856ad364e35~amd64~~10.0.15063.0" update="Microsoft-Windows-EditionSpecific-Starter-WOW64-Package"/>
            <Resolve package="Microsoft-Windows-StarterEdition~31bf3856ad364e35~amd64~~10.0.15063.0" update="Microsoft-Windows-Client-Features-Package"/>

SKU = Edition = Core, CoreN, Professional, ProfessionalN, Enterprise, EnterpriseN, CoreCountrySpecific, PPIPro, etc.

Read it.

<Tasks> = Available SKUs Microsoft Creates, starting with Microsoft-Windows-StarterEdition.

<Actions> = SKU packages to install. e.g. Microsoft-Windows-StarterEdition.

Code:

Microsoft-Windows-Foundation-Package
Microsoft-Windows-EditionSpecific-Starter-Package
Microsoft-Windows-TaskFlowDataEngine-Package
Microsoft-Windows-EditionSpecific-Starter-WOW64-Package
Microsoft-Windows-Client-Features-Package

Q: Can I make 15063 CoreConnected Edition with 10537 CoreConnected packages?
A: No. 15063 does not support CoreConnected.

PS:
Program packages, maybe compatible. SKU Certificates? No, different SPP service.

Fact:
Microsoft changes SPP service for each and every LTS.

10240\10586
-------------------------------------------------------
14393\15063\16299\17134
-------------------------------------------------------
17763\18362\18363\19041\19042\19043\19044.1149 (17763 LTSC SPP)
-------------------------------------------------------
19044.1200 (19044 LTSC SPP)\20348\22000

So,

InCompatible = Impossible:
10240 with 10537 packages.
19044 with 15063 Starter packages.

Compatible = Possible:
14393\16299\17134 with 15063 Starter packages.
20348\22000 with 19044.1200 LTSC packages.
and
18362 with 17763 or 19044.1149 LTSC packages.

You have to clarify aforementioned before you can do correct reconstructions.

 

Learn to make "dism /online /get-currentedition" show correct quick-switch Edition ID is more useful.

 

Odd it doesn't match what I observed using my quick switch method

According to what I remember certs are compatible as follows...

10240\10586
-------------------------------------------------------
14393\15063\16299
-------------------------------------------------------
17134\17763\18362\18363
-------------------------------------------------------
\19041\19042\19043\19044\20348\22000

 

You need to login to view this posts content.

 

I struggle to think of anything more useless, meaningless and harmful.

This is "Edition Reconstruction", not "Edition Renaming, Fakery and Frankenbuild General".
What edition do you reconstruct by swapping cerrificates and breaking CBS? This isn't the point of this thread.
OP would be disappointed.

 

You need to login to view this posts content.

 

While I not always agree with all is done here, I'm sure I have to disagree with what are you writing

Useless/meaningless ? Knowledge is never useless, but aside that there are many combinations that are REALLY very useful.

Say AZURE HCI + DC packages. There isn't a single official Core /aCor version that have wireless support while being capable of acting as a Domain controller.

Just an example but I can continue for a day

Harmful? Harmful to what? The worst you can face is wasting a bit of time...

Don't mix quick switch and reconstruction.

Quick switch (my method) breaks nothing, OP/Xinso's Method may break something depending on the combination, personally I can't see that as a big problem as long as yo are aware of it.

OP is not with us anymore, I can't speak for him, you shouldn't as well.

But even if he was still with us, his opinion would be an opinion, being the OP is not being the constitutional court.

 

There may be a way to patch ci.dll and remove signature verification of packages

 

Spoiler

 

Thank you for your teaching.

But that post of mine is for those persons who modify basebrd.dll.mui's Product Name for another SKU.

Please don't reply. I have new 19044.1415 CMGE to research which is more meaningful to me.

 

But for new update technology, it's gonna stop psfx LCU from updating.

 

Q: How to revert 19044.1415 CMGE to 19041.1?

PS:
This build has been Resetbase.

 

Useless and meaningless in the context of this thread.
No matter what, it still isn't recovering/reconstructing anything, which is the point of this thread.

If anything, it's undermining what this thread has achieved.
"Your method doesn't work? Just move around some certificates until the system is confused enough to think it works."

"It's not bad. Even if, it's not THAT bad. And if it is so bad, obviously we all know already!"
The problem is that no one outside of this thread knows.
Some will sell it as a miracle cure to all incompetent CBS manipulation (and some already have).

Knowledge is good, but mere scraps of it strewn around a thread this size isn't "knowledge", it's rambling and someone is bound to misunderstand and take it out of context.

That's exactly what I'm saying.

 

You need to login to view this posts content.

 

compare another 19044.1415 image (not reseted) to the same reseted image, record file and registry differences and import to cmge image, delete the update

 

patch the ci.dll in another system like WindowsPE, use offline update

 

OK. Just take it easy.

 

What I think is get the mum sku and then reconstruction with abbodi template script.

 

Thank you. But we need its original OEM settings.