[GUIDE] [DISCUSSION] Windows Editions Reconstructions

Discussion in 'Windows 10' started by TesterMachineOS, Sep 3, 2024.

  1. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1821 xinso, Apr 6, 2025
    Last edited: Apr 7, 2025
    It's not available in the image.
     
  2. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1822 xinso, Apr 6, 2025
    Last edited: Apr 7, 2025
    I downloaded it to make sure, it is fine.
     
  3. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    645
    116
    30
    nevermind. i made it :)

    waiting for gailium 20348 tool
     
  4. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1824 xinso, Apr 7, 2025
    Last edited: Apr 7, 2025
    No 26100.1 compatible build. Weird.
     
  5. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1826 xinso, Apr 7, 2025
    Last edited: Apr 7, 2025
    Let Client and Server help each other.
     
  6. ohault

    ohault MDL Member

    Dec 27, 2022
    227
    71
    10
    I know, that’s why I’m asking these questions.
     
  7. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1828 xinso, Apr 8, 2025
    Last edited: Apr 8, 2025
    I'd tried to construct it without that Microsoft Insider package, it worked, yes, but it won't boot.
     
  8. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1829 xinso, Apr 8, 2025
    Last edited: Apr 8, 2025
    pp03 is waiting for gailium's 20348.1 script.

    Me too.
     
  9. ohault

    ohault MDL Member

    Dec 27, 2022
    227
    71
    10
    I would start if an image that is known to boot like WinPE, ValidationOS, or the Nano Server 2016 because Windows Containers do not exactly boot, it is another story.
     
  10. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1831 xinso, Apr 8, 2025
    Last edited: Apr 8, 2025
    I don't understand what "I would start" meant.

    Did you mean:
    If an image that is known to boot like WinPE, ValidationOS, or the Nano Server 2016, you would start to use any one of them to reconstruct?

    If yes, I had stated that the target image been reconstructed with any of them won't boot, if missing Microsoft Insider Package.
     
  11. Mooniversal

    Mooniversal MDL Novice

    Jul 9, 2020
    29
    16
    0
    Can you share 20348's EnterpriseS's WinSXS files needed for reconstruction of Server + Client 2 in 1?
    Even with WinExp and PureSXS I still can't figure out which files to extract >_<
     
  12. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1833 xinso, Apr 8, 2025
    Last edited: Apr 8, 2025
    It is located in gailium119's 20348.1.210507-1500.FE_RELEASE_CLIENT_SERVER_ALLEDITIONS_X64FRE_ZH-CN.ISO.
    https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-90#post-1874983

    Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.20348.1
    Or
    Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.20348.1

    PS:
    1. gailium119 will share 20348.1 Reconstruction script.
    2. Two weapons for Reconstruction: sxsexp and pureSxS.py

    [ESource Preparation by 7-zip]
    Extract Windows\WinSxS to WinSxS
    Extract Windows\WinSxS\Manifests to WinSxS
    Extract Windows\servicing\Packages to WinSxS

    [Source Expansion and Package Extraction]
    1. Firstly, sxsexp. (expand WinSxS folder)
    2. Secondly, pureSxS.py. (Extract packages from WinSxS folder)
    3. Lastly, capture extracted package folder(s) to esd(s).
     
  13. Mooniversal

    Mooniversal MDL Novice

    Jul 9, 2020
    29
    16
    0
    @xinso

    This image already has a Windows edition installed. There cannot be more than one installed Windows edition in an image.

    I can't seem to have both versions installed at the same time

    How can I make it so it installs Pro on top of ServerDatacenter edition? To have both editions at once?

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <servicing>
    <package action="install">
    <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.20348.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
    <source location="Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.20348.1.mum" />
    </package>
    </servicing>
    </unattend>
     
  14. sakatgg

    sakatgg MDL Junior Member

    Jun 18, 2020
    55
    34
    0
    #1835 sakatgg, Apr 8, 2025
    Last edited: Apr 8, 2025
    After SXSEXP all folders will be empty and there will be no *.cat and *.mum
    At least I don't know how to make SXSEXP automatically copy the rest of the files

    You have to copy decompressed *.manifest back with replacement and then pureSxS

    SXSEXP only decompressed *.manifest - it does this perfectly.

    I have no doubt that you are aware of this, but for newcomers to the topic this is an important point.and can be confusing
     
  15. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    Windows, Client and Server must be seperated.
    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <servicing>
            <package action="install">
                <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.20348.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
    <source location="Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.20348.1.mum" />
            </package>
            <package action="remove">
                <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEdition" version="10.0.20348.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
            </package>
        </servicing>
    </unattend>
    
     
  16. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1837 xinso, Apr 8, 2025
    Last edited: Apr 8, 2025
    [Step 3-1]
    All components from those three mentioned folders should be in WinSxS folder.
    e.g.
    Step a. By 7-zip, open target index of install.wim.
    Step b. Select Windows\WinSxS ---> Extract to C:\WinSxS.
    Step c. Open Windows\WinSxS\Manifests ---> Select all ---> Extract to C:\WinSxS.
    Step d. Open Windows\servicing\Packages ---> Select all ---> Extract to C:\WinSxS.

    [Step -3-2]
    Expand the WinSxS folder to another folder, e.g. expanded.

    [Step 3-3]
    Xcopy expanded folder back to WinSxS.

    SxSExpand.cmd
    Code:
    @echo off
    pushd "%~dp0"
    
    set SourceFolder=C:\winsxs
    set TargetFolder=expanded
    
    if exist %TaregetFolder% (rd /s /q %TaregetFolder%&md %TargetFolder%) else (md %TargetFolder%)
    
    files\sxsexp-amd64.exe %SourceFolder% %TargetFolder%
    
    xcopy /S /E /I /H /R /Y /J %TargetFolder% %SourceFolder%
    rd /s /q %TargetFolder%
    
    :END
    pause
    exit
    
     
  17. Mooniversal

    Mooniversal MDL Novice

    Jul 9, 2020
    29
    16
    0
    I want both ServerDatacenterEdition and ProfessionalEdition to be installed at same time so I can install CU updates.
     
  18. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,996
    14,658
    340
    #1839 xinso, Apr 8, 2025
    Last edited: Apr 8, 2025
    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <servicing>
            <package action="stage">
                <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEdition" version="10.0.20348.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
            </package>
            <package action="install">
                <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.20348.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
    <source location="Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.20348.1.mum" />
            </package>
        </servicing>
    </unattend>
    
    --->
    Add ServerDatacenter Key to set "ServerDatacenter" as default Edition, so that CU can be installed "Offline".
    --->
    Switch to Client by adding Target Edition Key.
    --->
    Forget about "EditionID" or "Branding".

    PS:
    Under such circumstance, I usually backup Branding folder of both Client and Server. And restore to ServerDatacenter when next CU is to be added.
    e.g.
    C:\Windows\Branding-ServerDatacenter
    C:\Windows\Branding-Professional
    C:\Windows\Professional or ServerDatacenter

    This is more hassle than regular Reconstruction, isn't it?
    Add Client License and Key to official Server is the most easy way which won't affect Windows Update Online or install CU Offline.
    And no need to worry about Branding and EditionID which may lead to next CU failure.
     
  19. Mooniversal

    Mooniversal MDL Novice

    Jul 9, 2020
    29
    16
    0
    Server edition got erased even when using the 1.xml you sent... only ServerRdshEdition got left... I've spent all day tinkering with this stuff that I got a terrible headache. I'll just wait for gailium119 script >_<