[ARCHIVED] Windows Editions Reconstruction Project

Not exactly a request but 25398 updates are a bit of a mess.

The kb5035856-x64_March 12, 2024 patched by @zwl29107 breaks the Hyper-V console / service (VMMS).

The same (untouched) still has the same problem on Pro flavour

kb5036910-x64_April 9, don't install at all.

Personally I'm not affected by the updates sick, but still if you have nothing to do...

 

Q: How does Microsoft activate\ban an edition?
A: It activates\bans by detecting "EditionID" in product policy of License.

 

Hi @xinso here I have an old problem, is there a way to change 17663 (1809) Enterprise to 17663 EnterpriseS (LTSC)? Thanks very much!

 

If 17763.1, yes, you just start to learn from OP firstly.

That 19044 LTSC one. But it might be invalid. Search for Abbodi1406's script. You can ask Abbodi1406 for help too. Because it is his\her script, he\she knows it the best.

 

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.

 

Currently, what is the list of available Microsoft Internal Packages ?
What are the contents of a typical Microsoft internal package used for construct?

 

A1.
InternalBuildPackage-ServicingStack-OneCore-InstallOptions-Package~31bf3856ad364e35~amd64~~10.0.22621.1.

A2.
Unknown. Because it is removed upon completion of Construction.

The system has this package.
Microsoft-Windows-ServicingStack-OneCore-InstallOptions-Package~31bf3856ad364e35~amd64~~10.0.22621.1

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-ServicingStack-OneCore-InstallOptions" version="10.0.22621.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
  <registryKeys>
    <registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase">
      <registryValue name="ConfigOptions" valueType="REG_DWORD" value="0x00000003" />
      <registryValue name="ConfigOwner" valueType="REG_SZ" value="OneCore" />
    </registryKey>
  </registryKeys>
  <memberships>
    <categoryMembership>
      <id name="Microsoft.Windows.Categories" version="1.0.0.0" publicKeyToken="365143bb27e7ac8b" typeName="ServicingStackComponent" />
    </categoryMembership>
  </memberships>
</assembly>

 

Considering that its file does not ultimately exist, perhaps we can replace it with a tweak.

 

It may be possible to
- recover these files before completion if they are deleted later on
- create the missing package files and their contents if these files do not contain any missing binaries.

 

We are unable to obtain its detailed information.
Furthermore, for 26100, the available components are insufficient to reconstruct WinVOS.

 

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.

 

You need to login to view this posts content.

 

Nice!
xinso, sir, wanted to ask you about 25398.1
I see you do lot of Client reconstructions for it. But have you investigated server?
1) Instead of ServerDatacenterCore, that comes with it make full ServerDatacenter
2) Create a ServerHyperCore, like I seen you once done for 17763.1 - with or without UI.

Seems that AC (Core) builds of Server would come annually now, while LTSC each 3 years.

 

A1:
The CU supports ServerDatacenter Desktop Experience.
But lacking 25398.1 initial components. You can try asking gailium119 and zwl29107 If they could help repacking 25398.1.

A2:
If without compatible components, impossible. And update is another problem.

 

Thanks for answering!
So question for gailium119 and zwl29107 - how difficult is to reconstruct ServerDatacenter Desktop Experience 25398.1
I understand, that with 26100.1 coming soon, task is more a playground, - but as annual builds are core, we expect this to be repeated.
Is that technically possible to reconstruct Desktop Experience SKU, that would update (as long as CUs do support it).

 

I asked that @zwl29107 just a page ago and I was ignored, so...

I know that for some reason you hate the HCI flvour, but (unlike the above case) I can't see the practical use of that.

Just start from HCI ISO, remove the azure service, remove the packages you dont want. Or (better) remove all the disabled roles/features payload with a single line of code.

CMD

Code:

for /f %%a in ('dism /online /get-features /format:table ^|find "| Disabled"') do (dism /online /disable-feature:%%a /remove)

or PowerShell

Code:

Get-WindowsOptionalFeature -Online | where { $_.State -match "Disabled" } |
foreach { $_ = $_.FeatureName;
DISM /Online /Disable-Feature /FeatureName:$_ /Remove
}

Done.

If you really want to see the HyperCore writing just SKUwitch it.