Page 2 of 3
Posted: Sun Jan 11, 2026 7:07 pm
by 1ug4ch
Another option is to use the Windows 10 installation media to try a repair install, which might fix the boot issue without wiping your data.
Posted: Mon Jan 12, 2026 3:57 am
by Ue1Ginb2R
Yeah, You could also try booting from that same media and using the command prompt to run a system file check with "sfc /scannow" on your drive.
Posted: Mon Jan 12, 2026 6:15 pm
by 784idz
Agreed. And if that doesn't work, you might also try the "chkdsk /f" command from that same prompt to check for disk errors.
Posted: Mon Jan 12, 2026 8:02 pm
by 6opatK6o
+1 Yeah, that's solid advice. Also, before you run chkdsk, try a simple "sfc /scannow" first—it's quicker and sometimes fixes the underlying issue.
Posted: Tue Jan 13, 2026 1:16 am
by WLUeKyV
This. I had the same problem. I ended up using a USB drive on another computer to get my important files off before doing a clean install. Let me know if that works.
Posted: Tue Jan 13, 2026 1:18 am
by 3SEyU52RgFVM
You could also try booting from a Windows 10 USB and using the repair tools from there.
Posted: Tue Jan 13, 2026 1:36 am
by 6vfwXXldrz83
Another option is to use the USB to access the command prompt and try running the bootrec commands to fix the startup. Good luck!
Posted: Tue Jan 13, 2026 4:41 pm
by 289tx
Can confirm. Before you try that, can you boot from the USB and see if you can access your files from the recovery environment?
Posted: Tue Jan 13, 2026 7:18 pm
by 88a27276O
I had the same problem. I had to use a bootable USB drive to pull my files off before doing a clean install.
Posted: Fri Jan 16, 2026 3:26 pm
by 3114mp
Agreed. Yeah, that error code is a pain. Did you try using the Windows 10 installation media to run a repair from the USB?