Fix "No Bootable Device Found" on Windows 10/11 (Acer/Dell/Toshiba)

The fast answer. "No bootable device found" (Acer), "No Boot Device Found" (Dell), and "No bootable device — insert boot disk and press any key" (Toshiba) all mean the same thing: the firmware scanned its boot list and found no partition it recognizes as bootable. The fix depends on which of the three causes you're hitting. Start by unplugging every USB drive and external disk and rebooting — a non-bootable flash drive left in the port is the single most common trigger. If unplugging doesn't help, enter BIOS/UEFI setup (usually F2 or Del at power-on; F12 opens the one-time boot menu on most Acer, Dell, and Toshiba machines) and confirm the internal drive is detected and first in the boot order. If the drive is there but the error persists, the boot records are damaged — boot a Windows 10/11 install USB, open Repair your computer → Troubleshoot → Command Prompt, and run:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

Then reboot. On UEFI/GPT systems bootrec /fixboot may return "Access is denied" — that's expected; use bcdboot instead (Step 5 below).

Why this happens

Non-bootable USB or external drive in a port — the firmware boots devices in order and stops at the first one it tries. A flash drive left plugged in is queried first, fails, and the machine gives up without checking the internal disk. This is the most common cause.
Wrong boot order — the internal Windows drive has fallen below a network boot (PXE), optical drive, or external device in the firmware's priority list. A CMOS battery failure will reset the boot order to factory defaults, which may not have the hard drive first.
UEFI/Legacy (CSM) mode mismatch — Windows 10/11 on a GPT disk requires UEFI mode; an MBR disk requires Legacy/CSM. A BIOS update, CMOS reset, or board swap can flip the mode, making a perfectly healthy Windows installation invisible to the firmware.
Drive not detected by firmware — a loose SATA data or power cable, an unseated M.2 module, a disabled controller port, or a physically failing drive. If the BIOS storage list doesn't show the drive at all, no software command can fix it.
Damaged MBR, boot sector, or BCD — an unclean shutdown, a failed Windows update, malware, or a bad drive clone corrupted the structures the firmware reads to hand off to the Windows boot loader.
System partition not marked active (MBR/legacy only) — on MBR disks the partition holding the boot files must carry the active flag. A partition tool or clone operation can clear it silently.

Step-by-step fix

Step 1 — Unplug external media and correct the boot order

Remove every USB drive, external disk, SD card, and CD/DVD. Reboot. If Windows starts, the firmware was trying to boot an external device. Enter BIOS/UEFI setup (hold F2 or tap Del at power-on — Acer and Dell commonly use F2, Toshiba uses F2 or F12) and move the internal Windows drive to position one in the boot priority list. Save with F10 and exit.

Step 2 — Confirm the drive is detected in BIOS/UEFI

While in BIOS/UEFI setup, open the storage or boot-device list. If the internal drive is missing, power off, unplug from the wall, and reseat the SATA data cable and power connector (or press the M.2 module firmly into its slot and retighten the screw). Check that the controller port isn't disabled in the SATA configuration section. If the drive still doesn't appear after reseating, the hardware has failed — run the drive maker's diagnostics from a bootable tool if possible, and plan on recovering data before replacing the drive. None of the commands in the steps below can repair a drive the firmware cannot see.

Step 3 — Match the BIOS mode to the disk's partition style

Boot a Windows 10/11 install USB and press Shift+F10 at the first setup screen to open a Command Prompt. Check whether the disk is GPT or MBR:

diskpart
list disk
exit

An asterisk (*) in the Gpt column means the disk is GPT — the firmware must boot in UEFI mode (CSM/Legacy off). No asterisk means MBR, which needs Legacy/CSM mode. If the firmware setting doesn't match, change it in BIOS setup, save, and reboot — this alone often clears the error after a CMOS reset or board swap. Do not try to rebuild boot records until the mode matches the disk.

Step 4 — Run Startup Repair

From the install USB choose Repair your computer → Troubleshoot → Startup Repair. It detects and rebuilds missing or damaged boot files automatically. Let it finish and reboot. If it reports it could not repair the PC, continue to Step 5.

Step 5 — Repair the boot records manually

Open Troubleshoot → Command Prompt and run these in order:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

When bootrec /rebuildbcd finds a Windows installation, type Y to add it. Reboot and test.

UEFI/GPT systems: bootrec /fixboot will return "Access is denied" — that's normal and not the actual fix. Rebuild the EFI boot files with bcdboot instead. First, use diskpart to assign a drive letter to the EFI System Partition (a small FAT32 volume, typically around 100 MB). Confirm all volume letters in WinRE before proceeding — the Windows drive is often not C: inside the recovery environment:

diskpart
list vol
sel vol <EFI-FAT32-vol#>
assign letter=S:
exit
bcdboot C:\Windows /s S: /f UEFI

You should see "Boot files successfully created." Reboot and test.

Step 6 — Mark the system partition active (MBR/legacy disks only)

On MBR disks, the partition holding the boot files must carry the active flag. In Command Prompt:

diskpart
list disk
sel disk 0
list partition
sel partition 1
active
exit

Replace sel partition 1 with the actual System Reserved or boot partition — typically a small (100–500 MB) NTFS partition. Confirm the number before typing active; setting the wrong partition active moves the problem instead of solving it. This flag has no meaning on GPT/UEFI systems — skip this step if the disk is GPT.

Step 7 — Check the disk for file-system damage

If the error persists or comes back after a reboot, repair the file system and scan for bad sectors (replace C: with the Windows drive letter shown in the recovery environment):

chkdsk C: /f /r

A growing count of bad sectors — or a drive that intermittently disappears from the BIOS — means the drive is physically failing. Back up immediately and replace it. No software repair holds on dying hardware.

Data safety: A drive that intermittently drops out of the BIOS or shows this error after a recent shock or age may be failing — image it to a known-good external disk before running any repairs. bootrec, bcdboot, and the active flag only write boot metadata and don't touch data. But chkdsk /r does stress weak sectors, and a drive that's already marginal can drop data under that load. Never run format, clean, or a fresh Windows install to "get past" this error — those destroy data. Never run repairs on the only copy of irreplaceable files.

GRAM tip: Once the machine boots again, plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to check the drive's SMART health (critical when an intermittently detected drive is involved), read the event log for prior hardware errors, and let its AI agent confirm whether the root cause was boot order, a mode mismatch, or a failing disk so the error doesn't come back.

Download GRAM free See AI pricing →

FAQ

Can I fix this without a second working computer?

Often yes. The most common causes — a USB drive left in the port, a wrong boot order, a loose cable, or a flipped UEFI/Legacy setting — are fixed entirely in BIOS/UEFI setup without any media. One important difference from blue-screen errors: "No bootable device" fires before Windows begins loading, so forcing three failed boots cannot trigger Automatic Repair. If the boot records themselves are damaged, you need a Windows 10/11 install USB to reach Startup Repair and Command Prompt. Any existing install USB works; creating a new one does require a second working PC. (GRAM runs inside Windows, not from boot media — use it once the machine boots to verify disk health and confirm the root cause.)

Does "No bootable device" mean my hard drive has failed?

Not necessarily. First check whether the BIOS/UEFI storage list shows the drive. If it's listed, the drive itself is almost certainly fine and the problem is boot order, a BIOS-mode mismatch, or damaged boot records — all correctable. If the drive is missing from the BIOS even after reseating its cables, then it's a hardware problem: the drive, cable, connector, or controller port has failed. Data recovery comes before any repair in that case.

Will bootrec or marking a partition active erase my files?

No. bootrec and bcdboot write only boot-sector and BCD metadata — they don't touch your data partitions. The active flag is a single bit in the partition table. The real risks are accidentally selecting the wrong disk or partition in diskpart, or running chkdsk /r on a drive that's already physically failing. If the data is irreplaceable, image the drive to an external disk before starting repairs.

Why did this appear after a BIOS update or CMOS reset?

A CMOS reset or BIOS update restores factory defaults: boot order resets (and your Windows drive may no longer be first), and the boot mode can flip between UEFI and Legacy/CSM. A GPT disk is invisible to Legacy boot; an MBR disk is invisible to pure UEFI boot — so a healthy Windows installation suddenly "disappears." Check the disk partition style with diskpart (Step 3 above), set the firmware mode to match, then correct the boot priority before doing anything else. A dead CMOS coin-cell battery causes the same reset on every power cycle; replacing it (CR2032 on most boards) stops the loop permanently.