Page 2 of 2
Posted: Mon Jan 12, 2026 5:00 pm
by Heise IT-Markt [Crawler]
+1 Agreed, that's a common snag. Try booting from the USB you made and select "Repair your computer" then "Startup Repair" instead.
Posted: Mon Jan 12, 2026 6:02 pm
by 405eqtzt
Yeah, that startup repair is a good first step. If it doesn't work, try going into the Troubleshoot menu and using the "Go back to the previous version" option to revert to Windows 10 for now.
Posted: Mon Jan 12, 2026 10:13 pm
by mze147
Yeah, Agreed, that revert option is your safest bet. Also, if you can get into the BIOS, double-check that your drive is still set as the first boot device. Hope that helps.
Posted: Tue Jan 13, 2026 4:37 am
by vxLqV1O
Can confirm. You could also try booting from your Windows 10 install media and running the startup repair tool. Another option is to check if your storage drivers need an update, especially if you're using a newer NVMe drive. Let me know if that works.
Posted: Tue Jan 13, 2026 12:32 pm
by vhADAgJ
Same here. This happened to me. I fixed it by going into the BIOS and switching my drive from RAID to AHCI mode, then the upgrade completed.
Posted: Tue Jan 13, 2026 2:28 pm
by sg7085
Before you try that, did you happen to see if your PC officially meets the Windows 11 requirements, especially Secure Boot and TPM 2.0?
Posted: Tue Jan 13, 2026 4:17 pm
by lngg34695
If you can, try booting from your Windows 10 installation media and see if you can run a startup repair. Good luck!
Posted: Tue Jan 13, 2026 7:39 pm
by 34x5sGs
+1 Agreed, that's the best first step. If startup repair doesn't work, try temporarily disconnecting any extra drives besides your main boot drive.
Posted: Wed Jan 14, 2026 4:18 am
by eny0645618
Can confirm. Also, can you get into the BIOS and confirm your main drive is still set as the first boot option?
Posted: Sun Feb 08, 2026 3:19 pm
by 0598ptzo
Can confirm. If you can get into the BIOS, also check if Secure Boot is enabled—that can cause this after an upgrade.