[ARCHIVED] Windows Editions Reconstruction Project

Discussion in 'Windows 10' started by whatever127, Jan 10, 2020.

Thread Status:
Not open for further replies.
  1. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Can you explain, the time stamp of what? Some file modification date? Or the WIM creation time stamp?
    What should I set as time stamp if I want it work?
    Thanks!
     
  2. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    This, I can't make it. But you can change image creation time. Please search help from the Masters.
     
  3. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
  4. HLP Mr. Lin Yu

    HLP Mr. Lin Yu MDL Junior Member

    Jul 22, 2022
    94
    46
    0
    #16724 HLP Mr. Lin Yu, Jun 30, 2024
    Last edited: Jun 30, 2024
    Hello, is there anyone who might be able to teach me how to convert 22000 and 22631 to EnterpriseS versions?
    I want to do this but have no clue.
     
  5. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
  6. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
  7. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #16728 xinso, Jul 1, 2024
    Last edited: Jul 1, 2024
    LTSC Evaluation reconstruction,
    if by hand, OK,
    if by script, not OK.

    Why? Same processes. One is step by Step, One is Steps in a row.

    It needs tea time? How long?

    Any tweak like that of Starter?
     
  8. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Master, do you have ARM64 Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~arm64~~10.0.26100.1 MUM/CAT to share?
     
  9. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Well, technically LTSC editions for 22000 and 22621 have not been built, so even if you reconstruct that, they won't update. EnterpriseG is more elegant - same light style, but updates normally.
    Yarrak31 has promised last page to help with any edition. I may help with EnterpriseG if needed, - 19041/22000/22621/26100. Today have decided to try ARM64 first time in my life, - would see what happens )
     
  10. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    I am not Master. But I believe it should be like this.

    1. Rename
    Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~arm64~~10.0.26100.1.cat
    Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~arm64~~10.0.26100.1.mum
    --->
    Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~arm64~~10.0.26100.1.cat
    Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~arm64~~10.0.26100.1.mum

    2. Modify the EnterpriseG mum structure as this:
    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-EnterpriseGEdition" version="10.0.26100.1" processorArchitecture="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <package identifier="Windows EnterpriseG 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="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-EditionSpecific-EnterpriseG-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionSpecific-EnterpriseG-Package" version="10.0.26100.1" processorArchitecture="arm64" 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="arm64" 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="arm64" 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="arm64" 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="arm64" 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="arm64" 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="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-CHPE-Binaries-arm64x86-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-CHPE-Binaries-arm64x86-Package" version="10.0.26100.1" processorArchitecture="arm64.x86" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-EditionPack-Professional-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-Package" version="10.0.26100.1" processorArchitecture="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-EditionPack-Professional-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-WOW64-Package" version="10.0.26100.1" processorArchitecture="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-RegulatedPackages-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-Package" version="10.0.26100.1" processorArchitecture="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-RegulatedPackages-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-WOW64-Package" version="10.0.26100.1" processorArchitecture="arm64" 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="arm64" 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="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
      </package>
    </assembly>
    
     
  11. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Thank you, appreciate your help!
     
  12. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
  13. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #16734 xinso, Jul 1, 2024
    Last edited: Jul 1, 2024
    Test 26244.5000 Windows Server 2025 Datacenter amd64 en-US
    Code:
    C:\WINDOWS\system32>dism /english /logpath:z:\1.log /image:K: /apply-unattend:Z:\WinSxS\1.xml
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.26100.1
    
    Applying package servicing unattend
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /english /image:K: /add-package:Z:\WinSxS\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.26244.5000.mum
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.26244.5000
    
    Processing 1 of 1 - Adding package Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.26244.5000
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /english /image:K: /add-package:Z:\WinSxS\Microsoft-Windows-LanguageFeatures-Basic-en-US-Package~31bf3856ad364e35~amd64~~10.0.26244.5000.mum
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.26244.5000
    
    Processing 1 of 1 - Adding package Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.26244.5000
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /english /image:K: /add-package:Z:\WinSxS\Microsoft-Windows-LanguageFeatures-Handwriting-en-US-Package~31bf3856ad364e35~amd64~~10.0.26244.5000.mum
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.26244.5000
    
    Processing 1 of 1 - Adding package Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.26244.5000
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /english /image:K: /add-package:Z:\WinSxS\Microsoft-Windows-LanguageFeatures-OCR-en-US-Package~31bf3856ad364e35~amd64~~10.0.26244.5000.mum
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.26244.5000
    
    Processing 1 of 1 - Adding package Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.26244.5000
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /english /image:K: /add-package:Z:\WinSxS\Microsoft-Windows-LanguageFeatures-Speech-en-US-Package~31bf3856ad364e35~amd64~~10.0.26244.5000.mum
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.26244.5000
    
    Processing 1 of 1 - Adding package Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~10.0.26244.5000
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /english /image:K: /add-package:Z:\WinSxS\Microsoft-Windows-LanguageFeatures-TextToSpeech-en-US-Package~31bf3856ad364e35~amd64~~10.0.26244.5000.mum
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.26244.5000
    
    Processing 1 of 1 - Adding package Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package~31bf3856ad364e35~amd64~~10.0.26244.5000
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /english /image:K: /set-skuintldefaults:en-US
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.26244.5000
    
    
    Set SKU default settings for: en-US
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /english /image:K: /get-currentedition
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.26244.5000
    
    Current edition is:
    
    Current Edition : ServerDatacenter
    
    The operation completed successfully.
    
    C:\WINDOWS\system32>
    
     
  14. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
  15. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #16736 xinso, Jul 1, 2024
    Last edited: Jul 1, 2024
    Old official "Unstaged" is barebone. Have you ever seen any new build?
     
  16. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Can you explain what is meant by Unstaged?
    an image with many SKUs, where the serial defines what to install? Or something different?
    Thanks
     
  17. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,047
    90
    this is how the image install.wim looks shipped from ms

    packages are uncompressed unlike winsxs

    and windows directory is having just servicing stack installed

    look for 19100.1051.210916-1011.VB_RELEASE_SVC_TEAM_FLIGHT_CLIENTUNSTAGED_RETAIL_X64FRE_EN-US.iso

    or many unstage isos in windows beta archives
     

    Attached Files:

  18. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Are the stable builds (19041, 22621, 26100) posted unstaged?
     
  19. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,047
    90
    duno, ig internally