Rightek Rescue · Guides · No bootable device found
“No bootable device found”? Here's how to fix it
This message does not come from Windows. It comes from your PC's firmware, before Windows gets a chance to load, and it means the firmware looked for something to boot and did not find it. That splits cleanly into two cases with completely different answers — and one check tells you which one you have.
What you're seeing
The exact wording depends on who made the machine, but they all mean the same thing:
- No bootable device found — common on Acer and Lenovo
- Boot device not found, often with hard disk 3F0 — HP
- No boot device available — Dell
- Reboot and select proper boot device — generic desktop firmware
- Operating system not found / Disk boot failure
The screen is usually plain text on black, appears within a second or two of powering on, and has no Windows styling at all. That absence is the clue: Windows never started, so this is not a Windows error.
Why it happens
Two categories, and they are not close to each other:
- The firmware can see the drive, but cannot find boot files on it. The disk is fine, your files are fine, and the boot configuration is damaged or missing. This is a software problem and it repairs.
- The firmware cannot see the drive at all. A loose or failed cable, a drive that has died, or an NVMe module that is no longer being detected. This is hardware, and no repair software can help until it is resolved.
A third, more cheerful possibility: the firmware is looking at the wrong device entirely, because a USB stick is plugged in or the boot order was changed.
Fix it yourself — the manual steps
1. The thirty-second check first
Unplug every USB stick, external drive, SD card and phone, then restart. Firmware often prefers removable media, and a stick left in a port produces this message on a completely healthy PC. It costs nothing to rule out and it is the cause more often than people expect.
2. Ask the firmware whether it can see the disk
This is the check that decides everything else. Restart and press the setup key repeatedly as it powers on — Del or F2 on most desktops, F2 on Dell and Acer, F10 on HP, F1 or Enter then F1 on Lenovo. Look for a page called Main, Boot, or Storage, and see whether your drive is listed.
- The drive is listed. Good — the hardware is alive and this is a software problem. Go to step 3.
- The drive is not listed, or appears and disappears between restarts. Stop here and go to step 5.
3. Fix the boot order
While you are in the firmware, check that the Windows drive is first in the boot order and, on a UEFI machine, that there is an entry called Windows Boot Manager. If that entry has vanished, the boot files are gone rather than the drive — step 4 rebuilds them. Save and exit, and try booting once more.
4. Rebuild the boot files
You will need Windows installation media on a USB stick, made from another working PC using Microsoft's Media Creation Tool. Boot the broken machine from it (the boot menu is usually F12, F11 or Esc at power-on), then choose Repair your computer → Troubleshoot → Advanced options.
Try Startup Repair first — it is automatic, safe, and fixes the common case. If it fails, open Command Prompt and run these in order:
bootrec /fixmbr— writes a clean master boot recordbootrec /fixboot— writes a new boot sector to the system partitionbootrec /scanos— looks for Windows installations the boot menu has lostbootrec /rebuildbcd— rebuilds the boot configuration from what it found
If /fixboot returns Access is denied on a UEFI machine, that is normal and
not a failure — the EFI partition needs assigning a letter first, which is fiddly enough that
it is the point where most people reasonably stop doing this by hand.
5. If the firmware cannot see the drive
No amount of software fixes a disk the machine cannot detect. In order of cost:
- Desktop: power off at the wall, open the case, and reseat both the data and power cables at the drive and at the motherboard. Cables work loose, and this is a genuinely common fix.
- Laptop: far less likely to be a cable, far more likely to be the drive.
- Either: if the drive was making clicking or grinding noises before this started, do not keep power-cycling it hoping it appears. Each attempt is risk. That is a data recovery job — talk to us before doing anything else.
⚡ The one-click way: let Rightek Rescue do it
Rescue boots from its own USB, so it can see the disk even when Windows cannot start. It checks whether the drive is detected and looks healthy, then rebuilds the boot configuration and the EFI boot files in the right order — the UEFI case that stops most manual attempts — and, with your consent, restores a destroyed partition table or NTFS boot sector from the disk’s own backup copy. On any working PC: download Rescue, put it on a USB (one click makes it bootable), boot the affected PC from it, and choose Fix My PC. The diagnosis is free and it tells you what it found before it changes anything.
FAQ
Does this mean my hard drive is dead?
Not necessarily, and the BIOS tells you. If your drive is listed in the firmware setup screens, the hardware is alive and only the boot files are damaged — that repairs and your files are untouched. If the drive is not listed at all, then it is a cable or the drive itself.
Will I lose my files fixing this?
No. Everything in this guide writes to the boot record and boot configuration, which are tiny structures separate from your data. Nothing here formats, repartitions or overwrites the part of the disk your files live on.
What is error 3F0?
It is HP's code for the same condition — the firmware could not find a bootable device. It carries no extra diagnostic meaning beyond the message itself, and the same checks apply.
bootrec /fixboot says access is denied. What now?
That is normal on UEFI systems rather than a sign of a worse problem. The EFI system partition has no drive letter, so the command cannot reach it. Assigning one by hand through diskpart is possible but fiddly, and it is the point at which doing this manually stops being worth it for most people.
Why did this happen out of nowhere?
The most common triggers are an unexpected power loss during an update, cloning to a new drive without moving the boot files, a firmware change such as switching between UEFI and Legacy or AHCI and RAID, and disk repair tools that rewrote the partition table.