[GUIDE] [DISCUSSION] Windows Editions Reconstructions

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

  1. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    612
    340
    30
    That's what I'm going to try now..

    Although I just need to edit the Core Edition Pack in the same style as Starter to have results similar to Starter but in Home (core)

    The modifications made to the .mum files were as follows:

    Microsoft-Windows-Security-SPP-Component-SKU-Core-Default-Package: (they were taken as Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package and cat only their name was changed to Core)

    Code:
    <?xml version="1.0" encoding="utf-8" standalone="yes"?>
    <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved.">
      <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Core-Default-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
      <package identifier="Microsoft-Windows-Security-SPP-Component-SKU-Core-Default-Package" releaseType="Feature Pack">
        <update name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Deployment">
          <component>
            <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Deployment" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
          </component>
        </update>
      </package>
    </assembly>
    Microsoft-Windows-CoreEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum (sytle Starter)
    Code:
    <?xml version="1.0" encoding="utf-8" standalone="yes"?>
    <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved.">
      <assemblyIdentity name="Microsoft-Windows-CoreEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <package identifier="Windows Core Edition" releaseType="Product">
        <update name="Microsoft-Windows-Foundation-Package">
          <package contained="false" integrate="visible">
            <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-EditionSpecific-Core-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionSpecific-Core-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Client-Desktop-Required-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Win4-Feature">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Win4-Feature" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Win4-WOW64-Feature">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Win4-WOW64-Feature" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Client-Features-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Client-Features-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Client-Features-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Client-Features-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-EditionPack-Core-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionPack-Core-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-EditionPack-Core-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionPack-Core-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
      </package>
    </assembly>
     
  2. liliactr

    liliactr MDL Addicted

    Sep 3, 2009
    578
    204
    30
    #423 liliactr, Sep 30, 2024
    Last edited: Sep 30, 2024
    Windows 11 Starter does not updates. But when upgraded to another edition it successfully updates. Can be related to in there writes "Windows 10 Starter"?

    Also is there any way to activate it?

    Users that use Windows 11 EnterpriseG in english or chineese does it updates?
     
  3. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,876
    1,546
    60
    You are correct Starter (Edition Specific Packages) will not update, but with custom update all other packages can be updated.

    Yes Starter can be activated.

    Yes Enterprise G can be updated online for english & chineese version.
     
  4. liliactr

    liliactr MDL Addicted

    Sep 3, 2009
    578
    204
    30
    #425 liliactr, Sep 30, 2024
    Last edited: Sep 30, 2024
    Which tool activates starter?

    I had an idea and all day worked on enterpriseg again. After editing EnterpriseG-ppdlic.xrm-ms. cbs hash check does not let updates. but if ever licensing package removed from install.wim? So there will be not EnterpriseG-ppdlic.xrm-ms at cbs store Will not be such package and dism will not check EnterpriseG-ppdlic.xrm-ms hash. EnterpriseG-ppdlic.xrm-ms will not be updated and will not be need to patch it again. Build can be used at any language with updateable then.

    I am mosty succeded. I have created a build that has not Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseG-License-Package. It can install and boot without problem. But updates not works. I could not track the error code from dism and cbs.logs. Not much explainful. It looks like updates not enabled for enterpriseg edition. For to be sure i want to see an updated windows 11 enterpriseg picture if anybody uses it. Updated in normal ways, not with patched updates
     
  5. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,876
    1,546
    60
    i don't see CU for OS installed, only CU for .NET Framework is installed...
     
  6. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    612
    340
    30
    Do you know how much a CU update weighs? I don't have a fast enough internet connection to download.

    For now I'm here with the virtual machine active waiting for download..

    As for the rest, I'm still checking and testing.
     
  7. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,876
    1,546
    60
    looks like it was downloading fine to me,..:p
     
  8. TK50P

    TK50P MDL Junior Member

    May 29, 2023
    50
    9
    0
  9. Low Level Perform

    Low Level Perform MDL Junior Member

    Jul 21, 2024
    52
    34
    0
    I made a reconstruction of the script made by @xinso 25398.1_Neutral_to_Client_amd64_38in1_26100_License, but Win-X does not work in the LTSC version.

    has this script been updated?
    I've forgotten what page I downloaded it on.

    or can someone fix Win-X LTSC that doesn't work
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
  11. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,408
    2,592
    120
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. winosr25

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
    hello the packages are complete, for the server version
     
  13. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,876
    1,546
    60
    iamaHUN

    ProfessionalN_to_EnterpriseSN_26100.1_x64.7z looks good, seems to match Microsoft-Windows-EnterpriseSNEdition 26100.1 Sessions.xml taken from professionaln_en-us.esd [26100.1].