Windows Editions Reconstruction Project

The pkconfig of 18362 and 19041 is compatible, no conflict.

And the WIM information can be changed to cheat the eyes.

But I want it exactly 18362.

And, 22621 OK, why not 18362?

 

19045 display?

amd64_microsoft-product-data_31bf3856ad364e35_10.19045.19041.1806_none_c51339d1dae5b49e.manifest

Code:

    <registryKey keyName="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion">
      <registryValue name="CurrentVersion" valueType="REG_SZ" value="6.3" />
      <registryValue name="BuildGUID" valueType="REG_SZ" value="ffffffff-ffff-ffff-ffff-ffffffffffff" />
      <registryValue name="BuildLab" valueType="REG_SZ" value="19041.vb_release.191206-1406" />
      <registryValue name="BuildLabEx" valueType="REG_SZ" value="19041.1.amd64fre.vb_release.191206-1406" />
      <registryValue name="CurrentBuild" valueType="REG_SZ" value="19045" />
      <registryValue name="CurrentBuildNumber" valueType="REG_SZ" value="19045" />
      <registryValue name="SoftwareType" valueType="REG_SZ" value="System" />
      <registryValue name="CurrentMajorVersionNumber" valueType="REG_DWORD" value="0x0000000A" />
      <registryValue name="CurrentMinorVersionNumber" valueType="REG_DWORD" value="0x00000000" />
      <registryValue name="BaseBuildRevisionNumber" valueType="REG_DWORD" value="0x00000001" />
      <registryValue name="BuildBranch" valueType="REG_SZ" value="vb_release" />
      <registryValue name="ReleaseId" valueType="REG_SZ" value="2009" />
      <registryValue name="DisplayVersion" valueType="REG_SZ" value="22H2" />
    </registryKey>

amd64_microsoft-emergencyupdate_31bf3856ad364e35_10.19045.19041.1806_none_1a1fdf0c00ef8be2.manifest

Code:

    <registryKey keyName="HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Windows.EmergencyUpdate.amd64">
      <registryValue name="Version" valueType="REG_SZ" value="10.0.19045.1806" />
      <registryValue name="Repairable" valueType="REG_SZ" value="1" />
    </registryKey>

amd64_microsoft-updatetargeting-clientos_31bf3856ad364e35_10.19045.19041.1806_none_cec569ad2f936610.manifest

Code:

    <registryKey keyName="HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Client.OS.rs2.amd64">
      <registryValue name="Version" valueType="REG_SZ" value="10.0.19045.1806" />
      <registryValue name="Branch" valueType="REG_SZ" value="vb_release_svc_prod3" />
      <registryValue name="PrimaryOSProduct" valueType="REG_SZ" value="1" />
      <registryValue name="Repairable" valueType="REG_SZ" value="1" />
    </registryKey>

You can apply these values to registry, or install the packages.

19045 feature?
It is controlled by 22H2 Enablement package.

You can apply its Enablement code to registry, or install the package.

e.g. 21H2

Code:

    <registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\0\2083071627">
      <registryValue name="EnabledState" valueType="REG_DWORD" value="0x00000002" />
      <registryValue name="EnabledStateOptions" valueType="REG_DWORD" value="0x00000000" />
      <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" />
    </registryKey>

The 19045 display packages detect 19045 Enablement package.
If 19045 Enablement package found, install to system. Otherwise stay at WinSxS.

It's like Windows Features ( except .Net35).
You check, it installs from WinSxS to system.
You uncheck, it removes from system, yet stays at WinSxS.

PS:
The 19045 display packages are installed to WinSxS and stay untill they found installed 19045 Enablement package.

 

Use 18362 pkeyconfig. Either replace the file or repack the package.

 

No, we can't. It is defined in "manifest".

 

The test found that the installation of the lower version of Microsoft-Windows-Security-SPP-Pkeyconfig will not replace the higher version of pkeyconfig, so the PKeyConfigVersion will not change; the installation of the higher version of Microsoft-Windows-Security-SPP-Pkeyconfig will replace the lower version of pkeyconfig，PKeyConfigVersion will change.

 

So onlyway? Repack and testsign the package and eliminate the higher version

 

manifest, repacked?

There must be some parameter for the old build. The former just won't be replaced by the latter. Copy? No.

 

Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseSNEval-License-Package,18362
>>Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseSNEval-License-Deployment,18362
>>>>Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseSNEval-License,19041
>>>>Microsoft-Windows-Security-SPP-Pkeyconfig,18362
Edited deployment is only way.

 

Worked?

 

I worked on 22000 with no 19041 pkeyconfig in winsxs. Same should work.
Although I prefer to edit the version of the license as well.

 

22000 is new - no need to repack; 18362 is old.

 

Al link died

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Server in Client Structure? Does it work as server?

 

What do you think?

 

Q: Why does 19041-modded 18362 package cannot be updated by 18362 package?