Let's install Windows 11 on incompatible hardware

spapakons said:

Yes, Rufus still works with the additional precaution to keep disconnected from the internet during the upgrade on an unsupported computer.

Click to expand...

So Rufus adds internet disconnection during the upgrade?

Rufus hacks a specific file to bypass compatibility check and install or upgrade to Windows 11 an unsupported computer. However since version 22H2 this is not enough. An unexpected online compatibility check will make the upgrade fail. To prevent that you must stay disconnected from the internet so this hidden compatibility check cannot be done and the upgrade proceeds without issues. I have seen it in over 5 unsupported computers. If I forget to disconnect, the upgrade will fail. If I disconnect it succeeds.

spapakons said:

Rufus hacks a specific file to bypass compatibility check and install or upgrade to Windows 11 an unsupported computer. However since version 22H2 this is not enough. An unexpected online compatibility check will make the upgrade fail. To prevent that you must stay disconnected from the internet so this hidden compatibility check cannot be done and the upgrade proceeds without issues. I have seen it in over 5 unsupported computers. If I forget to disconnect, the upgrade will fail. If I disconnect it succeeds.

Click to expand...

What Rufus doesn't do is the CPU compatibility. MY PC has everything else except for this. It's a March 2017 with a 7th Gen i5CORE. Got Secure Boot and TPM. I have to write in the registry the MoSetup and it's been running just fine.

spapakons said:

Yes, Rufus still works with the additional precaution to keep disconnected from the internet during the upgrade on an unsupported computer.

Click to expand...

I tried Rufus with latest Canary and Legacy BIOS and it does not work in that case.
Could just be an issue with this specific Laptop MSI GT70-0NC. I don't have any other machines left with Legacy Bios to try so I cannot really compare.
Older Canary Builds before 25967 and up did not have any problem booting. Something is changed in the bootmgr file that is causing this Disk Error in this machine, looks like it is pointing to the wrong disk instead of the one where it was booted from.
No problem with other insider channel builds, Dev, Beta, R.P.
Public Win 11 23H2 build runs fine too.

The last Canary has a newer bootloader that drops legacy functionality, is UEFI mode only. There is a workaround, see previous posts in this thread. Last time I checked Rufus allows you to bypass all compatibility check, including the CPU. Maybe you didn't select all the options when creating the USB flash drive, try again.

Hi,
Yeah the only residual effect of rufus auto adding a local account which you need to change
It also uses the temp password feature that needs to be disable or you'll get an alter your password expired lol

Right click on the Start button, choose Computer Management from the menu,
and navigate to System Tools - Local Users and Groups - Users:
Double click your user name, and change the password settings as follows:

User must change password at next logon: Off

Password never expires: On

spapakons said:

The last Canary has a newer bootloader that drops legacy functionality, is UEFI mode only. There is a workaround, see previous posts in this thread. Last time I checked Rufus allows you to bypass all compatibility check, including the CPU. Maybe you didn't select all the options when creating the USB flash drive, try again.

Click to expand...

You can try if you like, I got it to work, but not with Rufus. Rufus 4.3 created a USB that hung when it asked to press any key to load from the USB.
There is a new Rufus 4.4 from Jan 17, 2024, and that fails the same way.
I'm done with these useless experiments.

Rufus 4.4.2103 creates the USB bootable flash using the same bootmgr file that it finds in the ISO.
That file is no longer good for this Legacy Bios laptop, and it just hangs.


If I replace it with a different bootmgr file I can get over this initial block, but then it will still fail on first reboot after the installation of Canary build 26020 as I already explained earlier.
Here I renamed the original bootmgr and replaced it with the one from Dev Build 23619


Also tried with Canary Build 25951 and it still works fine without this booting issue.


So, Rufus is not bypassing this specific problem, at least not yet with the version 4.4.2103 dated Jan 17, 2024.

To get over the second boot problem Rufus would need to modify the installation files and replace the bootmgr file with one that is good for this legacy BIOS PC, before the installation process loads it in the system partition.
Good luck with that!

There are other locations in the installed system where the bootmgr would need to be replaced.
Perhaps could be changed in boot.wim and install.wim before doing the install.
One example is this location.



Edit:
It looks like bootmgr is pointing to the wrong disk in this MSI GT70-0NC Legacy Laptop. I cannot figure out what exactly they changed in boomgr file, but the last several Builds from 25967 on to latest 26020 have the same exact issue. Not sure when the problem started, but I have used older Canary Builds 25951 and worked fine without booting issues, the problem was added with build 25967.
Maybe the problem is specific with this PC, I heard from another user that he did not have this boot problem on a legacy Bios machine, no problem booting on his legacy desktop with this same Build 26020.
I may never figure out what exactly they changed in bootmgr to cause this disk error.

fg2001gf11F said:

You can try if you like, I got it to work, but not with Rufus.
I'm done with these useless experiments.

Click to expand...

That's what Insiders is all about. Experiments.

mecanicogolf said:

That's what Insiders is all about. Experiments.

Click to expand...

Then you can have fun and try.

fg2001gf11F said:

Then you can have fun and try.

Click to expand...

I do, thank you. All the time.

mecanicogolf said:

I do, thank you. All the time.

Click to expand...

What about the results?
I just said that I tried Rufus 4.3 and 4.4 and did not work with Canary 26020 on Legacy Bios. Works fine with Dev Builds, but not the latest 4 Canary builds.
MS changed the bootmgr file and it causes an error when trying to boot on this Legacy Bios PC.
Probably done on purpose to stop the use of new Canary builds with Legacy Bios machines.

Looks like you don't have a Legacy Bios machine to experiment with.

fg2001gf11F said:

What about the results?
I just said that I tried Rufus 4.3 and 4.4 and did not work with Canary 26020 on Legacy Bios. Works fine with Dev Builds, but not Canary.
MS changed the bootmgr file and it causes an error when trying to boot on Legacy Bios.
Probably done on purpose to stop the use of new Canary builds with Legacy Bios machines.

Looks like you don't have a Legacy Bios machine to experiment with.

Click to expand...

That's what it looks like.

I never said Rufus can install Canary on Legacy BIOS mode. I said it removes compatibility check including CPU, minimum RAM, TPM 2.0, Secure Boot. A nice side effect of removing compatibility check is that you can install Windows 11 on Legacy BIOS mode, except Canary version of course. The Canary version, as already mentioned, requires to replace the bootloader after every restart, until you can finally boot to the desktop. Even then a new version might break the bootloader and you have to replace it again, so keep a copy of the bootloader file handy.

spapakons said:

I never said Rufus can install Canary on Legacy BIOS mode. I said it removes compatibility check including CPU, minimum RAM, TPM 2.0, Secure Boot. A nice side effect of removing compatibility check is that you can install Windows 11 on Legacy BIOS mode, except Canary version of course. The Canary version, as already mentioned, requires to replace the bootloader after every restart, until you can finally boot to the desktop. Even then a new version might break the bootloader and you have to replace it again, so keep a copy of the bootloader file handy.

Click to expand...

Hi,
The MS grip is tightening lol

spapakons said:

I never said Rufus can install Canary on Legacy BIOS mode. I said it removes compatibility check including CPU, minimum RAM, TPM 2.0, Secure Boot. A nice side effect of removing compatibility check is that you can install Windows 11 on Legacy BIOS mode, except Canary version of course. The Canary version, as already mentioned, requires to replace the bootloader after every restart, until you can finally boot to the desktop. Even then a new version might break the bootloader and you have to replace it again, so keep a copy of the bootloader file handy.

Click to expand...

Good luck with Rufus.
I never needed it for installing windows.
Just tested it a few times and could not find any valid reason to use it. No need for a hack helper.

You can use Rufus to create a "regular" (non-hacked) USB flash drive, just not select any options. I use Rufus to create any bootable USB flash drive, including for Windows XP, Vista and 7.

Hi,
I love rufus newer version
I think they might even trim toenails I just haven't noticed the setting yet

spapakons said:

You can use Rufus to create a "regular" (non-hacked) USB flash drive, just not select any options. I use Rufus to create any bootable USB flash drive, including for Windows XP, Vista and 7.

Click to expand...

Never needed Rufus for that.

ThrashZone said:

Hi,
I love rufus newer version
I think they might even trim toenails I just haven't noticed the setting yet

Click to expand...

It should come with a coffee maker; I could have a use for that.

fg2001gf11F said:

It should come with a coffee maker; I could have a use for that.

Click to expand...

And a pair of scissors for a haircut.