========================= 2xH2_Creator_16.6 ========================= Updated to 26x00.8655 - Added option to copy or not WPI to the image - Added option for select the M.A.S. package to be included as the DEFAULT: 1. TsForge 2. HWID 3. Do not include any M.A.S. packages in the image Regardless of whether the choice is 1 or 2: . When the created image is 25H2 IOT, is used TsForge . When the created image is 25H2 LTSC, is used TsForge + adjustment - Fixed the script _PreDownloadAllUpdates.cmd - Updated APPX files - Updated W10UI.cmd to v10.60 - Other adjustments Test with: - pt-br_windows_11_enterprise_ltsc_2024_x64_dvd_2bb6b75b_2.iso - 26100.1742.240909-0928.GE_RELEASE_SVC_REFRESH_CLIENTBUSINESS_VOL_X64FRE_PT-BR.ISO ========================= 26H1_Creator_2.1 ========================= Updated to 28000.2269 Edit 2026.06.23 Reuploaded the package fixed https://forums.mydigitallife.net/threads/slimdown11-–-turn-windows-11-or-ltsc-2024-into-classic-legacy-windows.90039/#post-1872013 Enjoy
========================= 2xH2_Creator_16.6 ========================= Update to 26x00.8737 - Only the all.txt and LCU2.txt files have been updated 1. Download the UUP_update.7z file and extract its contents into the 2xH2_Creator_16.6 folder. 2. Run the extracted file "UUP_8737.exe" to update the UUP\all.txt and UUP\LCU2.txt files. 3. Remove all updates .msu and .cab from the UUP folder. 4. Run the _PreDownloadAllUpdates.cmd script to download the new updates. https://forums.mydigitallife.net/threads/slimdown11-–-turn-windows-11-or-ltsc-2024-into-classic-legacy-windows.90039/#post-1872013
Yes, I know—I specifically enabled debug mode for testing. Since my other tests—24H2, 25H2, and 26H1—were all running updated versions, this time I tried the raw build 26100.1742 to save time, and I got the same result in all of them. There’s no issue on the virtual machine, but the disks are missing in the physical machine installation. I backed up the aStorVD / iaStorAC / stornvme / pciide / clfs / volmgr stack components currently installed on my computer, and I’m selecting them when prompted during installation, but unfortunately, it says the drivers are invalid.
Have you tried adding the autounattend.xml? How did you create your USB drive (Pendrive)? Keep in mind that the 2xH2_Creator_16.6 script is only for 24H2 and 25H2. For 26H1, the 26H1_Creator_2.1 script must be used. Try integrating the drivers into boot.wim 2 using the 2xH2_Creator_16.6 script.
I’m using the ISO file with Ventoy. Yes, I didn’t add the drivers, but there’s an interesting situation: when I use the install.wim created for the 24h2 ISO to perform the installation, it installs without any issues. So, there seems to be a problem with the boot.wim file generated by my script. Thank you very much for your interest. I could try adding the drivers, but when I select them during installation, it rejects them, saying they’re not compatible—and these drivers are already installed on my PC right now.
Personally, I don't use Ventoy. I prefer the script created by @rpo or Rufus. Try using @rpo's script; it's the one I use most often, and I haven't had any issues with it. https://forums.mydigitallife.net/th...secure-boot-bios-install-wim-over-4-gb.79268/
I don’t know much about coding, so I’d like to ask: as far as I understand, the script doesn’t delete any drivers, and that’s enough for me. I’ll try some different alternatives—first Rufus instead of Ventoy, and then what you suggested. That’s fine. The only change I made was to undo the right-click menu changes—that’s it. Thank you; I’ll give it a try and let you know the results.
That's right. The script doesn't remove any drivers. It simply gives you the option to integrate your drivers.
That answer is enough for me—thank you. So I guess I have a different problem... I'm going to try something now. Yes, that was a big problem, Ventoy. The method you suggested solved the issue, and the installation screen successfully displayed all the disks. https://forums.mydigitallife.net/th...secure-boot-bios-install-wim-over-4-gb.79268/ This is great...
SunLion, I’ve been testing things out—okay, I solved the problem yesterday, but Ventoy would have been great for me because all my ISO files are on a single USB drive... That’s why I’m still experimenting—there’s an issue with boot.wim because when I update using only W10UI and then merge the latest boot.wim from here with the install.wim I got from your script, the installation happens via Vento. I don’t understand why that happens. I think I can use it this way because install.wim works great.
Yes, using Ventoy is an option for you. In our script, the boot.wim file is edited to work correctly after reducing the size of the 'sources' folder and to add the TPM bypass.
@otvertka I too had trouble with some Win 11 boot.wim until I did the following: What I found with the later versions of Win 11 is that Setup client which calls setupprep.exe & setuphost.exe. To work around that: Mount boot.wim, and integrate this reg value to the SYSTEM hive: Code: [HKEY_LOCAL_MACHINE\SYSTEM\Setup] "CmdLine"="X:\\sources\\setup.exe" NOTE: Before you start to run any of the commands below, read the entire text. I am missing the specific details for the entry you want to add. If you can provide that to me, as described below, then I can nail down that one last command for you. DISM /mount-wim /wimfile:\Project\WinPE\boot.wim /index:1 /mountdir:\Project\Mount Note that I am mounting to D:\Project\Mount. Modify to fit your needs. If you change this, make sure to also do so for the other commands that follow. Next we load the registry "system" hive to a fictitious temp location, in this case I am using the name "offline" reg load HKLM\offline D:\project\mount\windows\system32\config\system Add the key: Note: You may need to refine this next line slightly. My apologies, but I'm not sure I understand what the <br> is. The idea here is that you have the system hive loaded to "offline" now. So in any "reg add" command, you would add it using the exact same command as on a live Windows system but substitute "offline" for "system". Here is a sample of how I would add the entry that bypasses the TPMCheck: EXAMPLE ONLY: reg add HKLM\offline\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f Here then is your line, but I seem to be missing details like if this should be a dword, string value, etc. If you can provide the details on this entry then I can help with the exact command. Bottom line is that the command below is not accurate and needs to be modified: reg add HKLM\offline\Setup\<br>"CmdLine"="X:\\sources\\setup.exe" Now we need to unload the "offline" hive: reg unload HKLM\offline Finally, we unmount and commit the changes: dism /unmount-image /mountdir:\project\mount /commit" Below is an example, putting all the above together, showing how I load the keys that bypass Windows 11 system requirements. Note that I repeat the exact same thing for index 2 in the boot.wim. In other words, I run the commands below twice but the second time I replace "index:1" with "index:2": DISM /mount-wim /wimfile:\Project\WinPE\boot.wim /index:1 /mountdir:\Project\Mount reg load HKLM\offline D:\project\mount\windows\system32\config\system reg add HKLM\offline\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f reg unload HKLM\offline dism /unmount-image /mountdir:\project\mount /commit"
@Mavericks Choice, Thank you for your help. I took a look, but this script already does exactly what you described. For example, it redirects to the Setup.exe file here, but my problem isn’t with Setup.exe—it’s that it doesn’t recognize the drivers even though they’re installed. This might be a conflict with Ventoy. echo. echo. echo ============================================================ echo Configuring Boot.wim 2 echo ============================================================ reg load HKLM\TEMP “MTBoot2\Windows\System32\config\SYSTEM” reg add HKLM\TEMP\Setup /v “CmdLine” /t REG_SZ /d “X:\\sources\\setup.exe” /f reg unload HKLM\TEMP echo. echo Done And here, it performs the BypassTPM operation echo. ECHO. ECHO ============================================================ ECHO Add BypassTPM to Boot.wim 2 ECHO ============================================================ reg load HKLM\TK_SYSTEM “%BootMount%\Windows\System32\config\SYSTEM” >nul reg add “HKLM\TK_SYSTEM\Setup\LabConfig” /v ‘BypassTPMCheck’ /t REG_DWORD /d “1” /f reg add “HKLM\TK_SYSTEM\Setup\LabConfig” /v ‘BypassSecureBootCheck’ /t REG_DWORD /d “1” /f reg add “HKLM\TK_SYSTEM\Setup\LabConfig” /v ‘BypassRAMCheck’ /t REG_DWORD /d “1” /f reg add “HKLM\TK_SYSTEM\Setup\LabConfig” /v ‘BypassStorageCheck’ /t REG_DWORD /d “1” /f reg add “HKLM\TK_SYSTEM\Setup\LabConfig” /v ‘BypassCPUCheck’ /t REG_DWORD /d “1” /f reg add “HKLM\TK_SYSTEM\Setup\MoSetup” /v ‘AllowUpgradesWithUnsupportedTPMOrCPU’ /t REG_DWORD /d “1” /f reg Unload HKLM\TK_SYSTEM >nul The issue I'm having only occurs with Ventoy; there are no problems with others—Rufus, for example, works fine. So the script does a great job, but the boot.wim conflicts with Ventoy's drivers.
This used to be an issue back in late 2021, early 2022. Use the latest version of ventoy and make sure you're using an up-to-date windows iso.