[ARCHIVED] Windows Editions Reconstruction Project

25393.1 Client language pack is compatible with 25398.1.

25379.1 Server Desktop Experience
25398.1 Server Desktop Experience
--->
Same structure

Q: Would it be possible that 25379.1 Server Desktop Experience is compatible with 25398.1?

 

You need to login to view this posts content.

 

Going to give it a try.

 

Got something that seem fairly usable (my first attempt and ace2's ones weren't, for different reasons).

Hyper-V works, WSL works, RASS works, Server manager works except for adding removing roles (but that's an old story).

Still far from being perfect, but usable.

 

Yes. Success and Failure, both are your experiences, same precious.

 

Can you share how you did it?

 

You need to login to view this posts content.

 

More or less merging my old script with the ace2 way, (both of them are explained in incredibly detailed way for the habits of this room) then the bigger problem was defender that hdd the services enabled although, in theory it wasn't supposed to be enabled, so everything took forever waiting for defender that never came in). Deleted the win defender service and everything started working as supposed to)

 

because the client packages are include defender
so if u are removing the server package of defender the client will fill it back :X

 

The server includes the defender packages as well, but the problem is that some packages aren't not the same (not formally at least) so they get duplicated.

For example Poweshell V2 client, and virtualmachine client fight with the server counterparts, and breaks Dism /get-features (just delete both items from the packages list, and the problem is solved)

 

mb the cat files include all the editions and we could make mum with servers packages minus the packages we dont have

so it could be better experience

 

Ok, fixed that as well. It was easier than I thought

Everything is doable
It's just matter of time, will, and cooperation

 

2025?

 

Branding folder from 26040

 

Windows_InsiderPreview_Server_vNext_en-us_26212.iso

Code:

506, "Windows Server 2025 Datacenter (Desktop Experience)"
507, "This option installs the full Windows graphical environment, consuming extra drive space. It can be useful if you want to use the Windows desktop or have an app that requires it."
508, "Windows Server 2025 Datacenter"
509, "(Recommended) This option omits most of the Windows graphical environment. Manage with a command prompt and PowerShell, or remotely with Windows Admin Center or other tools."
510, "Windows Server 2025 Datacenter (Features On Demand)"
511, "This option installs a complete installation of Windows Server, with some optional features available for installation remotely. This installation includes the entire user interface, and it supports all of the server roles."

 

Try install these four packages to ServerDatacenterCor:

From 25398.1 Client

Code:

    <update name="Runlevel-Win4-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Runlevel-Win4-Package" version="10.0.25398.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Runlevel-Win4-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Runlevel-Win4-WOW64-Package" version="10.0.25398.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>

From 25379.1 ServerDatacenter Desktop Experience

Code:

    <update name="Microsoft-Windows-Server-DesktopUX-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Server-DesktopUX-Package" version="10.0.25379.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Microsoft-Windows-Server-DesktopUX-WOW64-Package">
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Microsoft-Windows-Server-DesktopUX-WOW64-Package" version="10.0.25379.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>

Along with language packs.

 

Thanks

Win-4 package is already installed, I did that manually

The remaining part seem working reasonably well as is.

Il try that If I decide to start over for some reasons

 

You need to login to view this posts content.

 

zwl29107,

Do you think you could be available to complie en-US basebrd.dll.mui to confirm #16038 firstly?

Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1.mum
--->

Code:

    <update name="3A85776914ECCD84253163D62474F25B20F3E924A0D2B6760BA0FFD3B44E97D8">
      <component>
        <assemblyIdentity name="microsoft-windows-client-desktop-required-deployment0" version="10.0.25398.1" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
      </component>
    </update>

--->
amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.25398.1_en-us_038a5020a8d5cb45.manifest

Code:

    <dependentAssembly dependencyType="install">
      <assemblyIdentity name="Microsoft-Windows-Branding-Base-Client.Resources" version="10.0.25398.1" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
    </dependentAssembly>
  </dependency>

--->
amd64_microsoft-windows-b..se-client.resources_31bf3856ad364e35_10.0.25398.1_en-us_311376f7c7597b95

Code:

basebrd.dll.mui

 

Compile? Why?

Use the ones from 25393, and if you want to nitpick edit them with restorator 2018