Windows Editions Reconstruction Project

CoreCountrySpecific is for zh-CN only, isn't it?

 

Btw, haven't you thought, if I take two LPs - ZH-CN and RU-RU for example.
I take license and catalog files from ZH-CN, and all binary files from RU-RU (renaming them to be like ZH-CN)
Would that work?

 

You need to login to view this posts content.

 

It potentially would work if only contents remain un-touched.

 

Same applies to 19042? How to get EnterpriseS? I can't install enablement package on 19041.
Do I need specific first 19042 build to repeat what you showed us in 19041.1_PRO-to-ENTS_amd64_en-US.zip
I doubt 19042.1 exists

 

Code:

=================================================================================================
Creating 19041.1 Windows 10 Home Standalone image amd64 en-US
=================================================================================================

Mounting image

Removing Professional

Current Edition : Core

Cleaning up component

Unmounting image

=================================================================================================
19041.1 Windows 10 Home Standalone image amd64 en-US has been successfully created
=================================================================================================

Press any key to continue . . .

 

There is no 19042.

 

I wasn't able to install only the enablement update, after which normal SKU becomes 20H2. EntS didn't accept update
But can I /apply-unnatend and add license file to PRO 20H2 to get EntS 20H2?

 

Yes. But I am not good at it. You need a Master.

 

@xinso

Home-to-Standalone-to-EnterpriseS

Updating . . .

Spoiler

Before updating

Code:

Deployment Image Servicing and Management tool
Version: 10.0.19041.1

Image Version: 10.0.19041.1

Current edition is:

Current Edition : EnterpriseS

The operation completed successfully.

Windows(R), EnterpriseS edition:
    The machine is permanently activated.

Press any key to continue . . .

After updating.

Code:

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19041.630

Current edition is:

Current Edition : EnterpriseS

The operation completed successfully.

Windows(R), EnterpriseS edition:
    The machine is permanently activated.

Press any key to continue . . .

Didn't need to redo

Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.cat
Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.mum

and registry key

Updates only Security updates as it should.

Will see how it goes in the next few days

 

Sooner or later, when the image base was reset, the registry will be removed.

 

Same method . . . Home-to-Standalone-to-EnterpriseG

Spoiler

Code:

Deployment Image Servicing and Management tool
Version: 10.0.19041.1

Image Version: 10.0.19041.1

Current edition is:

Current Edition : EnterpriseG

The operation completed successfully.

Windows(R), EnterpriseG edition:
    Volume activation will expire 1/19/2038 11:11:24 AM

Press any key to continue . . .

Code:

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19041.630

Current edition is:

Current Edition : EnterpriseG

The operation completed successfully.

Windows(R), EnterpriseG edition:
    Volume activation will expire 1/19/2038 11:11:24 AM

Press any key to continue . . .

What script?

This registry?

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.19041.1]
"InstallClient"="DISM Package Manager Provider"
"InstallName"="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
"InstallLocation"="\\\\?\\d:\\os\\out\\Temp\\amd64fre\\4hbhcfxl.jug\\Client_staged\\"
"CurrentState"=dword:00000070
"SelfUpdate"=dword:00000000
"Visibility"=dword:00000001
"InstallTimeHigh"=dword:01d44d0e
"InstallTimeLow"=dword:2622bfc4
"InstallUser"="S-1-5-21-4237877585-3242297071-328945437-1018"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.19041.1\Owners]
"Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.19041.1"=dword:00020070

 

Add a command line to Import this registry at top of the script you show EnterpriseS and activation status.

 

For example:

1. Copy EnterpriseS.bat and EnterpriseS.reg to C:\Users\Default
2. Import Run.reg

Then it will silently import the registry at every boot , and hence the OS is always EnterpriseS.

 

Could we put the "owner" there which belong to professional mum file. Will it be deleted also by dism cleaning?
I'm just curious about the limitation of deleting package registers by dism if some owner are writing down there.

 

professional mum will be superseded by new mum.

 

AnyEdition_as_EntS_since_17134

Code:

Mounting image

Creating 19042.572 Windows 10 Education as EnterpriseS amd64 xx-XX

Current Edition : EnterpriseS (OEM)

Removing Appx

Resetting image base

Unmounting image

19042.572 Windows 10 Education as EnterpriseS amd64 xx-XX has been successfully created

Press any key to continue . . .

 

How you did that?
Rename enterpriseS files to pro?
Or pro got stage/removed?

I have tried to make a project like that but it requires 6 basic steps for me. And the results were very disappointing. I can't install it as usual, but I have to go through another application to install it.
1. Staging Professional.
2. Install EnterpriseS
3. Rename EnterpriseS files to Professional package files.
4. Remove Professional
5. Staging EnterpriseS
5. Install "The Professional" files which got at step 2.
6. Remove EnterpriseS.

 

I am doing 2Sec-Edition-Switch.

 

Yes, I see that.
But for me, that is not "real" reconstruction". It just converting between SKUs.