[ARCHIVED] Windows Editions Reconstruction Project

Although it is officially activated, BUT there are files that would cause Time-Bomb BSOD.

 

The preview version removes the expiration time, which is still difficult for me at present, I can only block the display.

 

Forget it. Use Official releases.

 

I am also thinking that in the early version, if you modify the installation package, you can install it offline or online. Now you can only install it offline, if you modify the installation package.It is probably the reason for Windows Integrity Check.I haven't figured out how to crack it.

 

You can find the files, but I think NOT that easy.

 

Manual Components Removal is good for Old systems because of new Update technology.

 

I don't understand it all at once, so I need to think about it.

 

Create xml: copy information of a component manifest about File, Folder, manifest, registry, language File, etc

Remove by xml: Remove those things documented in the created xml

 

You need to login to view this posts content.

 

It's a bit difficult for me

 

For creating xml:
1. Read it's usage in readme.txt
2. Set Path in settings.ini
3. Run create.exe to start creating xml

For removing components by xml definition
1. Read it's usage in readme.txt
2. Run remove.exe to start removing

These two tools are seperated for two jobs. You can use my "repacked" one for convenient and flexible use - two jobs in one.

 

Can you send me a complete document?

 

It's exact same as I mentioned. You need to digest it (together with #2089) yourself.

 

Microsoft starts pushing Feature update to 15063 PPIPro: H:\Windows\UpdateAssistantV2

OK. Let me see how... Nope. It detects Manufacturer info.

Code:

2021-03-17 22:33:49.571, Error     [OperatingSystemInfo::GetOEM] Failed to read Manufacturer info. Error code 0x80070002

 

How difficult is now adding normal desktop experience to ServerACor (like 20H2 or 21H1, taking something from client). I don't mean the server core AppCompatibility

 

You need to login to view this posts content.

 

It is pretty difficult to build image that doesn't break soon. I tried it with tutorial from this topic: https://forums.mydigitallife.net/threads/guide-adding-gui-to-server-core-1-21v.76023/

 

Q: Which package controls the "Desktop Experience" functionality for Server?
A: Microsoft-Windows-ServerShellInfra-Package~31bf3856ad364e35~amd64~~10.0.20313.1.

Q: How?
A: amd64_server-gui-desktop-defaults_31bf3856ad364e35_10.0.20313.1_none_8d758579768fd10d.manifest.

Code:

    <registryKey keyName="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Server\">
      <registryValue name="ClientExperienceEnabled" valueType="REG_DWORD" value="0x00000001" />
      <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" />
    </registryKey>

 

You need to login to view this posts content.

 

What's the next challenge? EnterpriseS conversion of Professional 20308.1?