I always run the script from cmd opened in the script path (or cd to) therefore, sudden exits could be noticed yes, debug mode is the proper way
better start doing that then.. I rightclick on script and pick run as admin Like previously it ran every install.wim index and mounted boot.wim only to dissapear with this in debug: This is in VM and I have zh-tw languagepack in Langs and OnDemand folder Spoiler
Thanks i can't seem to find that code in the script for me it's this Code: set _keep=1 if %_i%==%BOOTCOUNT% set _keep=0 if %foundupdates% EQU 1 call Updates\W10UI.cmd %_keep% "%BOOTMOUNTDIR%" "!TMPUPDT!" if %_Debug% neq 0 (@echo on) else (@echo off) cd /d "!WORKDIR!" if exist "%BOOTMOUNTDIR%\sources\setup.exe" ( if %_i%==1 copy /y "%BOOTMOUNTDIR%\sources\setup.exe" "!DVDDIR!\sources" %_Nul3% if %_i%==2 call :boots ) could be missing parenthesis mark somewhere, i will check
No thank you Same thing happened with R-version but the R worked just fine early January but not now.. Sofar sogood in debug, seems like it has passed that code snippet I was wrong Spoiler
I still can't find the cause or the code (searched all " equ " instances) could you share the tmp.log?
As soon as its available. I deleted the previous ones. I found the "cd/d workdir" part and i think its this: Code: :contboot set _keep=1 if %_i%==%BOOTCOUNT% set _keep=0 if %foundupdates% EQU 1 call Updates\W10UI.cmd %_keep% "%BOOTMOUNTDIR%" "!TMPUPDT!" if %_Debug% neq 0 (@echo on) else (@echo off) cd /d "!WORKDIR!" if exist "%BOOTMOUNTDIR%\sources\setup.exe" ( if %_i%==1 copy /y "%BOOTMOUNTDIR%\sources\setup.exe" "!DVDDIR!\sources" %_Nul3% if %_i%==2 call :boots ) Whats %_Nul3% defined as? Edit, you're not gonna believe it, thats the u2 version
yeah, it's the only matching part, and it's the same in all v23 revisions none contain the failing part "if equ 0 (" attached debug log is successful operation
Updated - Show visible script version - Export wim indexes one at a time if detected Dism.exe version 10.0.25115.1000 or later - SLIM option will be auto-disabled for builds 26040+ (because new setup require all ISO payload files) - Add support for new FOD packs for builds 26040+ - Improve FOD packs installation logic to add applicable packs only (by detecting parent neutral package in the mounted image) thanks to @Enthousiast for helping and testing
153 line :check if /i not "!dismroot!"=="dism.exe" ( set _dism2="!DismRoot!" /English /ScratchDir ) else ( set "DismRoot=%SysPath%\dism.exe" set _dism2=!DismRoot! /English /ScratchDir ) error
Links to CABs for 26100 doesn't work anymore (at least for ru-RU) Replacing build ID for the one of 26100.2 solves problem. ADK/WinPE 26100 not available at Microsoft anymore.
Why may the W10MUI tool corrupt image that have *many* instances? I download the full UUP with UUPDownloader: UUPDownload.exe -s Professional -v 10.0.26100.1 -t amd64 -r Internal -c ge_release -b Dev -l en-us Create a single AiO 25 editions image with UUPMediaConvertor. UUPMediaConverter.exe -u D:\10.0.26100.1.ge_release.240331-1435_amd64fre_daa9c9eaff11 -i D:\10.0.26100.1.ge_release.240331-1435_amd64fre_en-us.iso -l en-us Now I start W10MUI to add russian LP (copied all the required files). After few instances it fails and later instances in install.wim say that image is not serviceable anymore. First 4 indexes work fine. Starting from index 5 (Pro): Spoiler ============================================================ Mount install.wim - index 5/25 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Add LPs to install.wim - index 5/25 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 An error occurred trying to open - ru-RU\update.mum Error: 0x800703ee Error: 1006 The volume for a file has been externally altered so that the opened file is no longer valid. The DISM log file can be found at C:\WINDOWS\Logs\DISM\MUIinstallLP64.log Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Microsoft-Windows-LanguageFeatures-Basic-ru-ru-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 3 - Adding package Microsoft-Windows-LanguageFeatures-TextToSpeech-ru-ru-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] Processing 2 of 3 - Adding package Microsoft-Windows-LanguageFeatures-Handwriting-ru-ru-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] Processing 3 of 3 - Adding package Microsoft-Windows-LanguageFeatures-OCR-ru-ru-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 3 - Adding package Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] Processing 2 of 3 - Adding package Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~wow64~ru-RU~10.0.26100.1 [==========================100.0%==========================] Processing 3 of 3 - Adding package Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~ru-RU~11.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 3 - Adding package Microsoft-Windows-Printing-PMCPPC-FoD-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] Processing 2 of 3 - Adding package Microsoft-Windows-StepsRecorder-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] Processing 3 of 3 - Adding package Microsoft-Windows-StepsRecorder-Package~31bf3856ad364e35~wow64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 5 - Adding package Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] Microsoft-Windows-MediaPlayer-Package: The specified image is no longer serviceable and may be corrupted. Discard the modified image and start again. Error: 0x80073713 Processing 2 of 5 - Adding package Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~wow64~ru-RU~10.0.26100.1 [==========================100.0%==========================] Microsoft-Windows-MediaPlayer-Package: The specified image is no longer serviceable and may be corrupted. Discard the modified image and start again. Error: 0x800f0830 Error: 14099 The specified image is no longer serviceable and may be corrupted. Discard the modified image and start again. The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\MUIinstallFOD64d.log Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 7 - Adding package Microsoft-Windows-ProjFS-OptionalFeature-FOD-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] Microsoft-Windows-ProjFS-OptionalFeature-FOD-Package: The specified image is no longer serviceable and may be corrupted. Discard the modified image and start again. Error: 0x800f0830 Error: 0x800f0830 The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\MUIinstallFOD64e.log Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 7 - Adding package Microsoft-Windows-DirectoryServices-ADAM-Client-FOD-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] Microsoft-Windows-DirectoryServices-ADAM-Client-FOD-Package: The specified image is no longer serviceable and may be corrupted. Discard the modified image and start again. Error: 0x800f0830 Error: 0x800f0830 The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\MUIinstallFOD64f.log ============================================================ Update language settings ============================================================ ============================================================ Add updated winre.wim to install.wim - index 5/25 ============================================================ 1 file(s) copied. ============================================================ Unmount install.wim - index 5/25 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image File : E:\W10MUI\install.wim Image Index : 5 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. After that same picture
You clearly see that the errors are reported by DISM, nothing to do with W10MUI either the original images are corrupt, your harddisk is failing, your AV is blocking... or whatever
No. Tested same WIM (25 images) on system drive - same result, starting index 5 get an error. If I take same install.wim, - clean one manually without W10MUI, I can apply same package with DISM with no errors to index 5. Manual adding LP to all 25 indexes from ESD and later rerunning W10MUI results a stable image.