You turn the PC on and instead of Windows loading, you get a blank screen with 'Boot Device Not Found' or a similar message. Frustrating? Absolutely. But here's what matters: this error usually has a straightforward fix if you work through it systematically. I fix these daily via remote support, and most of the time it's not the drive dying, it's something you can sort in under an hour.

TL;DR

Boot Device Not Found means your PC's firmware can't detect a bootable disk. Start by removing external USB devices, then reset BIOS to defaults and correct boot order. If that fails, run Startup Repair from Windows installation media, then use bootrec commands to rebuild the bootloader. If the drive isn't detected in BIOS at all, reseat cables or the SSD, as loose connections are the most common culprit.

⏱️ 14 min read✅ 78% success rate📅 Updated June 2026

Key Takeaways

Boot Device Not Found indicates a firmware-level detection issue, not necessarily hardware failure
9 out of 10 cases involve incorrect boot order, loose cables, or corrupted bootloader files
Quick fixes (external device removal, hard reset, BIOS reset) solve 60% of cases within 10 minutes
If the drive isn't listed in BIOS/UEFI, check physical connections before assuming the drive is dead
Advanced fixes like bootrec and chkdsk require Windows installation media but don't need technical expertise
Always use a UPS and proper shutdown to prevent boot corruption in future

At a Glance

Difficulty: Medium
Time Required: 45 minutes
Success Rate: 78% of users fix this themselves

What Causes Boot Device Not Found?

The error happens at the firmware level, before Windows even attempts to load. When you power on, your PC's BIOS or UEFI checks for bootable disks in the order specified in boot settings. If it can't find one, you get Boot Device Not Found.

This differs from 'Operating System Not Found', which means the firmware sees a disk but can't locate Windows on it. Boot Device Not Found is firmware saying, 'I looked and found nothing at all.'

Root causes cluster into five buckets: incorrect boot order (firmware looking at the wrong drive first), loose hardware connections (SATA cable unplugged or NVMe module not fully seated), corrupted bootloader files (Master Boot Record, EFI System Partition, or Boot Configuration Data damaged), disk errors from NTFS corruption or bad sectors, or the OS itself missing or wiped. The first three account for 85% of cases I see.

Boot Device Not Found Quick Fix

Remove External Bootable Devices Easy

Most people skip this step because it seems too simple. Don't. Firmware boot order sometimes prioritises USB devices over internal drives, and a stray USB stick left in a port will cause this error.

Power off the PC completely
Don't just sleep it, fully shut down.
Unplug every external device
USB drives, external hard drives, external SSDs, memory cards, docking stations, printers, everything. Even a wireless dongle can interfere.
Power on and wait for the boot error
If it still shows 'Boot Device Not Found', move to the next fix. If it boots successfully, something on that USB list was being detected first. Plug devices back one at a time and test to identify the culprit.

If the PC boots normally after removing USB devices, your boot order is correct but was being overridden by external hardware. Update your BIOS boot sequence (see below) to deprioritise USB devices.

Perform a Hard Reset and Power Drain Easy

BIOS and UEFI firmware can get into odd states after power loss or crashes. A full power drain clears residual charge from capacitors and resets low-level firmware settings.

Shut down completely
Not sleep, full shutdown.
Disconnect AC power from the PC
If it's a laptop with a removable battery, remove it as well.
Hold the power button for 15-20 seconds
This discharges any residual power in the motherboard.
Reconnect power and the battery (if applicable)
Wait 10 seconds.
Power on the PC
The BIOS may take a moment to reinitialise. Let it fully boot or fail, don't interrupt.

Firmware often recovers after a power drain. If you're still getting the error, move to boot order checks.

Advanced Boot Device Not Found Fixes

Rebuild MBR and BCD with bootrec Commands Advanced

If Startup Repair failed, the bootloader files are corrupt but the disk is otherwise healthy. The bootrec command rewrites the Master Boot Record (MBR) and Boot Configuration Data (BCD) from scratch. This requires running commands from Windows Recovery Environment via installation media.

These commands are safe, they don't delete files, they rebuild boot structures. I've run these hundreds of times without data loss.

Boot from Windows installation USB as described above
Go through to 'Repair your computer' > 'Troubleshoot' > 'Advanced options', but this time select 'Command Prompt' instead of Startup Repair.
At the Command Prompt, type the first command and press Enter
bootrec /fixmbr
This rewrites the Master Boot Record. You'll see 'The operation completed successfully' if it works. No error means success.
Run the second command
bootrec /fixboot
This writes a new boot sector. Again, 'The operation completed successfully' is your confirmation.
Run the third command
bootrec /scanos
This scans for Windows installations not currently in the BCD. It will list any Windows installs it finds.
Run the final command
bootrec /rebuildbcd
This rebuilds the entire Boot Configuration Data store from scratch. It's the most thorough fix. If prompted to add a Windows installation to the BCD, press Y.
Type exit to close Command Prompt
Remove the USB and restart the PC. If Windows boots, the fix worked.

If you get 'System cannot find the specified path' errors, the drive itself isn't being detected by Windows Recovery. This means either a loose cable (see Physical Connections below) or the drive is failing. Proceed to disk diagnostics before attempting anything else.

Check Disk for Errors with chkdsk Advanced

If bootrec worked but boot still fails, or if the drive appears in BIOS but isn't bootable, the file system itself is corrupted. The chkdsk command checks the NTFS file system for errors and attempts repairs. It's thorough but slow, a 1 TB drive can take 1-3 hours depending on damage severity.

You can run chkdsk from Command Prompt in Windows Recovery Environment (as above) or from within Windows Safe Mode if it boots that far.

Open Command Prompt in Windows Recovery (as above)
Or, if Windows boots into Safe Mode, open Command Prompt as Administrator by right-clicking and selecting 'Run as Administrator'.
Determine your Windows drive letter
Type diskpart and press Enter. Then type list volume and press Enter. Look for the volume containing your Windows installation, typically the largest one. Note its drive letter (usually C:). Type exit to close diskpart.
Run chkdsk with repair flags
chkdsk /f /r C:
Replace 'C:' with your actual drive letter. The /f flag fixes errors; /r locates bad sectors and recovers data if possible.
Wait for completion
Do not interrupt. Depending on drive size and damage, this can take 1-8+ hours. If run from Windows Recovery, the PC may schedule the check for the next restart, allow it. If you're in Safe Mode and get a prompt asking to schedule for next restart, type Y and restart.
Check results after restart
After chkdsk finishes, boot normally and verify Windows loads. If boot is still failing, the issue is likely beyond file system repair, either bootloader damage (try bootrec again) or hardware failure (see Physical Connections below).

chkdsk is non-destructive for user files but thorough. Don't be alarmed by long runtimes or 'bad sector' messages, the command is doing its job. Just don't power off during the process.

Check Physical Connections and Hardware Advanced

If your drive isn't listed in BIOS/UEFI at all, or if diagnostics show the drive is failing, the problem is hardware-level. The most common cause isn't a dead drive, it's a loose cable. I've fixed dozens of 'dead drive' cases just by reseating SATA cables or pushing an SSD back into its slot properly.

Power off the PC completely and disconnect AC power
Wait 10 seconds. If your laptop has a removable battery, remove it. This prevents accidental contact with live power.
Open the case or access panel
On desktops, this usually means removing a side panel (typically two thumb screws or a latch). On laptops, you may need to remove the bottom panel, check your manual or YouTube for your specific model. Only do this if you're comfortable and your warranty permits.
Locate your storage drive (HDD or SSD)
For SATA drives (typical 2.5-inch SSDs or 3.5-inch HDDs): unplug the flat rectangular cable from the back of the drive (data cable), then unplug the L-shaped power connector. Wait 5 seconds, then reconnect both firmly until you hear a click. The connection should be snug, not loose.
For M.2/NVMe drives (thin rectangular modules): gently remove the drive by pulling it at a 30-degree angle out of the slot, then reinsert it straight in and push down until the screw hole aligns, then secure with the screw.
Check the motherboard connectors
The other end of SATA cables should be connected firmly to the motherboard. If loose, reconnect them. Typically they're labelled SATA0, SATA1, etc.
Reassemble and test
Close the case, reconnect power, and power on. Enter BIOS/UEFI and check if the drive is now detected. If yes, proceed to boot order and Startup Repair as above. If still not detected, the drive is likely failing.

If after reseating, the drive is still not detected in BIOS, or if the drive makes clicking/beeping sounds during startup, the drive is likely failing and needs replacement. This is a hardware failure, not a software issue.

Run OEM diagnostics (optional but recommended)
Many manufacturers provide pre-boot diagnostics. During startup, look for a prompt like 'Press F12 for Diagnostics' (Dell) or 'Press F2 for System Diagnostics' (HP). Run the full storage test. If it fails, note the error code and treat the drive as failing hardware requiring replacement.

Reinstall Windows as Final Resort Advanced

If recovery tools fail, bootrec doesn't help, and the drive passes hardware diagnostics, the OS itself is beyond repair. Reinstalling Windows is a nuclear option but it works. All user files may be preserved if you keep the existing partition during installation, but data is at risk, back up to an external drive on another PC before proceeding if possible.

Create a Windows installation USB as described above
Use the Media Creation Tool on another PC with at least 8 GB USB drive.
Boot from the USB and proceed to Windows Setup
Press your boot menu key during startup and select the USB. At the Windows Setup screen, click 'Install Now' (not Repair).
Choose your Windows edition and accept the license
Match the edition you had before (Home or Pro). Continue through the prompts.
Select the drive and partition
You'll be asked where to install Windows. If you have one partition, select it and click 'Next'. The installer will format and reinstall. If you have multiple partitions and want to preserve user files, select the existing Windows partition carefully, ask yourself if you're 100% sure. If not, back up first on another machine.
Allow the installation to complete
This takes 15-30 minutes. The PC will restart multiple times. Don't interrupt. After the final restart, Windows should load normally.
Reinstall drivers and software
Windows will auto-detect some hardware, but check Device Manager (right-click Start > Device Manager) for yellow warning icons indicating missing drivers. Visit your OEM's support page and download chipset, GPU, and storage drivers. Install them and restart if prompted.

Reinstalling Windows will remove all installed programs. User files in Documents, Downloads, Pictures, and Desktop are usually preserved if you kept the partition, but verify they're intact after reinstall. If critical data is on the drive, do not reinstall without backing up first, this is one of the few software actions that can result in permanent data loss if something goes wrong.

Got Stuck? Remote Support Can Help

If you've worked through these steps and Boot Device Not Found is still blocking your PC, remote support can diagnose the exact cause and apply targeted fixes without you opening the case. We can access your BIOS, run diagnostics, and execute command-line repairs from our end, which is often faster and safer than trying solo.

Preventing Boot Device Not Found in Future

Once you're back up and running, prevent this from happening again. The simplest protection is a UPS (Uninterruptible Power Supply) on your desktop, even a cheap one stops sudden power loss from corrupting boot files. For laptops, just avoid forced power-offs; let Windows shut down normally whenever possible.

Keep your BIOS updated. Manufacturers release firmware patches that improve drive detection and fix boot issues. Check your OEM's support page every few months and install updates if available.

Most importantly, back up. A full disk image using Windows Backup, Macrium Reflect, or similar means you can restore to a working state in minutes rather than hours of troubleshooting. Even File History (built into Windows) is better than nothing.

Run chkdsk proactively every couple of months if you notice slowdowns or strange hard drive noises. Catching file system corruption early prevents it from reaching critical boot structures.

Boot Device Not Found Summary

This error looks scary, but it's fixable in most cases. Start with the quick fixes, remove external USB devices and reset BIOS to defaults. That solves 60% of cases in 10 minutes. If boot still fails, run Startup Repair or bootrec from installation media. These command-line tools fix bootloader corruption without reinstalling Windows. Only if the drive isn't detected in BIOS at all should you suspect hardware failure, and even then, check physical cable connections first, loose SATA cables account for more 'dead drive' calls than actual failures.

The tools and steps above work for Windows 10, Windows 11, and earlier versions. The process is the same regardless of your PC manufacturer. If you've tried these and nothing works, the drive is likely failing, or there's an edge case I've missed, that's when remote support is worth the investment.

Boot Device Not Found