[GUIDE] [DISCUSSION] Windows Editions Reconstructions

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

  1. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,674
    14,411
    340
    #861 xinso, Nov 28, 2024
    Last edited: Nov 28, 2024
    Q: How to reconstruct an image exactly the same as official?
    Or
    Q: How to reconstruct LTSC without unwanted\redundant Apps?

    Ask yourself.

    "I can make them all", useless, unless you can make them exactly what they should be, or what you\your followers wish.

    "as is", excuse or obstacle only. It won't help you at all.

    So, start collecting all kinds of script, and studying, and digesting, and applying them in your Reconstructions. Don't stay "as is".

    Learn to fish. Don't wait for fish. Remember. Step by Step, and you'll make it yourself sooner or later. Then you can say, proudly: I did it my way.
     
  2. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    win10 updates are supporting versions as below:

    <assemblyIdentity name="Microsoft-Windows-CoreCountrySpecificEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-CoreEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-CoreNEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-EnterpriseEvalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-EnterpriseGEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-EnterpriseSEvalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEvalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-PPIProEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-ProfessionalNEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-ServerAzureCorEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-ServerDatacenterACorEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-ServerDatacenterNanoEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-ServerStandardACorEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-ServerStandardNanoEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-UtilityVMEdition" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <assemblyIdentity name="Microsoft-Windows-WinPE-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />


    there is no (for example) enterprise n or education above, but every month microsoft releases mvs consumer and business isos which have (for example) enterprise n or education.

    how to understand this?
     
  3. Javac75

    Javac75 MDL Member

    Mar 16, 2015
    167
    196
    10
    @xinso, finally.
    Use windows10.0-kb5046714-x64 license.
     

    Attached Files:

    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    565
    264
    30
    What is this build exactly?

    license? I'm a little confused. :confused:
     
  5. Javac75

    Javac75 MDL Member

    Mar 16, 2015
    167
    196
    10
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Javac75

    Javac75 MDL Member

    Mar 16, 2015
    167
    196
    10
    Yes, the license only.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,674
    14,411
    340
    I have no idea about WinSXSv1.
     
  8. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,674
    14,411
    340
    #870 xinso, Nov 29, 2024
    Last edited: Nov 29, 2024
    Yeah, it's another way. Good job. But you still don't know\get the method I mentioned to combine 22000.1 "LTSC License" and 22000.1 "AC License" in one package.

    "Add" 19041 License "folder", and "Combine" 22000 AC License "package", different outcome when "sysprep" or "rearm".
    Folder will disappear.
    Package will stay.

    [Hint]
    Pro License package is composed of:
    Full Enterprise License Package
    +
    Other Editions' License packages

    Core License package is composed of:
    Full Core License Package
    +
    CoreSingleLanguage's License package

    "Combine package", not "Add folder".
     
  9. Javac75

    Javac75 MDL Member

    Mar 16, 2015
    167
    196
    10
    Yes, thanks.
    I'm confused about that combination.
    Actually I just realized that what you meant was a combination.
    What is AC? Enlighten me, please.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,674
    14,411
    340
    #872 xinso, Nov 29, 2024
    Last edited: Nov 29, 2024
    [LTSC]
    EnterpriseS\EnterpriseSN\IoTEnterpriseS\IoTEnterpriseSK = Long Term Servicing Channel (5 or 10 years)

    [AC]
    Core\Professional = Annual Channel (24 or 30 months)

    And PPIPro (Windows Team), another Channel.
    And CMGE EnterpriseG? (Contracts between Microsoft and CMIT)

    [Hint]
    PPIPro is based on top of Enterprise. But PPIPro is not limited by AC update. It has its own update life cycle.
     
  11. Javac75

    Javac75 MDL Member

    Mar 16, 2015
    167
    196
    10
    Ah, I already understand what you mean. Later it will be like a pro or enterprise license which is a collection of licenses for various SKUs. Is it really like that?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,674
    14,411
    340
    #874 xinso, Nov 29, 2024
    Last edited: Nov 29, 2024
    If you meant "Parent" and "Virtual" editions, yes.
     
  13. Javac75

    Javac75 MDL Member

    Mar 16, 2015
    167
    196
    10
    What I mean by this is that in the end there will be a package containing a collection of various SKU licenses.
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-CloudEdition-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-CloudEdition-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalEducation-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalEducation-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalWorkstation-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalWorkstation-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-Education-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Education-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalCountrySpecific-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalCountrySpecific-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalSingleLanguage-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ProfessionalSingleLanguage-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-ServerRdsh-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ServerRdsh-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterprise-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-Professional-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Professional-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package" version="10.0.22000.2600" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,674
    14,411
    340
    #876 xinso, Nov 29, 2024
    Last edited: Nov 29, 2024
    Yes. But that structure will show AC Edition IDs, not LTSC. Correct Edition ID needs both "License" and "EditionMatrix.xml" to work together.

    (dism /online /get-currentedition)

    [Hint]
    License is controlled by "License" package.
    EditionMatrix.xml is controlled by "Editions" package.
    Both matched = Edition ID displayed
    Both mismatched = No ID

    PS:
    It depends on "build". e.g.

    Check if your 22000 LTSC would show correct Edition ID by "dism /online /get-currentedition".
    I answer for you: Yes, even not matched. e.g. 22000.1 License + 22000.3260 Edition.

    Check if your 22621 LTSC would show correct Edition ID by "dism /online /get-currentedition".
    I answer for you: No, if not matched. e.g. 22621.1 License + 22621.4541 Edition.

    Check if your 19044\26100 LTSC would show correct Edition ID by "dism /online /get-currentedition".
    I answer for you: Yes. Because it is officially supported. They will match anyway.
     
  15. Javac75

    Javac75 MDL Member

    Mar 16, 2015
    167
    196
    10
    #877 Javac75, Nov 29, 2024
    Last edited: Nov 29, 2024
    Editions package content manifest file only.
    So, we will need many specific edition packages to get the combination. Is it right?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Javac75

    Javac75 MDL Member

    Mar 16, 2015
    167
    196
    10
    upload_2024-11-29_10-51-16.png
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,674
    14,411
    340
    #879 xinso, Nov 29, 2024
    Last edited: Nov 29, 2024
    Patiently waitng for zwl29107's new 25398 CUs.
     
  18. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,674
    14,411
    340
    #880 xinso, Nov 29, 2024
    Last edited: Nov 29, 2024
    To be honest, I can't quite understand your sentences.

    For WinX on 22000.1 LTSC, this is the way I use.

    Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
    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-EnterpriseS-SPP-Components-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <package identifier="Microsoft-Windows-EnterpriseS-SPP-Components-Package" releaseType="Feature Pack">
        <update name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
      </package>
    </assembly>
    
    +
    Code:
        <update name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-License-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-License-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
          </package>
        </update>
    
    ---> 22000.1 Enterprise License that supports Windows 11 WinX menu
    Code:
    Microsoft-Windows-Security-SPP-Component-SKU-Enterprise-License-Package