To fix Windows 10 not booting, match the exact symptom first: black screen, Automatic Repair loop, or “no boot device” error, then use the least risky repair that fits. I always start by identifying the screen, because the wrong fix can cost time, break a working boot entry, or make file recovery harder. This guide walks through each boot failure message and the fastest safe fix path for Windows 10.
What Windows 10 boot failures usually mean
The symptom usually tells you whether Windows cannot load, the drive is not being found, or the boot files are damaged. Start with Startup Repair from Windows Recovery Environment (WinRE) when normal boot fails, since it is usually the least intrusive first step and can lead to Advanced options or Command Prompt if needed.
How to read the symptom before you try any fix
A black screen can point to a display issue, a driver problem, or a failed update. A repeated repair loop often suggests that boot files or BCD entries may be damaged. A “no bootable device” or “boot device not found” message often points to firmware boot order, a drive not being detected, or a boot-mode mismatch.
What a black screen, repair loop, and boot device error usually point to
Bad update, wrong UEFI/BIOS boot order, corrupted Boot Configuration Data (BCD), missing EFI boot files, drive detection trouble, and damaged system files are the common suspects. Less often, the issue is a failing SSD or HDD, or a driver that stops Windows during early startup.
Likely causes, ranked from most common to least common
The fastest path is to check the most likely cause for the exact screen first. Recent updates and drivers are frequent after a normal shutdown. Wrong boot order and corrupted boot entries are common when the system drive still works but Windows will not load. Drive detection and hardware problems come next.
| On-screen error | Likely cause | Safest first action | Exact WinRE tool to use | Data-loss risk |
|---|---|---|---|---|
| No bootable device | Wrong UEFI/BIOS boot order or drive not detected | Check firmware sees the internal drive and place it first | UEFI/BIOS setup, then WinRE Command Prompt if needed | Low |
| Boot device not found | Drive detection failure, bad cable, or wrong boot mode | Confirm the drive appears in firmware and test boot mode | UEFI/BIOS setup | Low |
| Startup Repair loop | Corrupted boot files or BCD entries | Run Startup Repair once, then use Command Prompt | Startup Repair, Command Prompt | Low to medium |
| Black screen | Bad update, driver, or display startup problem | Try Safe Mode or uninstall the latest update | Safe Mode, Uninstall updates, System Restore | Low |
| Post-update failure | Recent quality or feature update, or a bad driver | Roll back the update or restore to a known good point | Safe Mode, System Restore | Low |
Did Windows stop booting after an update?
When the failure starts right after an update, Safe Mode from WinRE is a sensible place to begin, then remove the recent update or roll back with System Restore if available. That path keeps personal files intact and avoids command-line repairs when the issue is probably a bad update or driver.
Enter Safe Mode from WinRE
- Power on the PC and interrupt boot three times to open WinRE.
- Select Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 for Safe Mode or 5 for Safe Mode with Networking.
Uninstall the latest quality or feature update
- In WinRE, go to Troubleshoot > Advanced options > Uninstall Updates.
- Choose Uninstall latest quality update first.
- If that fails, try Uninstall latest feature update.
Use System Restore if there is a restore point
- Open Troubleshoot > Advanced options > System Restore.
- Select a restore point dated before the update or driver change.
- Complete the restore and let the PC restart.
Is this a no bootable device or boot device not found error?
Those messages usually mean firmware cannot find a valid boot path, not that Windows is always broken. The first check is whether the internal drive appears in UEFI or BIOS. If it does, fix boot priority and boot mode before touching boot records or reinstalling anything.
Check whether the system drive is detected in UEFI or BIOS
- Restart and enter firmware setup with the key shown on screen, often F2, Del, or Esc.
- Look for Storage, NVMe, SATA, or Boot information.
- If the drive is missing, power down and check cable or seat the drive again.
Fix boot order so the internal drive is first
- Open the Boot section in UEFI or BIOS.
- Move the internal Windows drive or Windows Boot Manager to the top.
- Save changes and restart.
Confirm the correct boot mode for the installed Windows version
- In firmware, check whether the machine is set to UEFI or Legacy/CSM.
- Match that mode to how Windows was installed.
- If Windows was installed in UEFI mode, keep UEFI enabled and prefer Windows Boot Manager.
Why does Windows keep going back to Startup Repair?
A repair loop means Startup Repair found a startup fault but did not fully fix it. Run Startup Repair once from WinRE, then switch to manual repair if the loop returns. At that point, the boot files or BCD are often damaged enough that automatic repair cannot finish the job.
Run Startup Repair from WinRE once
- Open Troubleshoot > Advanced options > Startup Repair.
- Select the target Windows installation if prompted.
- Let it finish, then reboot once.
Use Command Prompt to inspect and rebuild BCD entries
- Go to Troubleshoot > Advanced options > Command Prompt.
- Run bootrec /fixmbr.
- Run bootrec /rebuildbcd.
- If Windows still will not start, continue with bcdboot.
Know when a failed repair points to missing boot files
If the system uses UEFI and the EFI boot files are missing, bootrec may not finish the job. That is where bcdboot.exe fits: it recreates boot files and is often the better choice when the boot partition exists but the startup files do not.
Use Command Prompt to repair boot files and the boot record
WinRE Command Prompt is the right place for low-level startup repair when Startup Repair and Safe Mode do not fix the issue. bootrec.exe helps with the master boot record and BCD store. bcdboot.exe is the stronger option when EFI or system boot files need to be recreated.
Run bootrec.exe commands from WinRE
- Open Command Prompt from Advanced options.
- Type bootrec /fixmbr and press Enter.
- Type bootrec /rebuildbcd and press Enter.
- Restart and test boot again.
When bootrec is not enough and bcdboot.exe is the better fix
- In Command Prompt, identify the Windows drive letter and, if present, the EFI partition.
- Run bcdboot C:\Windows to copy fresh boot files, replacing C: if Windows is on a different letter in WinRE.
- If needed, add the firmware target for UEFI with the appropriate boot files on the EFI partition.
How WinRE Command Prompt fits into the recovery flow
WinRE is the recovery entry point when normal boot fails. From there, the path is simple: Startup Repair first, Safe Mode for update or driver removal, then Command Prompt for boot records and boot files. That order avoids unnecessary file damage.
Symptom-to-repair matrix
Use this table to stop guessing. Match the screen first, then take the least risky action that fits the failure. If the drive still opens in recovery, copy files before moving to destructive repairs.
| On-screen error | Likely cause | Safest first action | Exact WinRE tool to use | Data-loss risk |
|---|---|---|---|---|
| No bootable device | Boot order wrong or drive not detected | Check UEFI/BIOS drive detection and boot priority | UEFI/BIOS setup | Low |
| Boot device not found | Drive missing, bad cable, or wrong boot mode | Confirm the internal drive appears, then match boot mode | UEFI/BIOS setup | Low |
| Startup Repair loop | Corrupted boot files or BCD | Run Startup Repair once, then use bootrec or bcdboot | Startup Repair, Command Prompt | Low to medium |
| Black screen | Driver, update, or display startup failure | Boot Safe Mode and uninstall the latest change | Startup Settings, Uninstall Updates, System Restore | Low |
| Post-update failure | Recent patch or driver change | Uninstall the update or restore to an earlier point | Uninstall Updates, System Restore | Low |
Still not working?
If the drive is still readable in WinRE, copy personal files first before trying a destructive repair. If Startup Repair, Safe Mode, bootrec, and bcdboot all fail, use Reset this PC with Keep my files as the last repair step before a clean reinstall.
Back up files before any destructive step if the drive still opens in recovery
- Open Command Prompt or Notepad from WinRE.
- Copy user folders to an external drive.
- Do this before Reset this PC or reinstalling Windows.
Use Reset this PC with keep my files as the last repair step
- Go to Troubleshoot > Reset this PC.
- Choose Keep my files.
- Follow the prompts and reinstall only the Windows system files and apps.
When to stop and look at the drive, firmware, or hardware
If the drive does not appear in UEFI or BIOS, repeated repair commands will not fix it. At that point the problem may be a failing drive, loose connection, or firmware issue. If the system still refuses to boot after several repairs, outside help is the safer move.
Frequently asked questions
how to fix windows 10 not booting command prompt
Open Troubleshoot > Advanced options > Command Prompt in WinRE, then run bootrec /fixmbr and bootrec /rebuildbcd. If Windows still will not start, use bcdboot C:\Windows to rewrite boot files for the Windows installation that exists on the disk.
how to fix windows 10 not booting after update
Use Troubleshoot > Advanced options > Startup Settings, boot into Safe Mode, then uninstall the latest quality update from Uninstall Updates. If a restore point exists, System Restore is the better next step because it rolls back drivers and registry changes too.
how to repair windows 10 not booting
Start with Startup Repair from WinRE. If that fails, move to Safe Mode for update removal, then use Command Prompt repairs for BCD and boot files. If the internal drive is not detected in firmware, fix that first or the software repairs will not help.
how to fix windows 10 no bootable device
Enter UEFI or BIOS setup and check that the internal drive or Windows Boot Manager is first in boot order. If the drive is present, confirm the machine is using the correct boot mode. If the drive is missing, inspect the cable or reseat the device.
how to fix windows 10 boot device not found
Check drive detection in firmware, then match boot mode to the Windows install. If the drive shows up but Windows still will not load, go to WinRE Command Prompt and rebuild the boot records with bootrec /rebuildbcd or recreate boot files with bcdboot.
how to repair windows 10 if it does not boot
Use the least risky ladder: Startup Repair, Safe Mode, uninstall updates, System Restore, then Command Prompt repair. If none of that works and the drive still opens, copy files out before choosing Reset this PC with Keep my files or a full reinstall.