[ARCHIVED] Windows Editions Reconstruction Project

Reserved.

 

These custom images are made with just Windows precompiled compoments, not from bare code.

 

Tarsynear thinks too much. EeroS is appropriate.

 

@xinso

pm link for Windows_InsiderPreview_ServerDataCenter-in-ServerWeb-style_vNext_xx-xx_20344_No_Edge.wim (2,876,638 KB)

 

deleted for no responce

 

Q: Why I always failed in manual creation of custom Server image?
A: Besides sequence issue, the other factor is the error caused by mismatched manifest information.

 

Q: How to make 14393 .NET48 applicable to 10240 and 10586?


PS.
Any modified updates can be installed\integrated OFFLINE only.

 

I'm currently comparing x64 WOW64 packages and "real" x86 packages.

 

Reserved.

 

For no response, I'll delete and never reply since then.

 

What is the purpose of this project?

When I was young, there were two similar projects:
In addition to yours, the other most popular one is "pure amd64".

 

You need to login to view this posts content.

 

Reserved.

 

Can UI.Xaml.2.4 be removed?

Server 2022 Desktop Experience has

WindowsApps:
UI.Xam
VCLibs

SystemApps (more than 17763.1):
Microsoft.Windows.Search_cw5n1h2txyewy
Microsoft.Windows.SecHealthUI_cw5n1h2txyewy
Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy
MicrosoftWindows.Client.CBS_cw5n1h2txyewy
MicrosoftWindows.UndockedDevKit_cw5n1h2txyewy

 

Reserved.

 

OK.

 

Just experimenting, modding Windows to pure x64 has been around for ages.

 

On Server 2022 Desktop Experience, (at least) SecHealthUI failed when UI.Xam and VCLibs were removed.

 

Reserved.

 

OK. Thanks.

AppxManifest.xml might be of help.