I spoke about VirtualBox. VirtualBox (maybe only the older version I have) has failed checks for me in the past, even if the same setup worked on bare metal and under VMWare. Looks like some additional hidden checks for Virtualizers. The option 2, which is the combined options 2 and 3 from the old version does work under VirtualBox. The old version 2 alone would fail, I always had to do 2+3.
There is just one currently supported version (6.x) and as far as i have tested all options work on vbox too. I test in vbox, vmware and real hardware (old non efi laptops). When it doesn't work on one of the virtual tests i test on the real hardware, when it works on vmware and/or real hardware, it works. Example: VBox is a bit of a weird thing, MRP settings are ignored when it disables the network adapter, so on vbox that won't work, on VMWare and real hardware all works..
Wrong, the only supported VirtualBox versions are 7.1 and 7.2. 7.0 and lower are all out of support. On Windows 7, I'm limited to my trusted VirtualBox 5.2.45.
Can you stop using windows 7 as a reference for proper functionality of tools and software? Not interested in vbox discussion in this thread. And my 6.x reference is about MY tool, the SUBJECT of this THREAD. OMG...
The script you can download here : https://forums.mydigitallife.net/attachments/win_11_boot_and_upgrade_fix_kit_v6-1-zip.73436/ is updated to introduce une new parameter Select_ISO defined at the top of the script. If the parameter is set, ie Code: @SET "Select_ISO=yes" , the user can select the iso image by exploring the folder of his choice; the default folder is Source_ISO. If the parameter is not set =, ie Code: @SET "Select_ISO=" , the script is compatible with version 6.0 of the script.
@rpo, msft keeps targeting me with butloads of ISOs to process, thanks for the update, i will update the tool files asap with the updated script. As long as it first checks the original source_iso folder by default it is fine.
Enthousiast: I obtained version 6.1 of the command script from the link in post #1735. I currently have it in the Windows 11 Boot And Upgrade Fix Kit folder for version 6.0, as shown here: Can I delete the version 6.0 command script, or is each version needed for a specific Windows 11 version? Can the UUP Dump ISO's for 24H2 and 25H2 be used with this tool?
You can delete the 6.0 script, i am almost about to upload the 6.1 zip file. All properly created ISOs can be used (ESD>ISO, MVS, Techbench and UUP dump)
When I read post #1735, I was wondering why a stand-alone command file was available, but the download for the entire Windows 11 Boot And Upgrade Fix Kit v6.1 tool could not be found. Thanks for making me aware that it has not been released yet.
https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit-v6-0-released.83724/ Changelog: @rpo at MDL made the ISO selection easier, it selects the existing "ISO_Sources" folder by default but you can browse to any other folder and select an ISO.
asking help here. Am I doing something wrong? missing something? when I tried to press number 1 while running the tool. I cannot press and it has a beep sound. stick keys is not enabled.
And what are you expecting to happen? When you run the tool, option 1 is selected by default. Pressing 1 again will do nothing. When you press 2, option 2 is selected and option 1 is deselected. Nothing wrong here. The beeping is from cmd when repeating the same input or invalid input.
I've downloaded the v6.1 but inside the .zip there's 2 files named "Win_11_Boot_And_Upgrade_FiX_KiT_v6.1.cmd One is alone and the other one is inside the folder...the hash are not the same ...that's why i'm asking which one should I use ??
One seems to be the newer ISO detection in ISO srouce folder and the other not. other than that they're identical
You can remove the cmd from outside the project folder, the one from September 4. 2025, the correct one is inside the project folder inside the zip. https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit-v6-1f-released.83724/ Removed the older 6.1 script from the zip.
I checked, i didn't include one but the folder OEM is missing now, i ma having a bad weekend for releasing stuff it seems You can make a OEM folder and put in the desired $OEM$ folder to have it copied to the ISO:\Sources folder. Will re-up all once more asap