[GUIDE] [DISCUSSION] Windows Editions Reconstructions

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

  1. Ace2

    Ace2 MDL Guru

    Oct 10, 2014
    2,206
    1,909
    90
    Code:
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    Mount image
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Clean Microsoft-Windows-EditionPack-Core-WOW64-Package
    ============================================================
    
            1 file(s) copied.
            1 file(s) copied.
    remove Microsoft-Windows-WinPE-SKU-Foundation-WOW64-merged-Package
    remove Microsoft-Windows-WinPE-SKU-Foundation-merged-Package
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    convert 28000.1
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Image Version: 10.0.28000.1
    
    Removing package Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.28000.1
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Image Version: 10.0.28000.1
    
    Processing 1 of 1 - Adding package Microsoft-Windows-Defender-Removal-Package~31bf3856ad364e35~amd64~~10.0.32767.1
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Image Version: 10.0.28000.1
    
    Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.28000.1
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Image Version: 10.0.28000.1
    
    
    Set SKU default settings for: en-us
    The operation completed successfully.
    
    ============================================================
    clean image
    ============================================================
    
    
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    add Winosr25
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Applying image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Image Version: 10.0.28000.1
    
    Starting to install product key...
    Finished installing product key.
    
    The operation completed successfully.
            1 file(s) copied.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Image Version: 10.0.28000.1
    
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    The operation completed successfully.
    
    ============================================================
    reset base
    ============================================================
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Image Version: 10.0.28000.1
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Save and Unmount image
    ============================================================
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.26100.1150
    
    Image File : C:\winosrpe\winpe.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Press any key to continue . . .
    [Credit]
    winosr25
     
  2. pp03

    pp03 MDL Expert

    Apr 12, 2014
    1,482
    524
    60
    #3862 pp03, Dec 24, 2025
    Last edited: Dec 24, 2025
    C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\mount.log /mount-wim /wimfile:winre.wim /index:1 /mountdir:mount || exit /b 1

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792

    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.

    C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\1.log /scratchdir:"C:\Users\LocalAdmin\Downloads\22621\temp" /image:mount /apply-unattend:1.xml || exit /b 1
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792

    Image Version: 10.0.22621.1

    Removing package Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.22621.1
    Removing package Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.22621.1
    [==========================100.0%==========================]

    The operation completed successfully.

    C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\2.log /scratchdir:"C:\Users\LocalAdmin\Downloads\22621\temp" /image:mount /add-package /packagepath:lp || exit /b 1

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792

    Image Version: 10.0.22621.1

    Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~pl-PL~10.0.22621.1
    [==========================100.0%==========================]
    The operation completed successfully.

    C:\Users\LocalAdmin\Downloads\22621>copy mount\Windows\servicing\Editions\EnterpriseEvalEdition.xml mount\Windows\EnterpriseEval.xml
    1 file(s) copied.

    C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\3.log /scratchdir:"C:\Users\LocalAdmin\Downloads\22621\temp" /image:mount /apply-unattend:mount\Windows\EnterpriseEval.xml || exit /b 1

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792

    Image Version: 10.0.22621.1

    The operation completed successfully.

    C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\4-currentedition.log /scratchdir:"C:\Users\LocalAdmin\Downloads\22621\temp" /image:mount /get-currentedition /english || exit /b 1

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792

    Image Version: 10.0.22621.1

    Current edition is:

    Current Edition : EnterpriseEval

    The operation completed successfully.

    C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\5-targetedition.log /scratchdir:"C:\Users\LocalAdmin\Downloads\22621\temp" /image:mount /get-targeteditions /english || exit /b 1

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792

    Image Version: 10.0.22621.1

    Editions that can be upgraded to:

    (The current edition cannot be upgraded to any target editions.)

    The operation completed successfully.

    edit: error 87 add-package option is unknown

    "Failed to create a new GUID folder for servicing stack shim" in log

    edit: fix https://forums.mydigitallife.net/th...s-reconstructions.88605/page-194#post-1900550
     
  3. pp03

    pp03 MDL Expert

    Apr 12, 2014
    1,482
    524
    60
    #3863 pp03, Dec 24, 2025
    Last edited: Dec 24, 2025
    i prefer zhanglin winre method - no ramdisk
     
  4. winosr25

    winosr25 MDL Senior Member

    May 14, 2024
    442
    547
    10
    WinPE for my code, not WinRE
     
  5. pp03

    pp03 MDL Expert

    Apr 12, 2014
    1,482
    524
    60
    in zhanglin method winre.wim is mounted and winpe-package is removed
     
  6. Ace2

    Ace2 MDL Guru

    Oct 10, 2014
    2,206
    1,909
    90
    :Feedback

    Winosr25 skus doesn't work with slmgr -rilc, slmgr -ipk, Change product key (Activation page), and No product key found in Activation page after installing new winpe.wim

    All other available skus work.
     
  7. pp03

    pp03 MDL Expert

    Apr 12, 2014
    1,482
    524
    60
    #3867 pp03, Dec 24, 2025
    Last edited: Dec 24, 2025
  8. xinso

    xinso MDL Guru

    Mar 5, 2009
    15,089
    15,292
    340
    #3868 xinso, Dec 25, 2025
    Last edited: Dec 25, 2025
    Congrats.

    Q: The WinRE.wim is original image or just neutral System?

    "Neutral" means "Barebone System", without Features and Language packs.
     
  9. zhanglin

    zhanglin MDL Expert

    Jan 11, 2018
    1,058
    623
    60
    These errors appear in dism.log
    "Failed to create a new GUID folder for servicing stack shim"
    "edit: error 87 add-package option is unknown"

    The reason is the absence of the Windows\Temp folder.
    WinRE.wim has this Windows\Temp folder.
    If it doesn't, this step won't succeed either.

    Code:
    C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\2.log /scratchdir:"C:\Users\LocalAdmin\Downloads\22621\temp" /image:mount /add-package /packagepath:lp || exit /b 1
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~pl-PL~10.0.22621.1
    [==========================100.0%==========================]
    The operation completed successfully.
    Code:
    C:\Users\LocalAdmin\Downloads\22621>dism /logpath:logs\4-currentedition.log /scratchdir:"C:\Users\LocalAdmin\Downloads\22621\temp" /image:mount /get-currentedition /english || exit /b 1
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792
    
    Image Version: 10.0.22621.1
    
    Current edition is:
    
    Current Edition : EnterpriseEval
    
    The operation completed successfully.
     
  10. xinso

    xinso MDL Guru

    Mar 5, 2009
    15,089
    15,292
    340
    #3870 xinso, Dec 25, 2025
    Last edited: Dec 25, 2025
    My 10240\14393 does not have Windows\Temp.

    OK. Let me try 17763 without it.
    Code:
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.17763.1
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    So, it depends. What exactly? No idea.

    22621.1. For disk space, I had deleted all AC scripts, no way to test them.

    But I keep their base image. OK. Let me test 22621.1 by hand.

    [without Windows\Temp]
    Code:
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    
    Error: 0x80004005
    
    DISM failed. No operation was performed.
    For more information, review the log file.
    
    The DISM log file can be found at z:\1.log
    
    [with Windows\Temp]
    Code:
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    So, it depends on "Build".
     
  11. zhanglin

    zhanglin MDL Expert

    Jan 11, 2018
    1,058
    623
    60
    It happened several years ago, and I can't remember from which version it started requiring Windows\Temp.

    Simple method, did get-CurrentEdition succeed?
     
  12. xinso

    xinso MDL Guru

    Mar 5, 2009
    15,089
    15,292
    340
    #3872 xinso, Dec 25, 2025
    Last edited: Dec 25, 2025
    Yes.
    Code:
    C:\windows\system32>dism /english /logpath:z:\1.log /image:K: /get-currentEdition
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Current edition is:
    
    Current Edition : EnterpriseS
    
    The operation completed successfully.
    
    Code:
    C:\windows\system32>dism /english /image:K: /get-targeteditions
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Editions that can be upgraded to:
    
    Target Edition : IoTEnterpriseS
    
    The operation completed successfully.
    
    C:\windows\system32>
    
    Code:
    C:\windows\system32>dism /english /image:K: /set-edition:IoTEnterpriseS
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Starting to update components...
    Starting to install product key...
    Finished installing product key.
    
    Starting to apply edition-specific settings...
    Finished applying edition-specific settings.
    
    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.22621.1
    
    Current edition is:
    
    Current Edition : IoTEnterpriseS
    
    The operation completed successfully.
    
    C:\windows\system32>
    
     
  13. xinso

    xinso MDL Guru

    Mar 5, 2009
    15,089
    15,292
    340
    #3873 xinso, Dec 25, 2025
    Last edited: Dec 25, 2025
    Q: Can your Windows, reconstructed with WinRE, boot to Desktop? (You did not test installation, did you?)

    Reconstruction is one thing. Installation is one thing. Applicability is one thing.

    e.g.
    We can reconstruct an image with PPIPro. But the installation won't boot to Desktop. Let alone applicability.
     
  14. xinso

    xinso MDL Guru

    Mar 5, 2009
    15,089
    15,292
    340
  15. pp03

    pp03 MDL Expert

    Apr 12, 2014
    1,482
    524
    60
    #3875 pp03, Dec 25, 2025
    Last edited: Dec 25, 2025
  16. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,875
    3,149
    120
    Integration are offline only ?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. pp03

    pp03 MDL Expert

    Apr 12, 2014
    1,482
    524
    60
    yes
     
  18. TK50P

    TK50P MDL Member

    May 29, 2023
    191
    95
    10
    #3878 TK50P, Dec 25, 2025
    Last edited: Dec 25, 2025
    Trying to Apply LCU for EnterpriseG ARM64 26100, 26100.7462 Failed to report SKU
    Code:
    PS C:\EnterpriseG-Reconstruction> Dism /Scratchdir=C:\Scratched /Image:mount /add-package /packagepath:C:\Windows11.0-KB5043080-arm64\update.mum /LogPath:C:\LCU1742.log
    
    Deployment Image Servicing and Management tool
    Version: 10.0.28000.1
    
    Image Version: 10.0.26100.1
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~arm64~~26100.1742.1.10
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Code:
    PS C:\EnterpriseG-Reconstruction> Dism /Scratchdir=C:\Scratched /Image:mount /get-currentedition /LogPath:C:\SKUReport.log
    
    Deployment Image Servicing and Management tool
    Version: 10.0.28000.1
    
    Image Version: 10.0.26100.1742
    
    Current edition is:
    
    Current Edition : EnterpriseG
    
    The operation completed successfully.
    

    Code:
    PS C:\EnterpriseG-Reconstruction> Dism /Scratchdir=C:\Scratched /Image:mount /add-package /packagepath:C:\Windows11.0-KB5072033-arm64\update.mum /LogPath:C:\LCU7454.log
    
    Deployment Image Servicing and Management tool
    Version: 10.0.28000.1
    
    Image Version: 10.0.26100.1742
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~arm64~~26100.7462.1.16
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Code:
    PS C:\EnterpriseG-Reconstruction> Dism /Scratchdir=C:\Scratched /Image:mount /get-currentedition /LogPath:C:\SKUReport.log
    
    Deployment Image Servicing and Management tool
    Version: 10.0.28000.1
    
    Image Version: 10.0.26100.7462
    
    Current edition is:
    
    Current Edition : EnterpriseG
    
    The operation completed successfully.
    
    Code:
    PS C:\EnterpriseG-Reconstruction> Dism /Scratchdir=C:\Scratched /Image:mount /get-currentedition /LogPath:C:\SKUReport.log
    
    Deployment Image Servicing and Management tool
    Version: 10.0.28000.1
    
    Image Version: 10.0.26100.7462
    
    Current edition is:
    
    Error: 0x800f0805
    
    The specified package is not valid Windows package.
    
    The DISM log file can be found at C:\SKUReport.log
    
    Code:
    2025-12-25 09:06:59, Info                  CBS    InternalOpenPackage failed for Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~arm64~~10.0.26100.1 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2025-12-25 09:06:59, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2025-12-25 09:06:59, Info                  CBS    Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2025-12-25 09:06:59, Error                 DISM   DISM Package Manager: PID=6600 TID=5732 Failed opening package Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~arm64~~10.0.26100.1. - CDISMPackageManager::Internal_CreatePackageByName(hr:0x800f0805)
    2025-12-25 09:06:59, Error                 DISM   DISM Package Manager: PID=6600 TID=5732 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByName(hr:0x800f0805)
    2025-12-25 09:06:59, Error                 DISM   DISM Package Manager: PID=6600 TID=5732 The specified package is not valid Windows package. - GetCbsErrorMsg
    2025-12-25 09:06:59, Info                  DISM   DISM Transmog Provider: PID=6600 TID=5732 Building list of edition ids for edition [EnterpriseG]... - CTransmogManager::OpenPackageFromEditionId
    2025-12-25 09:06:59, Info                  DISM   DISM Transmog Provider: PID=6600 TID=5732 Retrieving list of package ids for edition [EnterpriseG]... - CTransmogManager::OpenPackageFromEditionId
    ...
    2025-12-25 09:07:00, Info                  DISM   DISM Transmog Provider: PID=6600 TID=5732 Retrieving list of package ids for edition [EnterpriseG]... - CTransmogManager::OpenPackageFromEditionId
    2025-12-25 09:07:00, Info                  DISM   DISM Transmog Provider: PID=6600 TID=5732 Failed opening package for edition id [EnterpriseG]. hr = [0x800f0805] - CTransmogManager::GetCurrentEdition
    2025-12-25 09:07:00, Error                 DISM   DISM Transmog Provider: PID=6600 TID=5732 GetCurrentEdition: Error [0x800f0805] retrieving current EditionId value. - CTransmogManager::GetCurrentEdition
    2025-12-25 09:07:00, Error                 DISM   DISM Transmog Provider: PID=6600 TID=5732 Failed to get current edition! - CTransmogManager::ExecuteCmdLine(hr:0x800f0805)
    
    basically they are trying to open base EnterpriseGEdition (i.e. 26100.1) Package, but failed. is there any way to make that package open 26100.1742 or latest package?

    I've used UpdateOS for modding LCU, similar with 28000's situtation (like replacing ServerDataCenter to EnterpriseG).
     
  19. max2000

    max2000 MDL Novice

    Nov 22, 2024
    3
    0
    0
    Will this work if you don't activate the administrator profile? Have you tried running the operating system as System (Trusted Installer), as is the default in Windows PE?
     
  20. pp03

    pp03 MDL Expert

    Apr 12, 2014
    1,482
    524
    60
    doesn't 26100 support enterpriseg?