[ARCHIVED] Windows Editions Reconstruction Project

Thanks! I did a fresh installed...!

 

@xinso

Where can I get these package files

Code:

amd64_microsoft-windows-editions-client_31bf3856ad364e35_10.0.19041.1_none_xxxxxxxxxxxx
x86_microsoft-windows-editions-client_31bf3856ad364e35_10.0.19041.1_none_xxxxxxxxxxxx
amd64_microsoft-windows-editions-client_31bf3856ad364e35_10.0.19041.1_none_xxxxxxxxxxxx.manifest
x86_microsoft-windows-editions-client_31bf3856ad364e35_10.0.19041.1_none_xxxxxxxxxxxx.maifest

 

Oh. editions-client? I can't find them. Where did you see them?

You meant:

amd64_microsoft-windows-editions-core_31bf3856ad364e35_10.0.19041.1_none_xxxxxxxxxxxx
amd64_microsoft-windows-editions-professional_31bf3856ad364e35_10.0.19041.1_none_xxxxxxxxxxxx
amd64_microsoft-windows-editions-enterpriseg_31bf3856ad364e35_10.0.19041.1_none_xxxxxxxxxxxx
amd64_microsoft-windows-editions-enterprises_31bf3856ad364e35_10.0.19041.1_none_xxxxxxxxxxxx

If yes, they are from
Microsoft-Windows-Editions-%SKU%-Package~31bf3856ad364e35~amd64~~10.0.19041.1
in
Microsoft-Windows-EditionSpecific-%SKU%-Package~31bf3856ad364e35~amd64~~10.0.19041.1

 

Actually I was trying to re-create LTSC 2021 19041.1 using the files from yesterday's official LTSC image files

In the earlier guide there was these two package files inside Microsoft-Windows-EnterpriseSEdition-Package-amd64-10.0.19041.1.cab

Code:

amd64_microsoft-windows-editions-client_31bf3856ad364e35_10.0.17763.1_none_50d477fcc05015c9
amd64_microsoft-windows-editions-client_31bf3856ad364e35_10.0.17763.1_none_50d477fcc05015c9.manifest

So was looking for similar 19041.1 files to replace them.

 

Oh. It is old 17763.1. No, those initial 19041.1 components are gone with 19041.1288 LCU being resetbase..

 

What updates are in 19044.1288 LTSC amd64 install.wim?

[Official]

[install.wim]
Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1220.1.0 (SSU)
Package_for_KB5003791~31bf3856ad364e35~amd64~~19041.1237.1.3 (21H2Enablement)
Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1288.1.7 (LCU)
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4400.1 (NDP48)

[winre.wim]
Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1220.1.0 (SSU)
Package_for_KB5005645~31bf3856ad364e35~amd64~~19041.1262.1.5 (bootux for winre)

PS:
The winre has not been resetbase.

[My Homebrew]

[install.wim]
Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1220.1.0 (SSU)
Package_for_KB5003791~31bf3856ad364e35~amd64~~19041.1237.1.3 (21H2Enablement)
Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1288.1.7 (LCU)

[winre.wim]
Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1220.1.0 (SSU)
Package_for_KB5005645~31bf3856ad364e35~amd64~~19041.1262.1.5 (bootux for winre)
Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1288.1.7 (LCU)

 

Q: Is the offficial image with Store while Microsoft creates it?

Have you ever seen any Windows App defined in an SKU's package structure?
Have you ever seen Windows App being updated by Windows Update?

 

Q: Is it wise to reconstruct LTSC without Store with original Pro image?

 

Q: Is 19044.1288 LTSC a good release?
A:

 

Q: Is it possible to convert 19044 Pro to Enterprise LTSC?
A: Yes.

 

Question to finalize in my mind:
What we have:
1) LTSC Enterprise 2021 - x86 and x64
2) LTSC Enterprise Eval 2021 - x86 and x64
3) LTSC IOT Enterprise 2021 - x64 only
4) Enterprise 21H2 - x64 and x86
5) IOT Enterprise 21H2 - x64 and arm64


Questions on reconstruction:
1) LTSC IOT 2021 x86 - just use LTSC Enterprise 2021 x86 and change key?
2) LTSC IOT 2021 arm64 - what is the best way?

 

Answers:
1. Yes.
2. No idea.

 

For 2 I mean what would be the closest way to what MSFT does?
Start with IOT Enterprise 21H2 arm64, take few missing packages from LTSC Enterprise 2021 x86? as they might run on arm64?

 

The easiet way to test arm64 Enterprise LTSC is quick-switch.

 

Can you give some more comments?
I remember you described an approach to keep reconstructed image updatable, but miss details.

And very quick Q: - in latest PSF LCU - are there EnterpriseS arm64 mums? Havent checked it yet.

BTW: Have a serious explanation, why me, previously paying no interest to either IOT or arm64 images am now quite intersted, - first in IoT LTSC x64, second - if it's possible from licensing perspective IoT LTSC arm64

 

From what i successfully tested :
Reconstructed LTSC 2021 editions, using (psfextracted) baseless psf/cab combo ARE updatable, but using updated baseless psf/cab again.
They do NOT WU the classic way...
To do this flawlessly, i had to copy the whole win32calc 19041 files and tree structure into the latest release baseless psf extracted directory.
win32calc mum and cat files must be fully named and qualified to function :
Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum
Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cab
instead of the short name SxSv1 may produce, or the ones you may download elsewhere...
Include the win32calc localized LP cat and mum files into the updated baseless structure too.

Then applying dism with packagepath targeted on the modified "baseless_latest" directory DOES the online update with no glitch.
Tested from 19044.1288 installed LTSC N 2021 VM to 19044.1348 one shot. WU happy !

 

Are you answering my question about arm64 image?

 

Hmmm... No. General gossip...

 

@xinso
Could you maybe elaborate on how you built the professional from the 19100.1064 ppipro.
There doesn't seem to be a Professional_en-us_XXXX.esd.

I'm trying to wrap my head around the whole process but there really isn't a noob tutorial about what you guys are doing.
I managed to create a 19041.1 EnterpriseG with the help of the file package on the first page and followed the single steps in the batch files...but without a description of where these provided files came from i don't get too far.

 

You need to login to view this posts content.