Page 1 of 2
Has anyone else hit a constant "This PC can't run Windows 11" message during the?
Posted: Sun Jan 11, 2026 12:49 pm
by gTseTtJbXvns
Has anyone else hit a constant "This PC can't run Windows 11" message during the upgrade check? My laptop meets all the official requirements (TPM 2.0, secure boot, etc.), but it keeps failing. I also got a vague error code 0xC1900101 a couple times before it reverted to Windows 10. I've run the update troubleshooter with no luck. Any ideas on what I'm missing or how to fix this?
Posted: Sun Jan 11, 2026 1:09 pm
by HelpWizard66
I ran into this a while back. That error code often points to a driver conflict. I'd try doing a clean boot and then running the upgrade again to see if that isolates the problem.
Posted: Sun Jan 11, 2026 1:29 pm
by gxg4615
Also, have you checked if there's a pending BIOS update from your laptop manufacturer?
Posted: Sun Jan 11, 2026 2:07 pm
by 3314ouzf
Can confirm. You could also try temporarily disconnecting any non-essential peripherals, like external drives or docks, before starting the upgrade again.
Posted: Sun Jan 11, 2026 2:12 pm
by 19u1ju44v69
Same here. That error code often points to a driver conflict, so maybe check for any pending BIOS or chipset updates from your laptop manufacturer.
Posted: Sun Jan 11, 2026 2:14 pm
by FtdEOdxoCCI
+1 This happened to me too. It turned out my BIOS needed an update, even though all the main settings were correct.
Posted: Sun Jan 11, 2026 2:15 pm
by 980pyzzwv
Can confirm. Also, try temporarily disconnecting any non-essential peripherals like external drives or docks during the upgrade.
Posted: Sun Jan 11, 2026 2:15 pm
by dqiz744847
+1 Agreed, that driver fix worked for me too. A quick tip: also try temporarily disconnecting any non-essential USB devices before running the upgrade again.
Posted: Sun Jan 11, 2026 2:25 pm
by gpg909149
Yeah, I had the same problem. For me, it was a specific driver causing the 0xC1900101 error; updating my graphics driver finally let it push through.
Posted: Sun Jan 11, 2026 3:34 pm
by wdpi4365
Yeah, This happened to me too. I had to go into my BIOS and manually re-enable secure boot, even though it looked like it was already on.