Windows Editions Reconstruction Project

You need to login to view this posts content.

 

Everyone has their own way. I just share the simple way for make it from scratch
From scratch you can:
-Tweak as your wish
-Update as your wish
Example:
-Make An ISO EnterpriseS 19041.1 (Tweak as your wish), from this .1 you can go anywhere like this:
https://forums.mydigitallife.net/th...struction-project.80939/page-275#post-1704910

 

Test 20348.1 Windows Server 2022 Datacenter Azure Edition Reconstruction

Code:

WIM Information:
---------------------
GUID:{74703E16-6511-444D-98EF-FE462AD365D8}
Image Count:1
Compression:LZX
Part Number:1/1
Attributes:0x8
RP_FIX

Image Index: 1
-------------------
Name:Windows Server 2022 SERVERTURBINE
Description:Windows Server 2022 SERVERTURBINE
Flags:ServerTurbine
Files:89291
Folders:19404
Expanded Size:13112 MB


WIM XML Information:
---------------------------
<WIM>
  <IMAGE INDEX="1">
    <DIRCOUNT>19404</DIRCOUNT>
    <FILECOUNT>89291</FILECOUNT>
    <TOTALBYTES>13749722397</TOTALBYTES>
    <HARDLINKBYTES>5696596105</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01D7DDBD</HIGHPART>
      <LOWPART>0xFB4B80D4</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01D7DDBD</HIGHPART>
      <LOWPART>0xFB4B80D4</LOWPART>
    </LASTMODIFICATIONTIME>
    <WIMBOOT>0</WIMBOOT>
    <WINDOWS>
      <ARCH>9</ARCH>
      <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
      <EDITIONID>ServerTurbine</EDITIONID>
      <INSTALLATIONTYPE>Server</INSTALLATIONTYPE>
      <SERVICINGDATA>
        <GDRDUREVISION>0</GDRDUREVISION>
        <PKEYCONFIGVERSION>10.0.20348.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>20348</BUILD>
        <SPBUILD>1</SPBUILD>
        <SPLEVEL>0</SPLEVEL>
        <BRANCH>fe_release</BRANCH>
      </VERSION>
      <SYSTEMROOT>WINDOWS</SYSTEMROOT>
    </WINDOWS>
    <NAME>Windows Server 2022 SERVERTURBINE</NAME>
    <DESCRIPTION>Windows Server 2022 SERVERTURBINE</DESCRIPTION>
    <FLAGS>ServerTurbine</FLAGS>
    <DISPLAYNAME>Windows Server 2022 Datacenter Azure Edition</DISPLAYNAME>
    <DISPLAYDESCRIPTION>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.</DISPLAYDESCRIPTION>
  </IMAGE>
  <TOTALBYTES>3648394906</TOTALBYTES>
</WIM>

 

Test 20348.350 Windows Server 2022 Datacenter Azure Edition Reconstruction

Code:

WIM Information:
---------------------
GUID:{74703E16-6511-444D-98EF-FE462AD365D8}
Image Count:1
Compression:LZX
Part Number:1/1
Attributes:0x8
RP_FIX

Image Index: 1
-------------------
Name:Windows Server 2022 SERVERTURBINE
Description:Windows Server 2022 SERVERTURBINE
Flags:ServerTurbine
Files:93747
Folders:22035
Expanded Size:13409 MB


WIM XML Information:
---------------------------
<WIM>
  <IMAGE INDEX="1">
    <DIRCOUNT>22035</DIRCOUNT>
    <FILECOUNT>93747</FILECOUNT>
    <TOTALBYTES>14060707009</TOTALBYTES>
    <HARDLINKBYTES>5732856885</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01D7DDC1</HIGHPART>
      <LOWPART>0x9B937076</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01D7DDC2</HIGHPART>
      <LOWPART>0xBE456E43</LOWPART>
    </LASTMODIFICATIONTIME>
    <WIMBOOT>0</WIMBOOT>
    <WINDOWS>
      <ARCH>9</ARCH>
      <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
      <EDITIONID>ServerTurbine</EDITIONID>
      <INSTALLATIONTYPE>Server</INSTALLATIONTYPE>
      <SERVICINGDATA>
        <GDRDUREVISION>0</GDRDUREVISION>
        <PKEYCONFIGVERSION>10.0.20348.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>20348</BUILD>
        <SPBUILD>350</SPBUILD>
        <SPLEVEL>0</SPLEVEL>
        <BRANCH>fe_release</BRANCH>
      </VERSION>
      <SYSTEMROOT>WINDOWS</SYSTEMROOT>
    </WINDOWS>
    <NAME>Windows Server 2022 SERVERTURBINE</NAME>
    <DESCRIPTION>Windows Server 2022 SERVERTURBINE</DESCRIPTION>
    <FLAGS>ServerTurbine</FLAGS>
    <DISPLAYNAME>Windows Server 2022 Datacenter Azure Edition</DISPLAYNAME>
    <DISPLAYDESCRIPTION>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.</DISPLAYDESCRIPTION>
  </IMAGE>
  <TOTALBYTES>3830136533</TOTALBYTES>
</WIM>

 

You need to login to view this posts content.

 

Thanks for confirming @huynhlam2's shared project!

Is there any advantage to this version compared to the "official reconstruction" released by Microsoft?

In my own mind, I think that starting with the complete 19041.1 package as base means that:

1. Updating is going to produce a "cleaner" less bloated result than the official released version with it's ResetBase of 19044.1288.
2. "Under the hood", the image is more "feature complete" than the fully stripped down official version and so may have better driver/software compatibility
3. You have the freedom to debloat as you like, rather than have to try and add things back that were removed by Microsoft in the official release
4. If you retain the store in your 19041.1 base, then you save the step of integrating the store

However, I'm possibly completely confused and the only purpose to doing this is to have a bit of nerdy fun!

 

You're not confused and these points make sense for some people but not for most. For most it's easier to download official release and update then add store than to mess with all these scripts...

 

All of the above

 

Thank you so much!! You've put my mind at ease. I can finally relax and move forward with updating a couple of workstations that are in desperate need of a clean install.

I do think that in 5 or 6 years, manufactures might stop releasing new GPU and other drivers for Windows 10, but a lot of things can happen by then.

1. Windows 12 is released with a Windows 7 like shell or Windows 11's shell (and other bugs) are finally fixed.
2. Intel actually makes a competitive GPU (three companies competing!). Intel's always been much better at long-term support for their HW which might force the others to follow suite.
3. Coin mining is recognized as the environmental disaster that it is and gets banned!
4. etc.

Remember, you heard it hear first!

 

Your question actually got me thinking (not that I haven't) so I thought of comparing Windows to a house. Some prefer to "buy" a ready built house and just make a few modifications. Others (if they can) prefer to build their own house the way they think it should be.

Update: I think it has to do with mindset. We all have different mindsets. And this applies to everything not just operating systems

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Big thanks for arm64 .1200 archive. I have successfully created and tested arm64 LTSC and IOT LTSC versions.
Server IoT 2022 to follow! Greatest question - x64 only, or with arm64? mmm?

 

Another thing i just remebered is i dont use reconstructed ISOs only. I shift between different Enterprise editions. Same configuration different edition.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

the problem is how can i find original 22000.1 entg and ltsc edition files

 

You need to login to view this posts content.

 

i don't understand how this makes a vanilla Enterprise LTSC 2021 ?, can you explain why you think this

 

You need to login to view this posts content.