[ARCHIVED] Windows Editions Reconstruction Project

Steps which are need to be followed to make one or I can say full automatic script to reconstruct/construct it

 

I don't renew all Reconstruction scripts. Is 19041.1 script for x86\amd64\arm64 3-in-1 without update OK ?

 

Reconstruction script for 19041.1 Enterprise G amd64 en-US with update(.ie., 19045.3208) if possible

 

No. I don't renew Reconstruction scripts. 19041.1 is flexible and convenient to add any update with professional 3rd-party tool.

 

So no issue in integrating updates via W10UI.cmd on Reconstructed 19041.1 Windows 10 G edition?

 

It should be OK. Because it's not OEM.

 

@xinso
Dear Teacher,I have a question for you，Like This Package:Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.17763.1
This Package included some files and folders:
File: amd64_microsoft-windows-win32calc_31bf3856ad364e35_10.0.17763.1_none_3a7509176fdfd06a.manifest
amd64_microsoft-windows-win32calc-deployment_31bf3856ad364e35_10.0.17763.1_none_95fd231b684e68b2.manifest
update.cat
update.mum
wow64_microsoft-windows-win32calc_31bf3856ad364e35_10.0.17763.1_none_44c9b369a4409265.manifest
Folder: amd64_microsoft-windows-win32calc_31bf3856ad364e35_10.0.17763.1_none_3a7509176fdfd06a
wow64_microsoft-windows-win32calc_31bf3856ad364e35_10.0.17763.1_none_44c9b369a4409265
So like "_3a7509176fdfd06a";"_44c9b369a4409265”，How it was generated,sincerely thanks~
I modify mum and manifest,I want to Rebuild the suffix id of folder name.

 

It's beyond my ability. Please search help from either abbodi1406 or gailium119.

 

Editing the .mum file is easy. However editing the .manifest files is the problem. Because of the checksum errors. DISM checks if the .manifest files are edited or not. If you edit the .manifest file, you will have to rebuild the .cat file and sign it yourself.
So, I would you to recommend to edit .mum files only. Also don't touch the "Deployment" package values. The "Deployment" packages are actually the .manifest files.
For example:

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-Branding-CoreConnectedN-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="6.3.9600.16384"/>
  <package identifier="Microsoft-Windows-Branding-CoreConnectedN-Package" releaseType="Feature Pack">
    <update name="Microsoft-Windows-Branding-CoreConnectedN-Deployment">
      <component>
        <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Branding-CoreConnectedN-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10586.0" versionScope="nonSxS"/>
      </component>
    </update>
  </package>
</assembly>

I've used this for backporting SKUs from 10586 to 9600.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

No problem my friend, take your time

 

WOW, you had done a great job. Congrats.

 

Today is a good day for something new.

 

OK.I am still very grateful to you,Dear Teacher.

 

Welcome.

 

Thanks for sharing your experience.In the last,like 20348 Construction or other Clinet&Server Construction,If there didn't Exist Some Package,I will make Package Porting, only Edit Mum to bridge files.
In recent days,I am very interested in the suffix id of Manifest,I think it is important.

 

Dear Teacher,In my way ,I'm just giving an example，From the bottom，I want to change all Edition Number in the ALL Manifest And Mum,To Make a New Package Instead of Bridge Package.
It's just that I'm curious about this suffix，a bit Obsessive，I want the Package Porting used the same edition number,deployment package still be changed to the same edition number.

 

Test Reconstruct 25398.1 Windows 11 IoT Enterprise LTSC (without Store) amd64 en-US

Code:

No good for no Edge

Missing Edge.
Why?
Server Core has no Edge.

Copy Edge folder won't work.

 

There are two "update is under way" during OOBE.

Edge will be up to date by one of them.
This is why I said: No chance to show integrated Edge build upon the very first login.

The second one, I think, because Edge update needs more time.