[ARCHIVED] Windows Editions Reconstruction Project

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

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

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
    hello, I have just successfully rebuilt enterpriseG 26100.1, a mixture of 26090.1 26090.112 26100. and the kb update from 26090.1 to 26090.112 in the source.esd file.

    an error occurred during key integration
    message: file descriptor supplied is invalid

    please help us to correct it

    Code:
    ============================================================
    export base image
    ============================================================
    
    
    ============================================================
    Mount  image
    ============================================================
    
    
    ============================================================
    Remove System Notepad
    ============================================================
    
    
    ============================================================
    Convert  to EnterpriseG
    ============================================================
    
    
    ============================================================
    add lang
    ============================================================
    
    
    Outil Gestion et maintenance des images de déploiement
    Version : 10.0.19041.3636
    
    Version de l’image : 10.0.26100.1
    
    Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
    [==========================100.0%==========================]
    L’opération a réussi.
    
    ============================================================
    Set EnterpriseG key
    ============================================================
    
    
    Outil Gestion et maintenance des images de déploiement
    Version : 10.0.19041.3636
    
    Version de l’image : 10.0.26100.1
    
    file descriptor supplied is invalid.
    
    Finished installing product key.
    
    L’opération a réussi.
     
  2. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #16742 xinso, Jul 1, 2024
    Last edited: Jul 4, 2024
    1. "mixture" must not exist.

    2. file descriptor supplied is invalid. (提供的檔案控制代碼無效。Try "dism /english" to eliminate it.)
    Code:
    ------------------------------------------------------------
    Set EnterpriseG key
    ------------------------------------------------------------
    
    部署映像服務與管理工具
    版本: 10.0.19041.844
    
    映像版本: 10.0.26100.1
    
    提供的檔案控制代碼無效。
    
    Finished installing product key.
    
    操作順利完成。
    
    --->
    Code:
    echo.
    echo ------------------------------------------------------------
    echo Set %TARGET% key
    echo ------------------------------------------------------------
    dism /english /image:%MT% /set-productkey:%KEY%
    
    --->
    Code:
    ------------------------------------------------------------
    Set EnterpriseG key
    ------------------------------------------------------------
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.25398.1
    
    Starting to install product key...
    Finished installing product key.
    
    The operation completed successfully.
    
    To sum it up:
    Your problem is "mixture".

    PS:
    26100.1 is "Full" release, and EnterpriseG is also "Fully" supported, no need of 26090. So, you need two things for 26100.1 EnterpriseG reconstruction:

    1. from 26100 UUP
    Microsoft-Windows-EditionSpecific-EnterpriseG-Package.ESD

    2. from 26090.1 to 26100.1
    microsoft-windows-enterprisegedition~31bf3856ad364e35~amd64~~10.0.26090.1.cat
    microsoft-windows-enterprisegedition~31bf3856ad364e35~amd64~~10.0.26090.1.mum
    --->
    Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.1.cat
    Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.26100.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-EnterpriseGEdition" version="10.0.26100.1" processorArchitecture="amd64" 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="amd64" 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="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-Professional-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-Package" version="10.0.26100.1" processorArchitecture="amd64" 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="amd64" 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="amd64" 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="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>
    
     
  3. winosr25

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
    thank you problem resolut with: dism /english
     
  4. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #16745 xinso, Jul 2, 2024
    Last edited: Jul 2, 2024
    At MDL, any "Homebrewed" is not allowed to share directly from MDL.
     
  5. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #16746 xinso, Jul 2, 2024
    Last edited: Jul 2, 2024
    It's really weird. Any 26100.1 Evaulation reconstruction will ruin activation.
     
  6. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Master, I seek for your help.
    Have recreated 19041.1 x64 G image few different ways, as you teached - works perfectly.
    If I create a VM and install, - I can get any updates from WU.
    But I still fail integrating updates to install.wim.
    I have tried not just the latest 4598, but also 4593 - same result, - fail on last minute of installation stage. If I create a VHD with Convert-WindowsImage, system bluescreens on boot.

    I have tried not just W10UI, - as you said a 3d party util, but just adding SSU + LCU to install.wim brings me to same problem each time.
    That is clearly an exercise of course, but I can't understand what is wrong.
    Am not asking for your scripts or images, but can you make a look and create an updated G image on your side? Would 19045.4598 amd64 G install?
    Thanks!
     
  7. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #16748 xinso, Jul 2, 2024
    Last edited: Jul 2, 2024
    Could you please post link of 19041.1 x64 EnterpriseG script?
     
  8. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Don't you know, if updating WIM with the appxpackages cleaned (clean.cmd) can be a source of problems?
     
  9. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
  10. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    clean.cmd is your script - part of enterpriseg_19041_x64 package? That is why I am asking

    After creating image you clean APPX packages:
    Code:
    dism /logpath:logs\appx.log /scratchdir:"%~dp0TEMP" /image:mount /remove-provisionedappxpackage /packagename:Microsoft.549981C3F5F10_1.1911.21713.0_neutral_~_8wekyb3d8bbwe || exit /b 1
    .... and other packages.

    May I face problems updating image with cleaned APPX packages?
     
  11. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Thank you for your time!
     
  12. xinso

    xinso MDL Guru

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

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    I see.
    Can I make a look on 19041.1_Pro_to_EntG_x86_x64_a64_en-US_zh-CN_CMGE_Style script?
     
  14. xinso

    xinso MDL Guru

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

    Yarrak31 MDL Senior Member

    Feb 28, 2024
    419
    112
    10
  16. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    Sir, I missed a reply, - working hours :(
     
  17. liliactr

    liliactr MDL Addicted

    Sep 3, 2009
    528
    187
    30
    Please update your script to be capable to add mum files to OFFLINE image too. There is no offline image choice. I need that.
     
  18. liliactr

    liliactr MDL Addicted

    Sep 3, 2009
    528
    187
    30
    For to batch rename folders, files, inside manifests, inside mums. I have found and edited some scripts. i am not good at it but maybe can be usefull. Does it need to edit inside .cat files? Should be need binary editing. I am not capable of that yet.Put inside sxs folder. Edit string1, string2 inside batches and give as parameters for folder renaming.bat. Maybe somebody can merge them and improve them inside in a single batch.
     

    Attached Files: