[ARCHIVED] Windows Editions Reconstruction Project

You need to login to view this posts content.

 

As you said:
but how to add Enterprise certificate in C:\Windows\System32\spp\tokens\skus\ and reset the certificate, the right-click of the start menu is valid
--> I correct for you
but why it worked when Enterprise certificates folder were added in C:\Windows\System32\spp\tokens\skus\?
--> workaround
While reconstruction, add Enterprise license package to Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum

Code:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved.">
  <assemblyIdentity name="Microsoft-Windows-EnterpriseS-SPP-Components-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Microsoft-Windows-EnterpriseS-SPP-Components-Package" releaseType="Feature Pack">
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-License-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-License-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
      </package>
    </update>
  </package>
</assembly>

 

Good morning. Let's play


Q: Why some extraction script failed for some baseless files?
A: The cab has 2 GB limitation. If the script extracts the baseless LCU directly into cab, it may fail.

 

Yes, we have to learn a way to remove System Apps, NOT with the way for Windows Apps removal.

Fact:
System Apps, in C:\Windows\SystemApps, are made of packages (supported by LCU).
Windows Apps, in C:\Program Files\WindowsApps, are made of UWP files (supported by Store).


Q: How about 1904x new Internet Browser update for ChromiumEdge?
A: Oh, this is a combo PACKAGE.
ChromiumEdge in C:\Program Files (x86)\Microsoft
Edge deployment files stay in same old C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe

Still a PACKAGE, NOT Store App.

DON'T try to remove it with inappropriate Apps Removal tools. Otherwise, the outcome shall be:
1. The removed System Apps recovered by LCU for builds as of 17763.1.
2. The LCU failed for builds from 18362.1 forward.

18362.1...

 

Q: Is ServerWeb capable of being a workstation with Store?
A: Not fully. It is lacking in some mandatory components.

 

Q: Is it wise to remove ChromiumEdge from 1904x?
A: It depends on what have been done to it.

Fact1:
The PSFX LCU will update it now and then. It fails if source is missing or tampered.

Fact2:
The LTSC Client and Server do not have Internet Explorer package. The latest ChromiumEdge is being an add-on installed manually by Microsoft. That's why the LCUs can work fine.

 

Q: Is it possible to port 19041 LCU's ChromiumEdge to LTSC without affecting upcoming LCUs?

If ChromiumEdge integration is succeeded, theoretically the upcoming LCUs should be OK.

 

Reserved.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Have you figured it out now?

Yeah, maybe we have to compare the Product policy.

 

You need to login to view this posts content.

 

22000 PPIPro works with VMware. But LCU does not support it ATM.

 

You need to login to view this posts content.

 

Certificate ProductPolicy

20348.143 ServerTurbine (current system)
ServerDatacenter does not have Security-SPP-FlexibleClipEnabled
ServerTurbine has Security-SPP-FlexibleClipEnabled 1
ServerDatacenter+ServerTurbine does not have Security-SPP-FlexibleClipEnabled

22000.132 IoTEnterpriseS (current system)
IoTEnterpriseS or EnterpriseS does not have Shell-WinXMenu-Enabled
Enterprise has Shell-WinXMenu-Enabled 1
IoTEnterpriseS or EnterpriseS+Enterprise has Shell-WinXMenu-Enabled 1

By comparison, Can I say that the certificate has a primary and secondary distinction?

 

For EditionSpecific, I found that Microsoft-Windows-Branding-xxx-Package has never been updated, and if you create one, it will not affect the update.

 

Very good. But I can't understand "there are primary and secondary points for certificates". What points?

Certificates, besides Activation, it defines Product policy.

Default Product policies,
Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package

Override Product policies,
Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package
Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package

 

At the moment ONLY, when it is NOT fully developed.

 

19044 LTSC packages, available in LCUs from 19041.1149 forward.

Code:

Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1149
Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1151
Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1165

 

Oh, I see.

LTSC Client's WinXMenu and ServerTurbine's Activation for example, when a set of Cerfificates is added on, it may override original ones, and hence Product policy changed.