How to install Windows 11 24H2 RTM on unsupported PC?


Recommended Posts

I grabbed Windows 11 24H2 RTM ISO from Microsoft's server and tried using a modified appraiserres.dll to install Windows 11 24H2 on an unsupported PC, but found out that MSFT has blocked that method.

Microsoft has also blocked the  '/product server' command line method.

Does anyone knows a method that still works?

  • Sad 1

On the one hand, I wouldn't bother. You're going to find yourself with more headaches than it is worth. Go for Windows 10 or Linux instead.

But if you insist, I think Rufus circumvents the Windows 11 "requirements." Have you tried that?

  • Like 2

Instead of just blanketly saying, "It will run like crap," ... what are you running it on?

On 30/09/2024 at 16:54, Mockingbird said:

I grabbed Windows 11 24H2 RTM ISO from Microsoft's server and tried using a modified appraiserres.dll to install Windows 11 24H2 on an unsupported PC, but found out that MSFT has blocked that method.

Microsoft has also blocked the  '/product server' command line method.

Does anyone knows a method that still works?

I have windows 11 running on practically everything. Here is the specs of 1 unsupported pc I have it running on. It's a prodesk

image.png.f1e0cd97a4c809e04b58d321bd1e3391.png

I also have it running on an  i3-7100U, i7-8550U,  i7-6500U, i7-4700R, and i5-7600.

They all work great.

 

  • Like 3
On 01/10/2024 at 11:08, speedycars said:

Rufus is a no go for non-TPM2.0 PCs this time (you may still want to use the other bypass options provided by it).
Instead the HW check can be skipped with the "Setup.exe /product server" command. Tested it and it does work on a 10 years old PC. :)

Have you tried it with Windows 11 24H2?

MSFT blocked that method a while back

 

On 01/10/2024 at 13:46, Mockingbird said:

Have you tried it with Windows 11 24H2?

MSFT blocked that method a while back

 

Trying it now, in fact. You are correct. It's blocked. But Setup.exe /product server is working.

  • Haha 1
Posted (edited)

Surprising enough, "setup.exe /product server" still works on at least the one unsupported PC that I have tested so far.

It has an unsupported processor, but meets all the other system requirements (TPM, Secure Boot).

I don't have a PC older than that one, so I am going to have to borrow one when I get back later today.

On 01/10/2024 at 15:03, Mockingbird said:

Surprising enough, "setup.exe /product server" still works on at least the one unsupported PC that I have tested so far.

It has an unsupported processor, but meets all the other system requirements (TPM, Secure Boot).

I don't have a PC older than that one, so I am going to have to borrow one when I get back later today.

I can confirm that setup.exe /product sever also works on ones missing TPM 2.0

On 01/10/2024 at 18:29, Nick H. said:

I'm still curious. Why are you trying to install Windows 11 on unsupported hardware?

Because Windows 10 will be out of support in 1 year and the hardware I have is still perfectly fine. I would actually give linux a go, if only the screenconnect client for linux wasn't garbage.

  • Like 2
On 02/10/2024 at 00:35, Mockingbird said:

Why not?

Because as mentioned before, it's going to cause headaches down the line. If the headaches are only yours and you're doing it as a hobby/experiment then go nuts. I wouldn't suggest doing it for other people though...

 

On 02/10/2024 at 00:38, Warwagon said:

Because Windows 10 will be out of support in 1 year and the hardware I have is still perfectly fine. I would actually give linux a go, if only the screenconnect client for linux wasn't garbage.

Yep, Windows 10 goes out of support October 2025. That's a year away.

And I agree that Linux's RDC software has issues, but at the same time I'm working on finding a solution myself - not AnyDesk or TeamViewer, but a decent LAN-based RDC solution. And I've got a year to find something to work.

 

Like I said, I was just curious as to the need for Windows 11 compared to using something that is still officially supported.

Posted (edited)
On 01/10/2024 at 16:44, Nick H. said:

Because as mentioned before, it's going to cause headaches down the line. If the headaches are only yours and you're doing it as a hobby/experiment then go nuts. I wouldn't suggest doing it for other people though...

I have been running Windows 11 on unsupported PCs since Windows 11 came out 3 years ago.

What are these "headaches" that you are talking about?

Edited by Mockingbird
On 01/10/2024 at 18:44, Nick H. said:

Because as mentioned before, it's going to cause headaches down the line. If the headaches are only yours and you're doing it as a hobby/experiment then go nuts. I wouldn't suggest doing it for other people though...

 

Yep, Windows 10 goes out of support October 2025. That's a year away.

And I agree that Linux's RDC software has issues, but at the same time I'm working on finding a solution myself - not AnyDesk or TeamViewer, but a decent LAN-based RDC solution. And I've got a year to find something to work.

 

Like I said, I was just curious as to the need for Windows 11 compared to using something that is still officially supported.

ya, I do remote assistance with people. Other wise I would probably give linux a go.

On 02/10/2024 at 00:48, Mockingbird said:

I have been running Windows 11 on unsupported PCs since Windows 11 came out 3 years ago.

I don't know what "headaches" that you are talking about.

It's a fair cop. I can't say that I've seen many issues with people circumventing the "requirements" so far. What I do know is that if someone comes to me with an issue and I notice their machine doesn't meet whatever requirements - an outdated phone, for example -  that's where I stop my troubleshooting. Unsupported is unsupported. For my own hardware I would understand that it is me on my own to fix the issue I've potentially created.

 

On 02/10/2024 at 00:53, Warwagon said:

ya, I do remote assistance with people. Other wise I would probably give linux a go.

Funny. I need something better for LAN connectivity, but I'm able to use TeamViewer or AnyDesk for any client I need to remotely help and they are both compatible with all operating systems. But perhaps your remote assistance requires less latency than me. Maybe I'll drop you a PM sometime to talk about it further. (Y)

Posted (edited)
On 01/10/2024 at 17:05, Nick H. said:

It's a fair cop. I can't say that I've seen many issues with people circumventing the "requirements" so far. What I do know is that if someone comes to me with an issue and I notice their machine doesn't meet whatever requirements - an outdated phone, for example -  that's where I stop my troubleshooting. Unsupported is unsupported. For my own hardware I would understand that it is me on my own to fix the issue I've potentially created.

Microsoft said that the heightened system requirements in Windows 11 is the result of having visualization-based security (VBS) turned on by default in Windows 11.

Windows 10 also has visualization-based security (VBS), but it's turned off by default.

I simply turned off VBS in Windows 11 and now I have resolved the compatibility "issue".

Posted (edited)

Hello,

As previously noted on Neowin, Windows 10 will have paid support available after EOL.  That is an option if you have hardware that is not supported by Windows 11.

Regards,

Aryeh Goretsky

  • Thanks 2
On 02/10/2024 at 11:27, goretsky said:

Hello,

As previously noted on Neowin, Windows 10 will have paid support available after EOL.  That is an option if you have hardware that is not supported by Windows 11.

Regards,

Aryeh Goretsky

$61 per PC per year

no thanks

On 05/10/2024 at 17:04, JayZJay said:

There are many workarounds, which is nice once Windows 10 stops getting (free) security updates and fixes.
 

I am aware that there are unscrupulous ways to obtain Extended Security Updates (ESU) without paying, but I am not going there.

On 05/10/2024 at 23:08, Mockingbird said:

$61 per PC per year

no thanks

Hello,

Oh, that's just for the first year.  It doubles every year after that, and you must purchase them cumulatively/retroactively, i.e., if you want to purchase aftermarket support for a second year (~$120) and did not purchase for the first year (~$60), then you must purchase both years for ~$180.  It is really meant as a stopgap solution for organizations whose migration away from Windows 10 to Windows 11 won't be finished before the latter goes end of life.  Microsoft did something similar for Windows 7 but it wasn't really offered to consumers like it is this time around.

Regards,

Aryeh Goretsky
 

  • Sad 1
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.