[ARCHIVED] Windows Editions Reconstruction Project

Look like in:

Code:

Microsoft-Windows-EditionSpecific-ServerDatacenterCor-Package 10.0.25398.1

Only 
Microsoft-Windows-Editions-ServerDatacenterCor-Package needs replacing.

with
Microsoft-Windows-Editions-ServerDatacenter-Package

which Client package will work as:

Code:

Microsoft-Windows-Server-DesktopUX-Package
Microsoft-Windows-Server-DesktopUX-WOW64-Package

 

@Ace2

Added my old script on my previous message, being the last of the page you may haven't noticed

 

Code:

WIM Information:
---------------------
GUID:        {44AB5492-EB1B-43A5-96CA-1499D741BD72}
Image Count:    1
Compression:    LZX
Part Number:    1/1
Attributes:    0x8
        RP_FIX

Image Index: 1
-------------------
Name:        Windows ServerDatacenter 2022
Description:    Windows ServerDatacenter 2022
Flags:        ServerDatacenter
Files:        84497
Folders:        18074
Expanded Size:    11841 MB


WIM XML Information:
---------------------------
<WIM>
  <TOTALBYTES>2772861924</TOTALBYTES>
  <IMAGE INDEX="1">
    <DIRCOUNT>18074</DIRCOUNT>
    <FILECOUNT>84497</FILECOUNT>
    <TOTALBYTES>12417164316</TOTALBYTES>
    <HARDLINKBYTES>4836955884</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01D99C22</HIGHPART>
      <LOWPART>0xE26565DF</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01DAA186</HIGHPART>
      <LOWPART>0x44B8244D</LOWPART>
    </LASTMODIFICATIONTIME>
    <WIMBOOT>0</WIMBOOT>
    <WINDOWS>
      <ARCH>9</ARCH>
      <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
      <EDITIONID>ServerDatacenter</EDITIONID>
      <INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
      <SERVICINGDATA>
        <GDRDUREVISION>0</GDRDUREVISION>
        <PKEYCONFIGVERSION>10.0.25398.1;2016-01-01T00:00:00Z</PKEYCONFIGVERSION>
        <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE>
      </SERVICINGDATA>
      <PRODUCTTYPE>ServerNT</PRODUCTTYPE>
      <PRODUCTSUITE>Enterprise</PRODUCTSUITE>
      <LANGUAGES>
        <LANGUAGE>en-US</LANGUAGE>
        <DEFAULT>en-US</DEFAULT>
      </LANGUAGES>
      <VERSION>
        <MAJOR>10</MAJOR>
        <MINOR>0</MINOR>
        <BUILD>25398</BUILD>
        <SPBUILD>1</SPBUILD>
        <SPLEVEL>0</SPLEVEL>
        <BRANCH>zn_release</BRANCH>
      </VERSION>
      <SYSTEMROOT>WINDOWS</SYSTEMROOT>
    </WINDOWS>
    <NAME>Windows ServerDatacenter 2022</NAME>
    <DESCRIPTION>Windows ServerDatacenter 2022</DESCRIPTION>
    <FLAGS>ServerDatacenter</FLAGS>
  </IMAGE>
</WIM>

Time to install and see if it get to desktop...

 

I am testing Pro version now and it works well so far so you were right.
But I did not reconstruct this, I used a ISO by gailium which has many indexes.
But 25398.830 update does not want to install, I guess this one requires custom update.
I tried to install KB5037015.esd and KB5036910.esd files posted by ZWL in this thread by converting them to cab but W10UI says that the location is not valid. Maybe that update are not valid for Professional or I am doing it the wrong way.

Then I tried to use your instructions after modifying Create.cmd for Professional but when I launch Create-Start-As-Admin.cmd it just closes.
Is there any instructions for how to do it with stageSxS-principalis? I tried to copy some files to from 25398.1_ServerDatacenterCor_to_Client_amd64 to stageSxS folder and modifying cbss script but it fails.

 

You need to login to view this posts content.

 

I guess you can use a unattended.xml placed in the panther folder (there is one ready made in @xinso 's package, meant to be used if you choose the serverRDSH option).

BTW I used a different way.

1) Deploy the core installation in a vhd/vhdx and boot it using Hyper-V (or vmware, or Vbox)

2) Do the OOBE and setup your user(s)

3) Stop the VM and mount the vhd(x)

4) run the script

5) unmount the vhd(x), boot it in Hyper-V and check if it works (do additional fixes if needed, SKUwitch, additional reg fixes, additional packages and so on).

6) If step 5 is ok, add the vhdx to the baremetal bootloader and reboot your machine to use it.

My script (IIRC) was meant to be used starting from enterprise UUPs, here we have professional, so I guess some adjustment is needed.

P.S. After you SKUwitch to ServerStandard or ServerDatacenter (or RDSH or HCI) you *may* need to add

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Server]
"ClientExperienceEnabled"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Server\ServerLevels]
"Server-Gui-Mgmt"=dword:00000001
"Server-Gui-Shell"=dword:00000001
"ServerCore"=dword:00000001
"ServerCoreExtended"=dword:00000001

(run regedit as trusted installer)
To have all the GUI features working properly (it doesn't hurt if the actual SKU is client)

Given at the end of the script your actual SKU ends being client , you may need to to replace the branding folder with the original one from server core when you SKUwitch to Standard/Datacenter/HCI (but not for RDSH which is still a server SKU, but uses the branding from Client versions)

 

You need to login to view this posts content.

 

Not yet fully working but it's something (notice the old branding, you need the branding folder from server 260xx to get the 2025 one).

No much time today but I think some missing package should fix the remaining glitches (the taskbar is in W10 mode by default and explorer isn't working to browse files)

 

You need to login to view this posts content.

 

Thank you.

 

I can fix it, but I don't want to republish .830 CU again.
.887(or higher) CU will be released in six days.

gailium119 directly patched the serving stack to fix this error. This is more universal, but it will undermine the official nature of executable files.

 

You need to login to view this posts content.

 

Are the Custom updates in ESD format supposed to be integrated to the wim file or can they be installed on a running system?

 

I suggest none of them.

Online doesn't work (obviusly) except for Pro and untouched packages

Integrating on the wim is also stupid, you'll never know if a problem you may have is there because a problem in the original image or because the updates.

In short install offline on the already installed system (after you tested it) at least do that if you mind to use the system for something useful and not just to play with random images.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

But what is the correct way to install them? I downloaded the updates by zwl29107, converted them to cab and tried to install but that didn't work.

Since the Pro version of 25398 works well for me unlike the Enterprise versions I would stay on it if I knew how to install updates. I would like to reconstruct Pro myself so I can install updates from UUP but I failed, not sure what I'm doing wrong.

 

Windows Server 2022 Datacenter Version 23H2 Build 25398.1

Screenshot (1).png SHA1 77c4cf87e5e84310f8574247fe6c29c6f68442bb
Screenshot (2).png SHA1 f673c3066ce29875ea5c4b680793901e60b16232
Screenshot (3).png SHA1 782aa063d178a0dc25974c9f5c609692c31ee74b
Screenshot (4).png SHA1 c317c138e34e3ed76a4696b8697f5096bc8c95b2
Screenshot (5).png SHA1 a10862cac8b18029f5044b03e1166eb5eb5113b7

[Full Credits] to acer-5100 without his info i would never have made this build.

 

You need to login to view this posts content.

 

Did you download ISO by gailium from archive.org ?
I will download and test Pro with updates to see if they work, if not i will try to see how to fix.