[GUIDE] [DISCUSSION] Windows Editions Reconstructions

thanks for hint

 

thanks again

 

replying again to have copy

 

where did you get official 26100.1 enterprise sn iso from?

 

Official Microsoft-Windows-EnterpriseSNEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum from .1742 iso?

 

For 26100.1 EnterpriseSN?

Two ways:
2-1: iamaHUN's 26100.1 packages reverted from 26100.XXXX.
2-2: 26100.1742 packages patched as 26100.1.

Third way?
Ask gailium(119) or zwl(29107) to repack.

 

thanks, i'll try

 

dism in 26100 is not suggesting (like in 19041) missing files to add packages successfully. will dism++ do that?

nevermind, i've made it

 

everything works now

 

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.

 

Just an easy question too. If i have a working "Microsoft-Windows-EditionSpecific-EnterpriseG-Package.esd" package how can i change professional install.wim to enterpriseG? Just adding specific package does not adds edition. I have looked IamaHun scripts he can easy build EnterpriseG just with specific packages but could not understand what he does from his scripts. Also we need an edition package. I do not want a script. Just want to know how to.

 

Microsoft-Windows-EditionSpecific-EnterpriseG-Package.esd doesn't contain Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum, you have to create it yourself. Check the first LCU, which is 26100.2. It contains Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.2.mum, replace every .2 value to .1 in it, then also rename the mum file accordingly. After this you have to compare the mum with Sessions.xml to make sure it doesn't contain any unnecessary packages.

This is the content of the mum:

Spoiler: Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.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-EnterpriseGEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Windows EnterpriseG Edition" releaseType="Product">
    <update name="Microsoft-Windows-Foundation-Package">
      <package contained="false" integrate="visible">
        <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-EditionSpecific-EnterpriseG-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-EditionSpecific-EnterpriseG-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Client-Desktop-Required-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Win4-Feature">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Win4-Feature" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Win4-WOW64-Feature">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Win4-WOW64-Feature" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Client-Features-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Client-Features-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Client-Features-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Client-Features-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-EditionPack-Professional-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-EditionPack-Professional-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-RegulatedPackages-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-RegulatedPackages-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
  </package>
</assembly>

And you have to find the related part in Sessions.xml:

Spoiler: EnterpriseGEdition in Sessions.xml

Code:

<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-Foundation-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-EditionSpecific-EnterpriseG-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-Client-Desktop-Required-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-Client-Desktop-Required-WOW64-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Win4-Feature"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Win4-WOW64-Feature"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-Client-Features-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-Client-Features-WOW64-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-EditionPack-Professional-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-EditionPack-Professional-WOW64-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-RegulatedPackages-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-RegulatedPackages-WOW64-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-Required-ShellExperiences-Desktop-Package"/>
<Resolve package="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1" update="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package"/>

If the package count and order matches in your mum file with this part of Sessions.xml, you've successfully re-created the edition package for EnterpriseG. Now create a new empty txt file and give it the same name as your mum, but modify the extension to .cat. You don't have to sign it or anything, because edition packages contain subpackages only, and Windows won't check the hashes in the cat file.

After this you can create an unattended XML file to switch editions. You have nothing to do with EditionSpecific package, just extract the content of the ESD file to the same folder where you have the mum and cat to the edition package.

 

I think i understand. You create or take from packages folder only edition pack cat and mum and apply with 1.xml from extracted folder.

Is there any difference experienced that edition mum and sessions xml did not matched? I think normally do not. Just like enterprisesn eval package missing some, at upper topics.

You are saying mum and session.xml match just for edition.mum isnt it. We never need extra package files for an edition else than specific package files?

If i combine edition specific files and edition .cat and .mum in an edition.esd and apply will it work? I will test tomorrow. Thanks for explanation.
Edit: It not works. I think one of it "Feature Pack" other is "Product". Product can not installed as cab or esd.
<package identifier="Windows EnterpriseS Edition" releaseType="Product">
<package identifier="Microsoft-Windows-EditionSpecific-EnterpriseS" releaseType="Feature Pack">

How uupdump downloader creates isos. Extracting specific esds? Creates edition .cats .mum. Applying it? It does not look working that way. So much code inside it for to explore. Maybe that editions not implemented yet. Just builds core and professional and their virtual variants. It does not build Enterpriseg

 

Hello. Please help.
Where download
Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.20348.143.cab file (xinso repacked).
Or
Export ISO file?
Thaks.

 

You need to login to view this posts content.

 

i just used "MSU_to_esd_and_Modded_CU_202311242121". Expanded 26100.2 and 26100.3 update packages just fine.

 

You need to login to view this posts content.