Strange behaviour fixing an old win 10 with many apps (upgraded and up-to-date). Using fix-kit 4.0 selecting op1. Generating a "FIXED" win 11 iso from a win 10 iso (23H2) in the win 11 source folder (downloaded from this site) Nothing in the win 10 source folder. Went fine so far. A setup from the FIXED iso selecting "keep apps and folders" also went fine. BUT: Right click any exe-file (or icon on the desktop pointing to exe-file) locks up. A blue "dot" circling around and around forever. Other right clicks are ok. This behaviour was not there in the old win 10. Tried disable all non MS in shellexe via nirsoft shellexview. Did not help. Deleted all folders except NEW and WORK in shellex via regedit. Did not help. Tried a lot, have given up. This problem is probably not due to any bugs in the fix-kit (?), but never the less any hint or advise here would be appreciated.
This tool do not "convert" a win 10 iso in to a win 11 one. i think you need to read again what is this tool for and how to use it
10 iso (23H2) : what is this? There is no win10 23H2 If i want use a win10 iso, you have to use option 4 and you need a win 10 iso and a win 11 iso (install.wim or install.esf from win 11 is mandotory)
Sorry, spelling error. It should read win11(23H2). What I did is to boot my old win 10, run the fix-kit 4.0 op. 1 from thumb drive with the win11-23H2 iso in sources folder, subfolder win11. It produced a FIXED w11 iso. Executed the setup in the FIXED iso, selecting keep apps and folders. Resulted in a win 11 installation with all apps and folders, so far so good. Only problem is the rigth click on exe-files and desktop icon for exe-files. All other right clicks work ok. Have I misunderstood or done something wrong ?
Hi @Enthousiast !! I have a question. Does the lastest version of your program enable the possibility of using the modified ISO on a VM that doesn't meet the requirements? I made the ISO using option 3 for a Windows Server 2025 ISO and I'm stucked on the boot logo and I can't access to installation program Spoiler: VM Thanks!
Up till the last 26058 Canary/Dev all worked fine for me, but now option 2 seems to be the recommended option for most scenarios but all others should work too, but one for legacy setup and the other for modern setup. I will start my 26063 MRP test in a few minutes and report what happens. And on vbox you need to set the chipset to ICH9/
Fixkit 4.0 trouble when Clean installing w11 23H2. Both option1 and 4 aborts aften boot. Upgrade: No trouble, only Clean install. Seems w11 does not like pc in question (ga-x58a-ud7), and that abort is caused by old driver(s). No trouble clean installing w10, only w11. So w10 does not mind old drivers, but w11 does indeed. Have only found one way to bypass this problem: 1. Clean install w10 2, Registry fix reg add HKLM\SYSTEM\CurrentControlSet\Control\CI\Config /v VulnerableDriverBlocklistEnable /t REG_DWORD /d 0 /f to enable old drivers. This is maybe the same as Upgrade-fail-fix.cmd ? 3. Upgrade win 10 to w11 via Fixkit option 1. This procedure is a bit cumbersome, is there another more easy way to do a clean instal ?l
Option 4 is not a real option. At clean installing there are no already installed drivers present, that's only when performing an upgrade. What exact windows 11 build are you trying to install? The chipset ICH10 should work fine. When you are able to select the SKU and it continues to the EULA then the requirement checks are passed.
iso file 23H2-norwegian-x64v2.iso. Winver: 23H2 22631.3085 (noted from a successfull previous upgrade from win 10 to win 11) Install runs fine until first boot, after boot a blue screen with abort "message system service exception". Have also experienced blue screen with message "irql not less or equal" but forget under which circumstance. . Seems to me that win11 "does not like" the hardware (ga-x58a-ud7) with pcie cards for usb3.0, display, and SSD (revodrive). Nothing I can do to help win 11 to change its mind ?
Nothing related to the win 11 system requirements at boot and upgrades, this is something else it seems.
I should probably enter the UTM community, but felt like it is worth trying here as well. I tried booting and installing Windows 11 ARM via the "VM-Tool" UMT on a Apple M1 today. Windows 11 ARM boots, installs and activates via KMS script like a charm. Trying to boot up an untempered Windows 11 x64 in Emulation (not virtualization) will boot/work until "This version of Windows cant be installed on this PC". Trying to boot up a tempered (fixed with your FIX) Windows 11 x64 will show "Press any key to boot from CD/DVD..." and just shows the UMT logo then. Maybe someone already experimented around this? p.s. It works, for example, if I use Crystalfetch in MacOS (its using the UUPDUMP api) with Windows 10 x64.
Help I am using Win_11_Boot_And_Upgrade_FiX_KiT_v2.2 which I have I have used in the past with out issue. Now I am getting an error after starting setup when using it again. Windows failed to Validate the product key. My internet cable was unplugged. Now what?