Page 1 of 2
Has anyone else hit a wall with Secure Boot during the Win11 upgrade? My PC meet?
Posted: Tue Jan 13, 2026 7:16 am
by lasWGz
Has anyone else hit a wall with Secure Boot during the Win11 upgrade? My PC meets all the other requirements, but the PC Health Check app keeps failing on Secure Boot. In my BIOS (UEFI), it's enabled, but the TPM check still says it's unsupported. I'm getting the "This PC can't run Windows 11" error with no helpful details. Is there a specific setting I might be missing, or is it a motherboard compatibility issue?
Posted: Tue Jan 13, 2026 7:39 am
by IIDiYLHyca
I'm experiencing this too. Would love to know if anyone found a fix.
Posted: Tue Jan 13, 2026 9:33 am
by pNtaXaldUQn
I'm experiencing this too. Would love to know if anyone found a fix.
Posted: Tue Jan 13, 2026 12:17 pm
by aM33l5WvG
Agreed. Also, try clearing your TPM from the security settings in Windows—sometimes that resolves the mismatch.
Posted: Tue Jan 13, 2026 12:22 pm
by 11oxg
Yeah, same issue here. A quick tip: double-check if your drive partition style is GPT, not MBR, as that can also block it. Good luck!
Posted: Tue Jan 13, 2026 12:34 pm
by Kw4g337A8
Agreed. Another option is to check if there's a firmware update for your motherboard, as that can sometimes add proper TPM 2.0 support.
Posted: Tue Jan 13, 2026 12:46 pm
by gft17724
This. I had the same problem. For me, I had to clear my TPM in the BIOS before the PC Health Check would finally recognize it as supported.
Posted: Tue Jan 13, 2026 12:58 pm
by YQrjlaE
You could also try switching from CSM/Legacy Boot to UEFI mode in your BIOS, as that sometimes resolves the Secure Boot conflict. Let me know if that works.
Posted: Tue Jan 13, 2026 1:20 pm
by NgM3S06C3
Another option is to clear your TPM from the security settings in your BIOS, which can sometimes reset its status for the check.
Posted: Tue Jan 13, 2026 3:38 pm
by tEB3BsRY5g
Can confirm. I had the same problem. For me, clearing the TPM in BIOS didn't work until I also disabled Secure Boot, saved, rebooted, and then re-enabled it.