[ARCHIVED] Windows Editions Reconstruction Project

Master, ask a question, I made 22621EnterpriseG, because I don't want to activate KMS, because there is Enterprise digital activation, I add Enterprise certificate, switch to Enterprise, but always display the notification status, but if you install Enterprise directly, it shows the activated status, Comparing the ProductPolicy of the two, I did not find much difference. What is the reason?

 

22621 EnterpriseG is made exclusively for CMGE. When System Appx meet with it, the settings behavior changed.

So, be good and choose one.

Hint:
It needs OEM binaries for EnterpriseG to work with, i.e. those CMGE systems. 19044 OEM binaries are not compatible.

 

Good news: found 10586.0 ServerWeb licenses

Spoiler

Q: Is it compatible with newer builds:
A: Only by testing it.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

It is retail ONLY.

 

It doesn't work after installing Microsoft-Windows-Shell32-OEMDefaultAssociations-Package

Spoiler

 

You are saying that it will activate if not with that package?

Enterprise or Starter?

 

22621EnterpriseG switches to Enterprise, and prompts that the network cannot be connected, but install Enterprise directly and activate directly.

 

Off you go: https ://cdn.discordapp.com/attachments/978602282860027924/987029701384093727/10586_Starter_AMD64.7z

EDIT: had to reup this because I missed a file from Microsoft-Windows-Editions-Starter-Package

 

Thank you so very much!

 

You need to login to view this posts content.

 

pivotman319,

These packages won't install.

Code:

Microsoft-Windows-Security-SPP-Component-SKU-Starter-Package~31bf3856ad364e35~amd64~~10.0.10586.0

Microsoft-Windows-Starter-Features-Package~31bf3856ad364e35~amd64~~10.0.10586
Microsoft-Windows-SysMet-SKU-Starter-Package~31bf3856ad364e35~amd64~~10.0.10586.0

Microsoft-Windows-Editions-Starter-Package~31bf3856ad364e35~amd64~en-us~10.0.10586.0

Thanks.

 

shoot, did i forget a few things? i swear i included everything i could find in the zipfile. can you list down what's missing? i am not good at this, so please forgive me if i did forget a bunch of things.

EDIT: See below post

 

You need to login to view this posts content.

 

starter，It can't be done after 17763.

Spoiler

 

.

You mean, not activateable after 17763?

 

15063.0 Starter is compatible with 14393.0\16299.15\17134.1.

i.e.

15063.0 Starter can be activated:
As of 17134

or

15063.0 Starter can not be activated:
From 17763 forward

detailed info

[Not OK]
10240.16384
10586.0

[OK]
14393.0
15063.0
16299.15
17134.1

[Not OK]
17763.1
18362.1
18363.1
19041.1
.
.
.

 

So what's the problem when it is not OK? Is it about package structure?
10586.0, Microsoft-Windows-Security-SPP-Component-SKU-Starter-Package
14393+,Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package and Microsoft-Windows-Security-SPP-Component-SKU-Starter-License-Package
Or it's about pkeyconfig, that 17763+ starter key in pkeyconfig is not compatible with 15063 licenses, making it not activatable in normal method

 

This is not the very first time I post on 15063.0 Starter's compatibility with other builds.

You are more clever than me, read again and teach me if you please.