Ugh, so done with this?

x0Uc01 · Post by **x0Uc01** » Fri Jan 09, 2026 3:24 pm

This happened to me. I used the PC Health Check app, and it confirmed my CPU was the issue, so I just made peace with staying on Windows 10 for now.

5K67viz · Post by **5K67viz** » Sat Jan 10, 2026 11:50 am

+1 Yeah, that's exactly it. A quick tip: you can check if your specific CPU is on Microsoft's official supported list to be totally sure.

A6U6PrldR1 · Post by **A6U6PrldR1** » Sat Jan 10, 2026 12:21 pm

Agreed, and if it's not on the list, you're unfortunately stuck with Windows 10 for now on that hardware.

ttn3598716 · Post by **ttn3598716** » Sat Jan 10, 2026 7:08 pm

+1 I had the same problem with an older i5. That TPM 2.0 check is a real brick wall.

i8iJ3v2IDh · Post by **i8iJ3v2IDh** » Sat Jan 10, 2026 8:33 pm

Yeah, that's the exact same wall I hit. A quick tip: double-check if Secure Boot is enabled in your BIOS too, it's another common snag.

551hfdxaluh · Post by **551hfdxaluh** » Sun Jan 11, 2026 10:40 pm

I had the same problem. I ended up just sticking with Windows 10 on that machine—it runs perfectly, so I figured why force it?

dmUnrxRfBQ · Post by **dmUnrxRfBQ** » Mon Jan 12, 2026 8:11 pm

Same here. Yeah, that's the smart move. A quick tip: you can run the PC Health Check app to see all the exact requirements you're missing.

rze4976623 · Post by **rze4976623** » Tue Jan 13, 2026 3:26 pm

Agreed. I had the same problem with an older processor. Ended up sticking with Windows 10, which runs perfectly fine. Let me know if that works.