That is UFWS (part of option 1 in the new beta version) and works fine for both versions of setup, modern and the legacy version.
The info also is still kinda in beta, when we had a working tool we decided to publish it as beta, abbodi made the changes in the readme and right before the release i did some last miinute additions, i assumes that "it bypasses all win 11 requirements" would be understood that also legacy bios installs work. Will clarify/unify the info asap
If I use the FiX KiT to bypass 11 requirements, won't I still need Rufus (without enabling its options) to write the modified ISO file to USB?
No, you can simply format the USB drive FAT32 and extract the ISO to it, you only need to keep in mind that FAT32 can't handle install.wim > 4GB (then split the wim or compress it to install.esd) Some, if not most, modern hardware now can boot UEFI from NTFS formatted USB drives too. Or use rufus but don't use it's "fixes".
Copy the iso contents to fat32 format usb after using fix kit. Or use rufus without enabling it's Win 11 options. Your choice. (Darn. Enthousiast posted while I was typing )
You can use this : Win10+ Setup Disk (Works with UEFI Secure Boot / BIOS / Install.wim over 4 GB) | My Digital Life Forums
I am not a moderator or a staff member but from what i read the method is not used by my tool, the subject of this specific thread, and deprecated for quite some time now.
Option-1 isos appear to be OK for inplace-upgrades on legacy machines, but not Option-2. Historically, I have not been able to install option-1 isos on bios/mbr machines. They refuse to install. I've only been able to install option-2 isos on these legacy machines. But once I have the option-2 Win11 installed, I CAN'T do an inplace-upgrade using an option-2 anymore. The option-2 iso will tell me my machine it does not support tpm and secureboot and then halt. But once Win11 is already on a legacy machine, I CAN do an option-1 inplace-upgrade (but not the option-2). So I have to switch to option-1 isos for inplace-upgrades. This seems peculiar and any explanation is welcome.
I ran successful tests with option 2 and upgrades, what build install did you try to upgrade to what build? Please document your tests, screens and the script progress,
I used the v4 Fix kit script. I placed the 26100.1150 insider iso in the Source ISO/Win11 folder and executed the script. Then I proceeded to use that iso for the install. The option-1 iso works great for inplace-upgrades, but I thought I should initially use the Option-2 iso since that is what I used to clean install the original 23H2. I was transitioning from 23H2 to 24H2. For now, the option-1 iso worked great. In the future, I'll try to capture what happens. For now, I'm satisfied with 26100.
I downloaded win11 23h2 ISO from MS, used option 1, took all defaults. Successfully upgraded from Win10 to Win11 23H2!! intel NUC i7 cpu and no tpm. thanks! Do you think this will get 24H2 from Windows Update when it comes out? Also, can you explain the 'apply image script'? where is this script, and how do I modify it, it might help with some defaults I change after install. thanks for your work!!!!
I read that, Microsoft patches TPM 2.0 bypass to prevent Windows 11 installs on PCs with unsupported CPUs, will the FiX KiT continue to work?