Running Win 11 on i5 3570K. Sandy Bridge is MINIMUM here. You just don't WANT to use it with older hardware . For this a good linux is the way better choice.
Just saying Thanks! I just downloaded "Win_11_Boot_And_Upgrade_FiX_KiT_v4.0" from OP and it simply just worked for me (Option 1) on a UUPDump created ISO "26100.1150.240702-1833.GE_RELEASE_SVC_PROD1_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO" I was able to update an old(er) HP Laptop that only had TPM v1.2 and... Thanks again to those who make these options possible!
hello i wanted to update my windows 23h2 in 24h2 i requested option 2 and rufus to create the key and at the time of the update i have the required ready panel which stop my update thank you
The problem isn't using rufus in itself. You can use the kit and still make a bootable usb with rufus, just don't check any of the boxes in the rufus popup. The issue here is an unclear description of the problem...
I create a key to be able to put it on another PC to do the update but I'm not sure if it's the utility or rufus which is causing the problem
Win 11 Boot And Upgrade FiX KiT v4.0 I don't know which option you use I use option 1 and so far I haven't had any problems..
I believe @GREBERT mentioned option 2, which fails for me when attempting an in-place upgrade. (PC not meeting requirements) Option one works.
It should recommend which option to use. I think a clean option always works. Unsure about an upgrade, worth a try.
Win 11 Boot And Upgrade FiX KiT v4.0 I don't know which option you use I use option 1 and so far I haven't had any problems. It was a translation problem
i redoed with option 1 i was skippering the hardware requirements i had the blue page up to 100 percent and rebooted and there it stay stuck on the black page with the windows logo
I’m pretty sure it wants to install updates when it reaches that black page. Were you connected to the internet? Anyhow, at this point it’s not a problem related to the fix kit.
What chipset do you have? MS locked out some older ones, with the result that new Windows does not boot on them at all.
Chipset and/or cpu. Grebert mentioned going from 23H2 to 24H2. The lack of sse4.2 could be a problem during that upgrade.