[ARCHIVED] Windows Editions Reconstruction Project

You need to login to view this posts content.

 

You need to login to view this posts content.

 

hi @spanishfly

Thanks for your help. I have a doubt:

Download 19041.1237 or 19043.1237?

NOTE: The link directs to 19043

 

I have an idea: If conversion from Server to Workstation is possible, why not converting Client to Server?
I'm wondering how x86 Windows Server and Windows 11's server counterpart look like.

 

Reserved

 

Thanks. Corrected the build number. I have a bad habit of calling all 1904X builds "19041" since, really, what's the difference?

PS I may in the future move my two posts elsewhere in the thread. Being split between two pages is kind of a drag...

 

Question: Would a package made with this calculator work better in 19041-19043 reconstructions? And if so could you please package it and share it?

 

Everybody is waiting official release for it.

You need a solution accomplished by yourself.

For package, the solution is "Your learning to use Mr. SuperBubble's package extraction tool".
https://forums.mydigitallife.net/th...s-package-extractor-updated-2013-09-30.48325/

 

This isn't reconstruction but was able to set Telemetry to 0 in Professional

Spoiler

​

 

About SecHealthUI...

As of 20348, it is splitted components combined in some System package which is not possible to uninstall by dism.

Microsoft-ShellCommon-merged-Package~31bf3856ad364e35~amd64~~10.0.20348.1

Code:

  <dependency discoverable="yes">
    <dependentAssembly dependencyType="install">
      <assemblyIdentity name="Microsoft-Windows-SecHealthUI.AppxMain" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
    </dependentAssembly>
  </dependency>
  <dependency discoverable="yes">
    <dependentAssembly dependencyType="install">
      <assemblyIdentity name="Microsoft-Windows-SecHealthUI.AppxSetup" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
    </dependentAssembly>
  </dependency>

From 22000 forward, it is a Windows App for released SKUs.

Code:

Microsoft.SecHealthUI_1000.22458.1000.0_x64__8wekyb3d8bbwe

Therefore, the vNext non-released SKUs shall have a stanalone SecHealthUI package as zhanglin elaborated.

Code:

Microsoft-SecHealth-UI-Package~31bf3856ad364e35~amd64~~10.0.22458.1000

 

I tried this ages ago with Licence Switch. It was cursed to see 17763 ServerDatacenter in x86
Server SPP and Branding files work on x86 just fine.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Whats the benefit / differences of this version? Specifics please?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Q: For Windows 10 19044 LTSC, how to prevent "This PC doesn't currently meet all the system requirements for Windows 11"?
A: Quit "Windows Insider Program" before running Windows Update, not even "Release Preview" channel (maybe it is a temporary bug or mistake).

Q: Any solution not to reinstall system for this annoying prompt?

PS:
Rolling back to previous LCU is useless. It must be added by Windows Update, because it won't happen with Offline Update (unknown if next LCU comes from Windows Update).

Where is it?

Edit:
Now, it is gone with this command.

Code:

dism /english /image:F: /Cleanup-Image /startcomponentcleanup /resetbase

PS:
I am not quite sure if it is for that command. I did it offline and boot it, and it is gone.

Fact:
As usual, LTSC has no Insider program, and hence should not receive anything which is pushed by Windows Update to non-LTSC SKUs.

This is used for my LTSC reconstruction scripts to hide Insider page:

[for old build]

Code:

reg add "HKLM\SOFTWARE1\Microsoft\WindowsSelfHost\UI\Visibility" /v "HideInsiderPage" /t REG_DWORD /d "1" /f >NUL 2>&1

and\or

Code:

reg add "HKLM\SOFTWARE1\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v "SettingsPageVisibility" /t REG_SZ /d "Hide:windowsinsider" /f >NUL 2>&1

[for latest build]

Code:

reg add "HKLM\SOFTWARE1\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v "SettingsPageVisibility" /t REG_SZ /d "Hide:windowsinsider" /f >NUL 2>&1

 

I was wondering what the advantages/improvements are for using your method?
Improved image integrity? Easier to update?

 

Q: What exactly is baseless LCU?
A: It is packages extracted from an image which has been updated with PSFX LCU.

Fact:
The Classic LCU is with original binary files.
The PSFX LCU is with f\n\r files, which is needing original source files in the system, and failed if source files are tampered or missing.

And the baseless LCU is
PSFX
+
Classic

And, it will install in the Classic way.

 

I sit at your feet and learn the Tao of reconstruction. Someday I will grab the pebbles from your hand, master! But not today...