I get a few errors with the above script and en-us_windows_11_consumer_editions_version_25h2_updated_april_2026_x64_dvd_38233bf1.iso: ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.26200.8246 Processing 1 of 1 - Adding package Package_for_ServicingStack_1837~31bf3856ad364e35~amd64~~28000.1837.1.3 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at C:\Windows\Logs\DISM\DismSSU.log Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.26200.8246 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~28000.1836.1.18 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at C:\Windows\Logs\DISM\DismLCU.log ============================================================ Remove ProvisionedAppxPackages ============================================================ Microsoft.DesktopAppInstaller_2025.926.104.0_neutral_~_8wekyb3d8bbwe Error: 15610 Removal failed. Please contact your software vendor. ============================================================ Remove OneDrive ============================================================ The operation completed successfully. The operation completed successfully. The operation completed successfully. The operation completed successfully. The operation completed successfully. The operation completed successfully. Remove the Task registry key of OneDrive ERROR: The system was unable to find the specified registry key or value. ERROR: The system was unable to find the specified registry key or value. ERROR: The system was unable to find the specified registry key or value. Any ideas why?
You are trying to edit: en-us_windows_11_consumer_editions_version_25h2_updated_april_2026_x64_dvd_38233bf1.iso But script 26H1_Creator_1.7 is for version 28000. For image 25H2, use script 2xH2_Creator_15.9. Good luck!
I tried 2xH2_Creator_15.9 with X23-81951_26100.1742.240906-0331.ge_release_svc_refresh_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso and I again got an error: ============================================================ Downloading missing Windows 11 2xH2 Updates... ============================================================ Done. ########################################################### Prepare Updates to Integration ########################################################### D:\2xH2_Creator_15.9\UUP\25H2_Windows11.0-KB5082417-x64-ndp481.msu 1 file(s) moved. The system cannot find the file specified. Done... Both ISOs were not detected and needed to be placed in the same folder as the script. Where is each of the Options explained in this post? What are PersonalTweaks? =========================================================== 2xH2_Creator_15.9 Configured Options at 25/04/2026, 23:08:26.09 =========================================================== Running in NORMAL mode Selected Other ISO - Not configured in the script Integrate Drivers Into Install.wim Integrate Drivers Into Boot.wim index 2 Enable Store Do not Remove ClickToDo - GetStarted - WindowsBackup Enable WindowsSearch Do not Remove Windows Defender Do Not REMOVE Edge Enable Net35 Enable Modern Calculator Do not Remove WinRE.wim Do Not Enable MediaPlayer Don't Install Openshell Don't Customize Boot.wim Do Not Apply PersonalTweaks ===========================================================
The images that the 2xH2_Creator_15.9 script automatically identifies are: - Windows_11_Enterprise_LTSC_2024 (26100.1742) - Windows_11_IoT_Enterprise_LTSC_2024 (26100.1742) - 26100.1742.240909-0928.GE_RELEASE_SVC_REFRESH_CLIENTBUSINESS_VOL - 26100.1742.240909-0928.GE_RELEASE_SVC_REFRESH_CLIENTCONSUMER These images should have the following in their name: - *windows_11_enterprise_ltsc*.ISO - *windows_11_iot_enterprise_ltsc*.ISO - *CLIENTBUSINESS*.ISO - *CLIENTCONSUMER*.ISO Any other images should be placed in the main folder next to the script, and when asked if you want to use this image, answer yes. Try it and see if it works for you.
It works if it is in the same folder. Any ideas about the error? And are the Options explained somewhere in the post?
Please note that the script was written to use 26x00.1742 images as a base. Other images can be used. It has not been tested here with other images. The options/questions are self-explanatory, in a very simple way, during the use of the script. There is a _HowToUse.txt file inside the package with general instructions.
I get errors with X23-81951_26100.1742.240906-0331.ge_release_svc_refresh_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso (26100.1742) and 2xH2_Creator_15.9. Some of the options are not self-explanatory, at least to me, for example WinRE.wim, Boot.wim and PersonalTweaks.
Which errors do you get? Share the log... Regarding explanations: WinRE – Windows Recovery Environment, used to repair Windows if something goes wrong (startup issues, corruption, reset options), you can choose to keep or remove it. Boot.wim – The "setup" part of Windows (the installer). The script can modify it to bypass Windows 11 system requirements, integrate drivers (for the install stage only), or use the old setup instead of the newer Windows 11 one. PersonalTweaks – Here you can add any tweaks that are not included in the main script. These are usually based on personal preference, so you can ignore this if you don’t need anything specific.
I already posted some of the errors in previous replies. By the way, the _Start.cmd scripts fail to run and I need to use the _Start_Nsudo.cmd ones.
You're probably not using Windows 10 as your host system. When you use start-nsudo, the log file is not created automatically. In this case, at the end you must select everything, copy and paste it into a text file, and save it to have the log file.
@SunLion I unified the Start script so it works the same on both Windows 10 and 11, using NSudo for elevation while still preserving logging (no need to manually copy output anymore). Since the entire script is now running as TrustedInstaller, all internal uses of %NSUDO% in the main scripts should be removed, they’re no longer needed. You can replace the existing Start script with this: Code: @echo off cd /d "%~dp0" :: Ensure NSudo exists if not exist "%~dp0tools\amd64\NSudo.exe" if not exist "%~dp0tools\x86\NSudo.exe" ( echo. echo =========================================================== echo NSudo not found! echo =========================================================== echo. pause exit /b 1 ) :: Detect architecture if exist "%WinDir%\SysWOW64" ( set "HostArchitecture=amd64" ) else ( set "HostArchitecture=x86" ) :: Run as TrustedInstaller whoami /groups | find "S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464" >nul || ( "%~dp0tools\%HostArchitecture%\NSudo.exe" -U:T -P:E -UseCurrentConsole -Wait "%~f0" %* exit /b ) bin\quickedit.exe 0 echo Logging output to 2xH2_Creator_15.9.log ... call 2xH2_Creator_15.9.cmd 2>&1 | bin\tee.exe 2xH2_Creator_15.9.log Also you can move the version variable to the Start script and then replace hardcoded version number with the variable, easier to maintain.
Have you tried using this script yourself? Did it work? That's very interesting. If possible, could you please show me the finished solution?
I tested it with Win 10 as host, should also work with Win 11. The non-nsudo elevation script is very "hacky", Win 10 is more forgiving than 11. If you want to try it simply replace the entire code in the Start script with the one i shared, and remove all %NSUDO% calls in the main script. This also means that you don't need to run the Start script as admin, since it will relaunch itself already elevated.
I see, that's why I asked, because I feel like this script isn't working for me. When I run it, several windows open that don't work. Thanks for the advice. Try running the script without Administrator privileges and remove all NSudo entries from the main script.
If you try to use it in a custom version of the script make sure that the file names in the logging area are correct, this is the fragile part. Make sure the Nsudo path is correct. If all is correct, after you run the Start script you should see the main script. Add "pause" at the end of the script to keep the terminal open and see which error you get.
Got it, I'll give this script a try, as you suggested. Actually, I'm using my own version of the script, and everything works perfectly. https://forums.mydigitallife.net/th...sic-legacy-windows.90039/page-84#post-1910601 I just liked the idea of running the main script, but I'm having some issues with it right now.