Page 2 of 2
Posted: Fri Jan 09, 2026 1:27 pm
by s34p6e56vWj2
Agreed. I had the same problem with an older processor. Ended up sticking with Windows 10, which runs perfectly fine. Hope that helps.
Posted: Fri Jan 09, 2026 3:24 pm
by x0Uc01
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.
Posted: Sat Jan 10, 2026 11:50 am
by 5K67viz
+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.
Posted: Sat Jan 10, 2026 12:21 pm
by A6U6PrldR1
Agreed, and if it's not on the list, you're unfortunately stuck with Windows 10 for now on that hardware.
Posted: Sat Jan 10, 2026 7:08 pm
by ttn3598716
+1 I had the same problem with an older i5. That TPM 2.0 check is a real brick wall.
Posted: Sat Jan 10, 2026 8:33 pm
by i8iJ3v2IDh
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.
Posted: Sun Jan 11, 2026 10:40 pm
by 551hfdxaluh
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?
Posted: Mon Jan 12, 2026 8:11 pm
by dmUnrxRfBQ
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.
Posted: Tue Jan 13, 2026 3:26 pm
by rze4976623
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.
Posted: Tue Jan 20, 2026 9:25 pm
by 22jqymekgva
I had the same problem. That exact processor was the reason I couldn't upgrade either, so I'm just staying on Windows 10 for now. Let me know if that works.