Page 2 of 2
Posted: Tue Jan 13, 2026 12:16 am
by yoq589s5
Can confirm. You could also try booting into safe mode and running a startup repair from there.
Posted: Wed Jan 14, 2026 1:28 am
by KGflsFUXGKM
+1 If you can get into safe mode, try running "sfc /scannow" in the command prompt to check for system file corruption. Good luck!
Posted: Wed Jan 14, 2026 3:38 pm
by gqim14
You could also try a startup repair from the Windows recovery environment. Another option is checking if a recent BIOS update from your motherboard manufacturer is available.
Posted: Wed Jan 14, 2026 5:10 pm
by DMBnWYz
+1 Yeah, and if you can get into recovery, try running the bootrec commands to fix the boot sector.
Posted: Sat Jan 17, 2026 2:27 am
by x6SB8D6g
Yeah, I had the same problem. For me, it turned out to be a driver conflict with an old peripheral I had plugged in.
Posted: Tue Jan 20, 2026 5:12 pm
by 6p93adtjD1
Same here. You could also try booting into safe mode and rolling back the update to see if that gets you running again.
Posted: Sat Feb 07, 2026 10:24 pm
by 9nWXOw
Agreed. Yeah, safe mode is a good call—if you can get into it, try running "sfc /scannow" from the command prompt to check for system file corruption.