The no bootable device error means the firmware finished the power-on self-test but could not find a drive with a valid boot loader, so the first fix is to confirm the drive shows in the BIOS and that the boot order points to it. The message appears as No Bootable Device, No Boot Device Found, or Operating System Not Found, and it points at the boot configuration or the storage connection rather than the operating system. If the system drive is missing from the BIOS entirely, the problem is detection, a loose cable, a reset boot mode, or a failed drive. If the drive is listed but still will not boot, the boot record is most likely corrupted and rebuilt with bootrec.
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 often from a wrong boot order, a drive that is not detected, a corrupted boot record, or a mismatched boot mode. The system completes the power-on self-test, which proves the hardware initialized, but it has no bootable target to hand off to. The four causes below are ordered by how often they produce this exact message.
The error proves the hardware reached the firmware’s boot stage, which separates it from a dead system that will not power on and from a no-signal display fault. Use the symptom table to point at the most likely cause before you start.
| Symptom | Most Likely Cause |
|---|---|
| Drive missing from the BIOS boot list | Disconnected or failed drive |
| Drive present but not booting | Wrong boot order or corrupted boot record |
| Worked until a BIOS update or reset | Boot mode switched between UEFI and Legacy |
| Error after a power loss | Corrupted MBR or EFI partition |
| Clicking sound from a hard drive | Mechanical drive failure |
How Do You Fix the No Bootable Device Error?
Work from the fastest BIOS check to drive repair and replacement, stopping at the step that restores the boot. Each step states what it resolves and how to judge the result, so you move from boot configuration to storage hardware in order of probability.
- Check the drive shows in the BIOS. Enter setup with Delete, F2, or the key shown at startup and open the storage or boot list. A drive that is missing means a detection fault; a drive that is present means a boot-order or boot-record fault. This one check decides the whole path.
- Set the correct boot drive. In the Boot menu, move the system SSD or hard drive to the first position above any USB, optical, or network entry, then save with F10. A wrong boot order is the most common cause, so this is the fastest fix when the drive is detected.
- Reseat the SATA or M.2 connection. Power off and unplug, then reseat both ends of the SATA data cable and the power lead, or reseat an NVMe drive in its M.2 slot and tighten the screw. Try a different port and cable. A drive that reappears had a loose connection.
- Match UEFI versus Legacy and Secure Boot. Open the Boot or CSM settings and set the firmware to the mode the system was installed under, UEFI for a GPT disk or Legacy CSM for an MBR disk. Disable Secure Boot temporarily if a UEFI installation still fails after the mode is corrected.
- Rebuild the BCD with bootrec. Boot from a Windows installation USB, choose Repair your computer, Troubleshoot, then Command Prompt, and run bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, and bootrec /rebuildbcd. On a UEFI system where /fixboot returns access denied, repair the EFI partition with bcdboot instead.
- Test the drive and check its health. Connect the drive to a working computer through a SATA port or a USB adapter, confirm it is detected, copy off important files, and read its SMART data with CrystalDiskInfo. A status of Caution or Bad means the drive is failing and needs replacement.
After each hardware step, re-enter the BIOS to confirm whether the drive now appears in the storage list. A drive that the BIOS lists has working detection, which moves the fault to the boot order or the boot record. The handoff from firmware to loader differs between UEFI and Legacy, which is why a flipped boot mode hides an otherwise healthy installation.
When Is the Boot Record Corrupted Rather Than the Drive?
The boot record is the suspect when the drive is detected and listed in the BIOS but the system still will not boot. A failed Windows update, a power loss during a write, or a damaged EFI system partition removes the loader without touching the rest of the drive. The bootrec sequence in the Windows Recovery Environment rebuilds it:
- bootrec /fixmbr writes a compatible master boot record to the system drive on a Legacy MBR setup.
- bootrec /fixboot writes a new boot sector to the system partition.
- bootrec /scanos scans every disk for Windows installations the boot menu is missing.
- bootrec /rebuildbcd rebuilds the boot configuration data store and adds the installations it found.
- bcdboot C:\Windows /s S: /f UEFI recreates the boot files on the EFI partition when /fixboot returns access denied on a UEFI and GPT system.
A system that boots after a bootrec or bcdboot repair had a corrupted boot record rather than a hardware fault. One that still fails after the boot record is rebuilt, with the drive confirmed healthy, points to a deeper boot loop. A drive that is detected but slow may be on its way out, which ties to the guide on a SSD not showing up and the wider hub of common PC problems.
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 in order from the boot configuration to the storage hardware. Confirm the drive shows in the BIOS, set the correct boot drive, reseat the SATA or M.2 connection, match UEFI versus Legacy and Secure Boot, rebuild the BCD with bootrec, and test the drive’s health with SMART. The single most useful split is whether the drive appears in the BIOS at all: a listed drive points to boot order or a corrupted boot record, while a missing drive points to a connection fault or a failed drive.
This error sits alongside the other ways a PC stalls before the desktop loads, such as a machine stuck on the boot screen. For the full set of related boot and startup faults, the hub of common PC problems connects each symptom to its fix.
Key Takeaways:
- The error means the firmware passed POST but found no drive with a valid boot loader, so the fault is boot configuration or storage, not the operating system.
- Whether the drive appears in the BIOS is the key split: listed means boot order or boot record, missing means a connection fault or a failed drive.
- A wrong boot order is the most common cause, and setting the system drive first in the BIOS is the fastest fix.
- Reseat the SATA or M.2 connection and try another port and cable when the drive is missing from the BIOS storage list.
- Match UEFI versus Legacy to how the system was installed, especially after a BIOS update or a CMOS clear, and disable Secure Boot temporarily to test.
- Rebuild the boot record with bootrec, or with bcdboot when /fixboot returns access denied on a UEFI system, then check SMART data to confirm a failing drive.
Frequently Asked Questions (FAQs)
What does the no bootable device error mean?
It means the firmware finished the power-on self-test but found no drive with a valid boot loader. The fault is in the boot order, the drive connection, or the boot record, not in the operating system files themselves.
How do I fix no bootable device in the BIOS?
Enter the BIOS, open the Boot menu, and set the system SSD or hard drive as the first boot device above any USB, optical, or network entry. Save with F10 and restart. If the drive is not listed at all, the problem is detection, not boot order.
Why is my drive not showing in the BIOS at all?
A drive missing from the BIOS usually has a loose SATA cable, a disconnected power lead, or an unseated M.2 module, or it has failed. Reseat the connections and try another port and cable. A drive that never appears across ports has most likely failed.
How do I rebuild the boot record for the no bootable device error?
Boot from a Windows installation USB, open Command Prompt under Repair your computer, and run bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, and bootrec /rebuildbcd. On a UEFI system where /fixboot returns access denied, repair the EFI partition with bcdboot instead.
Can UEFI versus Legacy mode cause the no bootable device error?
Yes. An operating system installed in UEFI mode does not boot under Legacy CSM, and the reverse also fails, because each mode reads a different boot structure. A BIOS update or a CMOS clear can flip the mode and trigger the error. Set the firmware to match how the system was installed.
How do I know if my SSD or hard drive has failed?
Connect the drive to a working computer and read its SMART data with a tool such as CrystalDiskInfo. A status of Caution or Bad, or a rising reallocated sector count, indicates a failing drive that needs replacement. A clicking sound from a mechanical drive is a sign of physical failure.
