How to Fix the No Bootable Device Error

The no bootable device error most often appears because the BIOS boot order points to the wrong drive or the boot drive has lost its connection. The message, shown as No Bootable Device, No Boot Device Found, or Operating System Not Found, means the firmware finished the power-on self-test but could not find a drive with a valid boot loader. The fault sits in the boot configuration or the storage connection rather than the operating system itself.

This article lists the causes of the error in order of probability, then walks through step-by-step solutions ordered from the fastest BIOS check to drive repair and replacement. The fixes cover setting the correct boot drive in BIOS, reseating the SATA or NVMe drive and its power, matching the UEFI or Legacy boot mode to the installation, rebuilding the boot record with bootrec, testing the drive in another system, and checking drive health. Each solution states what it resolves and gives the exact procedure.

What Causes the No Bootable Device Error?

The no bootable device error occurs because the firmware cannot find a drive with a valid boot loader, most commonly from a wrong boot order, a disconnected drive, or a corrupted boot record. The system completes the power-on self-test but has no bootable target. The common causes are listed below, most frequent first:

• Wrong boot order points the firmware at an empty drive, a USB stick, or a network adapter instead of the system drive.
• A disconnected or failed drive leaves the firmware with no storage to read, from a loose SATA cable or a dead SSD.
• A corrupted boot record in the MBR or the EFI system partition removes the loader the firmware hands off to.
• A changed boot mode between UEFI and Legacy CSM hides an installation made under the other mode.
• A failed SSD or hard drive stops responding, so the firmware reports no bootable device even with the cable connected.

The error proves the hardware initialized, since the system reached the firmware’s boot stage, which separates it from a dead system in the computer that will not turn on guide and from a no-signal fault in the PC with no display guide. How the firmware locates and hands off to the boot loader appears in the explanation of the boot process, which clarifies why a missing loader produces this exact message.

Set the Correct Boot Drive in BIOS

Setting the correct boot drive in BIOS resolves the error when the firmware points at the wrong device. A changed boot order, a newly added drive, or a connected USB stick can push the system drive down the list, so the firmware tries an empty target first. Follow these steps:

1. Enter BIOS or UEFI setup by pressing Delete, F2, or the key shown at startup before the operating system loads.
2. Open the Boot menu and read the boot priority list to confirm the system drive appears and sits first.
3. Set the system SSD or hard drive as the first boot device, moving it above any USB, optical, or network entry.
4. Save and exit with F10, then confirm the system boots into the operating system on restart.

If the system drive is absent from the boot list entirely, the firmware does not detect the drive, which points to a connection or drive failure rather than a boot-order setting. A drive that appears but still fails to boot points to a corrupted boot record.

Reseat the SATA or NVMe Drive and Power

Reseating the drive and its power connection resolves the error when the firmware cannot detect the boot drive. A loose SATA data cable, a disconnected SATA power lead, or an NVMe drive unseated in its M.2 slot removes the drive from detection. Follow these steps:

1. Power off and unplug the system, then reseat both ends of the SATA data cable between the drive and the motherboard.
2. Reconnect the SATA power lead from the power supply to the drive, since a drive without power does not appear in BIOS.
3. Reseat an NVMe drive in its M.2 slot, securing the retention screw so the drive sits flat in the connector.
4. Try a different SATA port and cable on the motherboard to rule out a failed port or a damaged cable.

After reseating, re-enter BIOS to confirm the drive now appears in the storage list. A drive that reappears after reseating had a loose connection, while one that stays absent across ports and cables points to a failed drive that needs testing in another system.

Match the UEFI or Legacy Boot Mode to the Installation

Matching the boot mode to the installation resolves the error when the firmware boots in a mode different from the one the operating system was installed under. A Windows installation made in UEFI mode does not boot when the firmware switches to Legacy CSM, and the reverse also fails, because each mode reads a different boot structure. Follow these steps:

1. Enter BIOS and open the Boot or CSM settings, then read whether the system is set to UEFI, Legacy, or CSM mode.
2. Recall how the operating system was installed, since modern Windows installations on a GPT disk use UEFI mode.
3. Set the firmware to the matching mode, choosing UEFI for a GPT installation or Legacy CSM for an MBR installation.
4. Disable Secure Boot temporarily if a UEFI installation still fails to boot after the mode is corrected.

A BIOS update or a CMOS clear can reset the boot mode and trigger this error on a system that booted fine before, so a recent firmware change is a strong clue. The handoff from firmware to loader differs between the two modes, a distinction the boot process explanation details for UEFI and Legacy systems.

Rebuild the Boot Record With Bootrec

Rebuilding the boot record with bootrec resolves the error when the boot loader or the boot configuration data is corrupted. A failed update, a power loss during write, or a damaged EFI partition can remove the loader the firmware needs.

The Windows Recovery Environment provides the bootrec tool to rebuild it. Follow these steps:

1. Boot from a Windows installation USB and select Repair your computer, then Troubleshoot, then Command Prompt.
2. Run bootrec /fixmbr to write a compatible master boot record to the system drive.
3. Run bootrec /fixboot to write a new boot sector to the system partition.
4. Run bootrec /scanos and then bootrec /rebuildbcd to detect Windows installations and rebuild the boot configuration data store.

On a UEFI system where bootrec /fixboot returns access denied, the EFI partition needs repair with bcdboot, recreating the boot files from the Windows folder. The Microsoft support documentation describes the bootrec and bcdboot commands for both Legacy and UEFI installations. A system that boots after a bootrec repair had a corrupted boot record rather than a hardware fault, while one that still fails points to a deeper storage or boot-loop problem.

Test the Drive in Another Computer

Testing the drive in another computer isolates the error to a failed drive rather than the motherboard or its ports. Connecting the suspect drive to a known-good system determines whether the drive is detected and readable. Follow these steps:

1. Remove the drive and connect it to a working computer through a SATA port or a USB-to-SATA or USB-to-NVMe adapter.
2. Check whether the second system detects the drive in its BIOS and in the operating system’s disk management.
3. Copy any important files off the drive immediately if it is detected, since a failing drive can stop responding without warning.
4. Judge the result: a drive invisible on a second system has failed, while a detectable drive points to the original motherboard or cabling.

A drive that the second system detects and reads has working hardware, which moves the fault back to the original system’s ports, cables, or boot configuration. A drive that no system detects has failed and needs replacement, with data recovery attempted from a backup.

Check Drive Health With SMART Data

Checking drive health with SMART data confirms whether the boot drive is failing and causing the intermittent error. Self-Monitoring, Analysis, and Reporting Technology records reallocated sectors, read errors, and wear that predict a drive failure.

Reading the SMART values reveals a drive on the edge of failure. Follow these steps:

1. Connect the drive to a working system or boot a live environment that can read the drive without the corrupted operating system.
2. Open a SMART tool such as CrystalDiskInfo, which reports the overall health status as Good, Caution, or Bad.
3. Read the reallocated sector count and pending sector count, since rising values indicate physical degradation on the drive.
4. Replace the drive if the tool reports Caution or Bad, then restore the operating system and data from a backup.

A drive reporting Caution or Bad in SMART is failing and produces an intermittent no bootable device error that worsens over time. A drive reporting Good but still not booting points to a software boot fault that the bootrec rebuild addresses, while a drive that also slows the system ties to the guide to fixing a slow computer.

Key Takeaways

• Set the system drive first in the BIOS boot order, since a wrong boot order is the most common cause of the error.
• Reseat the SATA or NVMe drive and its power when the drive is missing from the BIOS storage list.
• Match the UEFI or Legacy boot mode to the mode the operating system was installed under, especially after a BIOS update.
• Rebuild the boot record with bootrec from the Windows Recovery Environment when the loader is corrupted.
• Test the drive in another computer to separate a failed drive from a motherboard or cabling fault.
• Check SMART data to confirm a failing drive, replacing it and restoring from a backup when health reads Caution or Bad.

Last Thoughts on the No Bootable Device Error

The no bootable device error means the firmware found no drive with a valid boot loader, so the fix moves from the boot configuration to the storage hardware: set the correct boot drive in BIOS, reseat the SATA or NVMe connection, match the UEFI or Legacy boot mode, rebuild the boot record with bootrec, test the drive in another system, and check SMART health. The symptom table separates a missing drive from a corrupted boot record. Readers can continue with the fix for a PC stuck on the boot screen, the fix for Windows stuck on the loading screen, or the hub of common PC problems for related boot faults.