[GUIDE] [DISCUSSION] Windows Editions Reconstructions

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.

 

You need to login to view this posts content.

 

[19044.1415 from CMGE_V2022-L.1345.iso]
2021-08-30

[19044.5737 by CMGE Update System]
2021-08-30

[19044.6093 by CMGE Update System]
2021-08-30

 

Q: Is there any solution to bypass 27XXX Preview "Integrity Check"?

 

i read that LTSc has minimum telemetry and G is completely without... (Allow Telemetry = 0) Does reconstructed editions follow this rules?

 

Enterprise G are ltsc + custom gpo to block telemetry

 

You need to login to view this posts content.

 

Anyone to rescue Reconstruction of vNext (Previews)?

Renamed, failed. Modified, failed. The .cat.

 

so basically G gpo can be exported and applied to ltsc? Any articles or solution on this topic?

 

A detailed walkthrough would be good

&

How to export gpo from Microsoft-Windows-EditionSpecific-EnterpriseG-Package.esd (26100.1)

 

How calculate hash for update package name?
md5("name|????|????")

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-OneCore-Console-Driver-Demand-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Microsoft-OneCore-Console-Driver-Demand" releaseType="Feature Pack">
    <update name="f63b75832875bc73715e4db582d38438">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-OneCore-Console-Driver-Demand-minkernel-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="ee0c7e45e1939277e4189a14d10f60c7">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-OneCore-Console-Driver-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
  </package>
</assembly>

md5(Microsoft-OneCore-Console-Driver-Demand-minkernel-Package)=f63b75832875bc73715e4db582d38438
md5(Microsoft-OneCore-Console-Driver-Package) = 7529777726e451b608b22b8ec66fe303 <> "ee0c7e45e1939277e4189a14d10f60c7"

how ee0c7e45e1939277e4189a14d10f60c7 is calculated?

just find answer self
md5(7529777726e451b608b22b8ec66fe303)=ee0c7e45e1939277e4189a14d10f60c7

 

You need to login to view this posts content.

 

My 27909.1000 workaround to reconstruct Professional to Enterprise G offline works, just need to "test" installing wim

 

makecat

 

Deployment just directly uses single MD5:

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="Composition-Core-merged-Package" version="10.0.26454.1000" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Composition-Core-merged" releaseType="Feature Pack">
    <update name="0d1b19e6ea89a3ceb1a097fbf5da9dc2">
      <component>
        <assemblyIdentity name="Composition-Core-merged-Deployment" version="10.0.26454.1000" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
      </component>
    </update>
  </package>
</assembly>

INFs and some WCOS packages use 256-bit hash, maybe SHA256.

 

Does anyone know content this mum?
Microsoft-Windows-Minwin-State-onecore-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum
Microsoft-Windows-Minwin-State-minkernel-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum

 

You need to login to view this posts content.

 

Fingers crossed...