How Do I Fix No Bootable Device Found in Windows?

Issue type: Boot failure — “No bootable device found” / “Boot device not found” / “Operating system not found”

SEO focus: If you are looking for fix no bootable device found windows, this guide starts with the fastest diagnosis, then moves to the exact fix that matches the symptom.

Short answer: This error means the BIOS can’t find a drive with valid boot files. Check the BIOS boot order first — your Windows drive must be first in the list. If the boot order is correct, boot from a Windows USB and run Startup Repair. If that fails, use bootrec commands to manually rebuild the boot configuration.

Fix No Bootable Device Found Windows: Quick Diagnosis

There are three possible situations when this error appears, and the fix depends on which one applies to you:
1 — Drive detected in BIOS but Windows won’t boot: The drive is healthy but the boot files (BCD) are corrupted or missing. This is fixable with Startup Repair or bootrec commands.
2 — Drive not detected in BIOS at all: The BIOS doesn’t see the drive under its storage device list. This is a hardware-level issue — loose cable, failed drive, or disabled SATA/NVMe port.
3 — Drive detected but wrong Secure Boot / CSM setting: The drive is present but BIOS mode doesn’t match how Windows was installed (UEFI vs Legacy).
To determine which applies, enter your BIOS setup (F2, F12, Del, or Esc at startup — the key varies by manufacturer) and check the storage device list. If your drive appears there, you’re dealing with situation 1 or 3. If it doesn’t appear at all, start with hardware checks.

What to do first

1. Enter BIOS and verify the boot order. The drive containing Windows must be listed first under Boot Priority. If a USB drive, optical drive, or network boot option is ahead of it, move the Windows drive to position 1. Save and exit (usually F10).
2. If the drive is missing from BIOS entirely, check physical connections. On a desktop: open the case and reseat the SATA or NVMe cable. On a laptop with a removable drive bay: reseat the drive. Try rebooting and entering BIOS again to see if it now appears.
3. Boot from a Windows installation USB or DVD. At the setup screen, click “Repair your computer” > Troubleshoot > Advanced options > Startup Repair. This automated tool detects and repairs corrupted BCD entries without you writing commands.
4. If Startup Repair doesn’t fix it, go back to Advanced options > Command Prompt and run these commands in order:
   bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
   When rebuildbcd asks “Add installation to boot list? Yes/No/All,” type A and press Enter.
5. If bootrec /fixboot returns “Access is denied,” run these two commands first, then retry:
   diskpart
list disk
select disk 0
list partition
   Find the EFI partition (100–500 MB, type System). Select it and assign a drive letter:
   select partition X (replace X with the partition number)
   assign letter=Z
exit
   Then run: bcdboot C:Windows /s Z: /f UEFI
6. Check Secure Boot and CSM settings. If Windows was installed in UEFI mode (GPT partition table), Secure Boot should be enabled and CSM should be disabled — or at minimum not set to Legacy Only. If Windows was installed in Legacy mode (MBR partition table), CSM must be enabled. Switching these without knowing how Windows was installed will prevent it from booting.

Common mistake

Switching between UEFI and Legacy mode in BIOS without understanding how Windows was originally installed. If Windows was installed in UEFI mode on a GPT disk and you enable Legacy/CSM mode, Windows won’t boot. The BIOS mode must match the partition table type: UEFI goes with GPT, Legacy goes with MBR. Don’t toggle these settings based on guesswork.

Best next step

If bootrec commands return “Element not found” or “The requested system device cannot be found,” the BCD store doesn’t exist at all. Recreate it from scratch using:
bcdboot C:Windows /s C: /f UEFI
(Use /f BIOS if your system uses Legacy mode instead of UEFI.)
If bcdboot also fails, the partition containing boot files may be corrupted. Boot into a live Linux environment (Ubuntu on USB), back up your personal files, then perform a clean Windows installation. Do not attempt further repairs on a partition that bcdboot cannot write to.

⚠️ Warning: Do not run bootrec commands on a drive protected by BitLocker encryption without first suspending BitLocker from within Windows (before the problem occurred). Running fixmbr or fixboot on a BitLocker-encrypted drive without proper handling can permanently lock you out of the encrypted volume.

Official reference: For official Windows troubleshooting guidance, check Microsoft’s Windows support page before downloading third-party repair tools or changing advanced settings.

Quick Q&A

My drive shows up in BIOS but Windows still won’t boot. What does that tell me?

The drive is physically fine and BIOS can read it — but the boot files on it are corrupted or missing. Boot from a Windows USB and run Startup Repair first. If that doesn’t fix it, use the bootrec commands in Recovery Command Prompt. The drive itself is not the problem.

This happened after I added a second internal drive. Could that cause it?

Yes. Adding a second drive can shift the boot order in BIOS. Go into BIOS setup and confirm your original Windows drive is still listed first in the boot priority sequence. Also check that the new drive’s partition wasn’t accidentally set as the active boot partition in Disk Management.

Can “No bootable device found” mean the SSD is dying?

Yes, if the drive doesn’t appear in BIOS at all, or appears intermittently across restarts. Boot from a Linux USB (Ubuntu), run sudo smartctl -a /dev/sda (or /dev/nvme0 for NVMe) to read S.M.A.R.T. data. If the drive shows reallocated sectors, pending sectors, or uncorrectable errors, it’s failing. Back up everything immediately before attempting any repairs.