Any negative impact on current bypass tricks as Microsoft tries to block now

Microsoft is cracking down on people upgrading to Windows 11 on unsupported hardware:

If you didn't see this previous thread, it's the same "news". Read this one for everyone's comments on the topic.

That thread is mental. So here is the video in the first post.

This video is based on a Neowin (bahahahahahahaha) post on Neowin’s website.
I haven’t come across anyone for ages that felt the need to use the registry hack in question.
Everyone I come across uses RUFUS 4.6 to do the job for them, with no adverse affects or “Negative impact”

Also, I don’t think Microsoft diverts pages to wawayback, I believe this guy has a plugin that does that for him, although I could of course be wrong.

Nothing has changed as far as I know.

@garlin @antspants thanks for the clarification!

When I said nothing has changed:

You can still bypass the TPM2 issue but there is no way on this earth that I know of to bypass the issue of SSE4.2 being absent from your CPU, if wanting to install Windows 24H2

Your Intel i5 7500 should be fine:
Instruction Set Extensions — Intel® SSE4.1, Intel® SSE4.2, Intel® AVX2

Two days ago I updated another non-compliant PC I had already forced to 22H2 to 24H2 using Option 3 in the tutorial here Bypass Windows 11 System Requirements on Unsupported PC

antspants said:

When I said nothing has changed:

You can still bypass the TPM2 issue but there is no way on this earth that I know of to bypass the issue of SSE4.2 being absent from your CPU, if wanting to install Windows 24H2

Click to expand...

So the old Windows 11 versions like 23H2 and 22H2 are fine to install on old CPUs without SSE4.2?

Yes.
But you still need to use a bypass for 23H2 with no TPM2 as far as I understand it, however SSE4.2 isn’t a deal breaker.

Old computers without SSE4.2 are stuck with 23H2, but they should have been retired anyway, so giving them 2-3 more years life by installing 23H2 isn't bad. Remember that end of support doesn't mean 23H2 will just stop running. It will only stop receiving new updates. Windows Defender will keep getting definition updates. If you are concerned about security, switch to a third-party antivirus and keep it updated. As long as you don't need new features and support for new hardware and applications, you can keep using 23H2 as long as you can keep the antivirus updated and of course watch where you click. Don't just click OK to get rid of a popup, it is better to click cancel if too lazy to read it.

PS: There are worse cases than being stuck with Windows 11 23H2. My HP Stream 7 tablet is locked by HP to boot in UEFI 32-bit only, so it is stuck with Windows 10 22H2 32-bit, I cannot install Windows 11 even if the CPU is a 64-bit Intel Atom Z series. Also old Intel Pentium 4 socket 478 32-bit CPU are stuck with Windows 7 32-bit, they cannot run Windows 8 or 10 32-bit because they lack PAE/NX support. Yes, they still exist, I am using an Intel Celeron 2.8GHz socket 478 at work running Windows 7 32-bit. It is much slower than an Intel Pentium 4 socket 478 with the same amount of RAM. You are blessed to run Windows 11 23H2...

antspants said:

I haven’t come across anyone for ages that felt the need to use the registry hack in question.

Click to expand...

I do it by hand.
I guess the owner of rufus also does this in his app? So that whe rufus creates the image is already pre-done.

The Registry hack is useful to test new versions of Windows 11 on a virtual machine. Why waste time to create the USB with Rufus? You just boot the latest ISO directly and enter the values in the Registry. I just remind you that it works with the old Setup interface. It might not work with the new interface (haven't confirmed it).

spapakons said:

It might not work with the new interface (haven't confirmed it).

Click to expand...

When did the new setup interface?
I downloaded on 20-10-2024 a 24H2 build x64_26100.1742 from microsoft, and with that one the reg hack was still working. (so about 2and a half month ago)

I am talking about a new (aka clean) installation, when you boot from the USB and run Setup. In 24H2 there is a new Setup interface, but you are given the choice to use the old interface. The Registry hack works with the old interface, but probably not with the new. When I was testing 24H2 in a virtual machine I first used the new interface, but it wasn't clear to me how to choose a specific partition to install, so I want back the steps and switched to the old familiar interface to avoid any mistakes.

When running Setup inside Windows in order to upgrade, you only see the familiar Windows 10/11 interface, no difference.

Ah ok, the regkey hack still works in the new layout.

Tester said:

Ah ok, the regkey hack still works in the new layout.

Click to expand...

Great! So we don't have to worry if Microsoft stops the old interface in 25H2. The hacks still work, but even if they don't Rufus will hopefully find new workarounds and implement them in a newer version.