How to Fix No Boot Device Found: Causes, Fixes, and Data Safety Tips

TLDR: The "no boot device found" error means your computer's firmware completed its startup checks but couldn't locate a drive with a valid operating system. Knowing how to fix no boot device found comes down to correcting the BIOS boot order, repairing corrupted boot files with bootrec commands, or reseating a loose cable without reinstalling Windows. Follow the steps below in order for the fastest path to a working machine.

What You'll Achieve (and What You Need Before You Start)

By the end of this guide, your computer will boot normally again. The no boot device found error stops your system before Windows even loads, which means the fix happens at the firmware or drive level, not inside Windows itself. This guide walks through every solution in sequence, from a 30-second USB removal to running command-line boot repair tools.

This error appears across HP, Dell, Lenovo, and custom-built PCs running both Windows 10 and Windows 11, so the steps here apply regardless of your hardware brand.

Before you begin, gather the following:

Work through the steps in order. Each fix is faster and less invasive than the one after it, so skipping ahead wastes time if an earlier step would have solved the problem.

What Is the 'No Boot Device Found' Error and Why Does It Happen?

The error means your BIOS or UEFI firmware completed its Power-On Self-Test (POST), the hardware checks that run every time you press the power button, but scanned every connected drive and found nothing it could boot from. Without a valid bootable partition to hand off control to, the system stops and displays the message. If you're dealing with related startup problems, the same BIOS and boot file causes apply.

For Dell laptop users searching "no bootable devices found Dell laptop" specifically: Dell machines are particularly prone to boot order resets after BIOS updates, which frequently surfaces this exact error with no underlying hardware problem.

Boot devices not found on Windows 10 and Windows 11 behave identically at the firmware level, so every fix in this guide applies to both versions.

Step 1: Perform a Hard Reset and Remove External Devices

Simply removing external devices resolves the boot device not found error more often than most people expect. When a USB drive, SD card, or disc is inserted at startup, the BIOS may attempt to boot from it. And if that device has no operating system on it, the system reports no bootable device found and stops.

Follow these steps:

1. Shut down the PC completely. Do not use Restart, power it fully off.

2. Disconnect every external device. Remove all USB drives, SD cards, external hard drives, and any disc from the optical drive. Check every port: front, back, and side panels on desktops.

3. For laptops with a removable battery: Remove the battery, hold the power button for 30 seconds to discharge residual power, then reinsert the battery.

4. For laptops with a non-removable battery: Hold the power button for 15 seconds while unplugged.

5. Power the machine back on and watch whether the error persists.

Common mistake: Desktop users often forget USB devices plugged into rear-facing ports. Check those before moving on; it takes ten seconds and occasionally saves an hour of unnecessary troubleshooting.

This single step resolves the error in a significant portion of cases, particularly where a USB drive was accidentally left in overnight.

Step 2: Check and Fix BIOS Boot Order Settings

Fixing the BIOS boot order settings is the most reliable first software step for how to fix no boot device found. Verifying BIOS boot order is one of the first actions to take when diagnosing this error. Here's how to access BIOS and correct the configuration.

Enter BIOS using the key for your manufacturer:

Press the key repeatedly immediately after pressing the power button — timing matters.

Once inside BIOS:

1. Navigate to the Boot tab or Boot Options menu.

2. Check what's listed first. Your internal SSD or HDD should be in position 1.

3. If no internal drive appears at all, skip to Step 3; this indicates a connection or drive failure, not a configuration issue.

4. If the drive is listed but not first, use the on-screen keys (typically F5/F6 or +/−) to move it to position 1.

5. Check boot mode. If your drive uses GPT (standard on Windows 11 and most Windows 10 installs after 2018), confirm Boot Mode is set to UEFI, not Legacy or CSM.

6. Press F10 to save and exit, then restart.

Common mistake for users who recently enabled virtualization technology: Some firmware versions automatically switch from UEFI to Legacy/CSM when VT-x or AMD-V is enabled. Re-enabling UEFI mode without disabling virtualization fixes the "boot device not found" error after enabling virtualization technology. The dedicated section later in this guide covers this in full.

What It Means When Your Drive Is Completely Invisible in BIOS

If the SSD or HDD does not appear anywhere in BIOS. It’s not in the boot list, not in the storage detection menu; that is a hardware problem, not a settings problem. A missing drive points to a loose cable, a failed drive, or a failed controller. Desktop users should proceed to Step 3. Laptop users should skip to Step 5, since internal drive access varies significantly by model and attempting it without the correct service manual risks further damage.

Step 3: Inspect Physical Hard Drive Connections and Hardware

A loose SATA cable is one of the most overlooked hardware causes of the no bootable devices found error, especially on desktops that have been moved, transported, or recently opened.

For desktop users:

⚠ Before touching any internal components: Discharge static electricity by touching a bare metal surface on the chassis, or use an anti-static wrist strap.

1. Power down completely and unplug from the wall outlet.

2. Open the case and locate the SATA data cable running from your hard drive or SSD to the motherboard.

3. Press both ends firmly — at the drive and at the motherboard. SATA connectors can work partially loose without looking disconnected.

4. Check the SATA power cable from the PSU. Disconnect and reconnect it.

5. Try a different SATA port on the motherboard — ports occasionally fail.

6. For NVMe M.2 SSDs: Remove the retention screw, reseat the drive firmly, and replace the screw. An unseated M.2 drive will not appear in BIOS.

For laptop users: Internal drive access requires removing the bottom panel and varies by model. Consult your manufacturer's service manual before opening the chassis.

After reseating connections, power the machine on and enter BIOS to confirm the drive now appears before attempting software fixes. If you need additional hard drive troubleshooting steps, that resource covers deeper diagnosis for drives that remain undetected after reseating.

Step 4: Use Windows Automatic Repair to Fix Boot Files

Windows includes built-in recovery tools for Windows boot recovery that repair this without reinstalling the OS or touching personal files — and understanding how to fix no boot device found at this level is where most readers find their solution.

Steps:

1. Create a Windows Recovery USB on a working computer. Go to Microsoft's Media Creation Tool page, download the tool, choose "Create installation media," and write to your 8GB+ USB drive. This process applies to both Windows 10 and Windows 11.

2. Insert the USB and power on the affected PC. You may need to enter BIOS (Step 2) and temporarily set USB as the first boot device.

3. Select language and keyboard layout, then click "Repair your computer" — do not click Install.

4. Go to Troubleshoot > Advanced Options > Startup Repair. Let Windows attempt automatic repair (5–15 minutes).

5. If Startup Repair fails, return to Advanced Options and open Command Prompt.

6. Run the bootrec commands in sequence (see below).

7. Type exit, remove the USB, and restart.

Common mistake: Many guides tell you to run one or two bootrec commands. Run all four in this exact order — each addresses a different layer of the boot configuration.

The Exact Commands to Type and What Each One Does

Open Command Prompt from the Windows Recovery Environment and type each command, pressing Enter after each:

bootrec /fixmbr

bootrec /fixboot

bootrec /scanos

bootrec /rebuildbcd

• bootrec /fixmbr — Rewrites the master boot record without touching partition data

• bootrec /fixboot — Writes a fresh boot sector to the active partition

• bootrec /scanos — Scans for all Windows installations across connected drives

• bootrec /rebuildbcd — Rebuilds the Boot Configuration Data with found installations

"Access is denied" after bootrec /fixboot? This happens when Windows cannot write to the EFI System Partition directly. If you receive Access is denied after running bootrec /fixboot, use this workaround:

diskpart

select disk 0

list partition

Identify the EFI partition (usually 100–500MB, Type: System). Then:

select partition number

assign letter=Z

exit

bootrec /fixboot

This assigns a drive letter to the EFI partition so bootrec can write to it. Once the command completes, type exit and restart.

Step 5: Diagnose Whether Your Hard Drive Has Failed

In professional repair environments, this scenario is more common than most users expect. In repair shops, technicians regularly see machines where a customer worked through every available software fix — bootrec commands, BIOS resets, Startup Repair — only to discover the drive was failing hardware the entire time. The critical insight from those cases: diagnosing drive health before further power cycling is what separates recoverable data from permanently lost data.

Steps to diagnose drive health:

• Boot from the Windows Recovery USB created in Step 4.

• Open Command Prompt and run:

chkdsk C: /f /r /x

• The /r flag scans for bad sectors — a leading cause of boot failures on aging drives. This can take 1–3 hours depending on drive size. For additional hard drive troubleshooting guidance, that resource covers SMART data interpretation and manufacturer diagnostic tools in more depth.

• Alternatively, download a manufacturer diagnostic tool: SeaTools for Seagate drives, or Western Digital Dashboard for WD drives.

• Run the Extended or Long test. If the drive fails, it needs physical replacement.

• If the drive passes diagnostics but the error persists, return to Step 4 or proceed with a clean Windows reinstall.

Important note about SSDs: Unlike HDDs, SSDs fail without warning sounds. No clicking or grinding. Don't assume silence means the drive is healthy.

If you hear clicking or grinding from an HDD, stop powering the machine on. Those sounds indicate imminent read/write head failure, and each additional power cycle risks permanent data loss. Professional data recovery becomes significantly more difficult once a drive is fully unresponsive.

Machines under manufacturer warranty with a confirmed failed drive should go through the warranty process rather than out-of-pocket replacement.

Need professional help? If you've worked through every step and your PC still won't boot, a professional PC repair service can diagnose and fix the issue — including data recovery if your drive has failed. Don't risk further data loss by continuing to power cycle a failing drive.

When the Error Happens on Specific Brands: Dell, HP, and Lenovo Notes

Brand-specific quirks cause enough variation in how this error appears and gets fixed that a structured reference is worth having.

Dell: The ePSA diagnostic is one of the fastest ways to rule out hardware failure before spending time on software fixes. At the Dell startup screen, press F12 and select Diagnostics — it reports drive status within minutes. Dell users also frequently encounter "no bootable devices found" after a BIOS firmware update that resets boot order. Always recheck boot order after any BIOS update on a Dell machine.

HP: HP's UEFI Firmware Settings (F2 at startup) includes a dedicated Hard Drive Self Test. Run this before attempting bootrec commands — if HP's test flags the drive, proceed to professional diagnosis rather than software repair. HP machines also occasionally require Secure Boot to be temporarily disabled to allow recovery USB booting.

Lenovo: The F12 boot menu provides a quick way to select a boot device without entering full BIOS. OneKey Recovery can restore the system to factory state — useful as a last resort when all other fixes have failed and data has already been backed up.

The One Cause Most Guides Miss: Virtualization Technology and Secure Boot Conflicts

Re-entering BIOS boot settings to correct the boot mode is the fix, and almost no troubleshooting guides address this specifically. For users searching for how to fix no boot device found after a recent BIOS change, this section covers the mechanism in full.

Here's what happens: when you enable Intel VT-x or AMD-V (commonly done to use WSL2, Hyper-V, VirtualBox, or VMware), some firmware implementations automatically switch Boot Mode from UEFI to Legacy/CSM, or silently disable Secure Boot. A Windows installation on a GPT-partitioned drive requires UEFI mode to boot. If the firmware switches to Legacy/CSM, the system can no longer read the GPT boot partition — so it reports no boot device identified and stops.

The fix does not require disabling Virtualization Technology:

Steps to fix:

1. Enter BIOS using your manufacturer's key (reference Step 2).

2. Confirm Virtualization Technology remains Enabled.

3. Set Boot Mode to UEFI.

4. Re-enable Secure Boot if it was auto-disabled.

5. Disable CSM/Legacy Support if it appears as a separate toggle.

6. Save (F10) and restart.

This configuration correction resolves boot devices not found after enabling virtualization technology for the majority of affected users. The common mistake is disabling virtualization entirely — that works but removes the functionality you enabled. Correcting only the boot mode setting achieves both goals simultaneously.

When to Stop Troubleshooting and Call a Professional

There are clear signals that DIY troubleshooting has reached its limit for resolving no boot device found errors, and recognizing them early protects your data.

Stop and call a professional if any of the following are true:

• The internal drive does not appear anywhere in BIOS after reseating all connections

• The chkdsk scan reports multiple bad sectors or cannot complete

• A manufacturer's diagnostic tool reports drive failure

• You hear clicking, grinding, or repeated seek sounds from the hard drive

• bootrec commands return persistent errors across multiple attempts

• The machine was dropped or exposed to liquid before the error appeared

Clicking sounds from an HDD indicate imminent read/write head failure. Each additional startup attempt can cause the head to physically damage the platter surface, destroying data that would otherwise be recoverable. Professional data recovery becomes significantly more difficult once a drive is fully unresponsive.

A professional technician brings tools not practical at home: specialized imaging hardware that clones a failing drive sector-by-sector before it fully dies, deep diagnostic software that reads drive firmware logs, and component-level repair capabilities. A written diagnosis also documents exactly what failed — useful for warranty claims, insurance purposes, or IT records.

Not every boot device not found error requires professional help. If your drive appears in BIOS, passes diagnostics, and the bootrec commands complete without errors, you can resolve the issue yourself using this guide. But the signs listed above are clear indicators that professional intervention will save both time and data.

Frequently Asked Questions

⚠ Editor's flag for client review: This FAQ section and the closing conclusion paragraph below it were not included in the original content brief and have no assigned word count or keyword targets. Please confirm whether to publish, cut, or revise before this article goes live. If cut, no instructional content is lost.

What does 'no boot device found' mean?

The "no boot device found" message means your BIOS or UEFI firmware completed all hardware startup checks but could not find a drive containing a valid, bootable operating system. Common causes include an incorrect boot order pointing to an empty USB drive, corrupted boot files, or a drive that has physically failed or disconnected.

How do I fix 'no boot device found' without reinstalling Windows?

Run the bootrec command sequence from a Windows Recovery USB: bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, and bootrec /rebuildbcd in that order. These commands repair the Master Boot Record and rebuild the Boot Configuration Data without touching your files. The majority of software-caused cases are fixable this way, with no reinstallation required.

Why does my Dell laptop say no bootable devices found?

The most common Dell-specific causes are a BIOS boot order reset after a firmware update, a Secure Boot conflict, or a loose SSD connection. Press F12 at startup and run the ePSA Diagnostics tool first — it identifies whether the issue is hardware or configuration within minutes.

Can enabling virtualization cause boot device not found?

Yes. Enabling Intel VT-x or AMD-V in BIOS can automatically switch Boot Mode from UEFI to Legacy/CSM on some firmware versions. A Windows installation on a GPT-partitioned drive requires UEFI mode, making the drive appear non-bootable after that switch. Re-enter BIOS, leave Virtualization Technology enabled, and manually set Boot Mode back to UEFI with Secure Boot re-enabled.

How long does it take to fix a no boot device error?

Correcting the BIOS boot order takes under five minutes. Removing an accidentally inserted USB drive takes thirty seconds. Running the full bootrec command sequence takes 10–20 minutes. A chkdsk scan on a large mechanical hard drive can run one to three hours. If hardware replacement is needed, add time for parts sourcing and installation.

The no boot device found error looks alarming but follows a clear, structured path to resolution in most cases. Start with the simplest fixes — removing external devices and checking BIOS boot order — before moving to boot file repair and hardware inspection. If diagnostics flag a failing drive, stop troubleshooting independently at that point. Further power cycles put your data at risk, and professional recovery becomes significantly harder once a drive is fully unresponsive.

Disclaimer

The information in this article is provided for general educational purposes only and may not apply to your specific device or situation. Technology issues can involve risks, including potential data loss. If you are unsure about any step, consider getting professional assistance. PC Laptops is not responsible for outcomes resulting from actions taken based on this content.