[ARCHIVED] Windows Editions Reconstruction Project

--delta-from=
&
-delta-from=

 

Could it be:

Code:

wimlib-imagex append F:\ ..\pro.esd --delta-from=".\UUPs\*.esd" --solid --threads=2

 

You need to login to view this posts content.

 

I used it first.It appearently didn't went well.

 

Keep going. Don't give up easily.

You mistook its usage? (Probably.)

Maybe those files (cab\esd) can be expanded to a folder and captured into one wim\esd? (alike Unstaged "Packages")

Yes, your script has "Packages", capture it to Packages.esd. Then export\apply --ref=".\Packages.esd"

You can use it as custom image. Because official UUP is in-place. No need to bother.

 

Idea: Maybe I can reference the official uup install.wim to unstaged.Then it will be much smaller.

 

OK. Give it a go and see if you have time.

 

17763 does not use new Update Technology like builds from 18362.1 forward.

Q: Does 17763 use PSFX updates as 18362?
A: Yes.

 

Q: Is microsoft-windows-editionpack-professional-package.esd necessary when there is microsoft-windows-editionpack-ppipro-package.esd?

e.g. 19041.1 microsoft-windows-editionpack-ppipro-package.esd

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-EditionPack-PPIPro-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Microsoft-Windows-EditionPack-PPIPro" releaseType="Feature Pack">
    <update name="c1dff5c5a42a27a5461e2fd497da80c9">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Client-Features-PPI-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="bf41d538080fad23e6a094f15f3e50d9">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Team-DevTools-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="858bf352242f5637a24a7da4a6efcea9">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="2d4b1be9c3f73d14c530b7ce6faad8fe">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-PPI-Hardware-Bantry-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="7ca0f0ddeb2846a147a763155a64bf55">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-PPI-SystemApps-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="0c938e8814896bb6f4e1c33cf3ba554d">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-PPI-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="0ae0ee634ca73bda73da7736acd42092">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Shell-PPI-Group-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
  </package>
</assembly>

Microsoft-Windows-EditionPack-Professional-Package

A: No.

 

Well, I use 19041.1 Professional_xx-xx.esd and the install.wim (3,573 MB) it creates to export index 3, the oucome is a wim of 2,303 MB without winre.wim.

Dism does not know it. Then, with Dism++, I apply it to a partition, and it installs and updates. It hangs at "rebooting".

Now, both System and Store, up to date and working fine.

 

Do you know what's missing?

 

Oh, I don't know. Check it yourself.

 

You need to login to view this posts content.

 

... whatever

 

i know i like that, but i am have interested to see the professional 20348 in my VM

 

if you can

 

I don't. Try gailium119.

 

ok, i will try

 

@xinso Do you have 22000.1 enterpriseS edition files?

 

You need to login to view this posts content.