[ARCHIVED] Windows Editions Reconstruction Project

But except license yuo need updated binaries.
There is now a fight on communities to return Hyper-V Server SKU )

 

And great thanks for comments. I was able to create Client Language Pack and made ServerRdsh from Datacenter.
Bluetooth, touch and dedup work!

 

You are welcome.

 

Good to hear that.

 

I now appreciate your short style and post editing.
Previously I just set a feeder and waited for binaries. Zero inside the head.
Last few month I gave up a challenge to myself - not to ask for scripts or binaries. And slowly I get to all the targets.

Unfortunately, I won't start recreating Starter/StarterN for 19041 cause have to less info and even less binaries.
But 190xx era is coming to the end... "Winter is coming".
I for sure get Starter images from OEM when that start.
Got storage server disks from HP for 15$ per SKU, officially

 

Test reconstructing 20348.1 Windows 10 Enterprise multi-session Workstation

Code:

==================================================================================================
Converting 20348.1 Windows ServerStandard to ServerRdsh amd64 xx-XX
==================================================================================================

Mounting image

Removing ServerDatacenter

Adding ServerRdsh

Removing ServerStandard

Adding xx-XX language pack

Enabling ServerMediaFoundation

Enabling WirelessNetworking

Current Edition : ServerRdsh

Resetting base

Unmounting image

==================================================================================================
20348.1 Windows Server 2022 RDSH amd64 xx-XX has been successfully created
==================================================================================================

WIM Information:
--------------------------------------------------------------------------------------------------
NAME="Windows Server 2022 RDSH"
DESCRIPTION="Windows Server 2022 RDSH"
FLAGS="ServerRdsh"
DISPLAYNAME="Windows Server 2022 RDSH"
DISPLAYDESCRIPTION="Windows Server 2022 RDSH"
--------------------------------------------------------------------------------------------------

Press any key to continue . . .

 

I read and read, and still can't imagine why you are so sure about "I for sure get Starter images from OEM when that start.".

IMHO, there won't be 1904x Starter(N).

 

Reserved.

 

I worked for HP, DELL, Microsoft, Citrix & Oracle. And I finished thousands of project in all major vendors.
Have much friends and access to internal resources, If it exists I just need a part number )

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Have a quick question for you, if you allow.
Sometimes, during upgrade of supported SKU to non-existing SKU, an error comes
0x8007001F-0x20006, The installation failed in the SAFE_OS phase with an error during REPLICATE_OC operation.
And upgrade process rolls back.
As I understand that's when it tries to install updates and fails, not finding new SKU in update.MUM
That happens even when I disable all NICs
That doesn't happen in VMs...

 

Sorry but I can't answer such a question. Programs, Drivers, Updates... No standard answer.

But, you may have got the answer:

Code:

As I understand that's when it tries to install updates and fails, not finding new SKU in update.MUM

 

You need to login to view this posts content.

 

Question was - if you probably know any setup key or registry hack to prevent updates check

 

And if you allow me asking theoretical questions. Have two more:

1) What was your suggested method to install updates (LCU) on non-existing SKUs, like ServerRdsh 20348? Change something in registry, install, return value. I missed the post (

2) And second if possible - server features that I export with SxSExtract are often inapplicable to same build client.
Cleaning <parent> from MUM doesn't help

Thanks. At least I tried )

 

True. And I suspect 32-bit. But that means vendors have OPK kits.
And they just wait to be copied )

 

I cannot do against Windows Update.

 

)) OK.
Thanks

 

A 1) I don't post twice.
A 2) There are specific restrictions. You have to deal with them.