No Boot Device Found? "Reboot and Select Proper Boot Device" — What It Means and How to Fix It

You press the power button, the machine whirs to life, maybe you see the maker's logo for a second — and then, instead of Windows, you get a black screen with a line of white text: "No boot device found," "Boot Device Not Found," "Reboot and Select proper Boot Device or Insert Boot Media in selected Boot Device and press a key," or "Operating System not found." HP laptops often add a code — "Hard Disk (3F0)"; Dell, Lenovo, ASUS and Acer each word it a little differently. It looks like the worst kind of failure, and it stops you cold before you can do anything.

Take a breath, because it's often far less serious than it looks. This message comes from your computer's firmware (the BIOS/UEFI) — the very first thing that runs when you turn the machine on, before Windows gets a chance to load. All it's saying is that the firmware went looking for a drive with a working copy of Windows on it and didn't find one where it expected. Sometimes that's because a USB stick is in the way, or a setting slipped; sometimes a cable worked loose; and sometimes the drive itself has failed. The good news is that even in the worst case, a drive that won't boot has very often not lost your files — so don't let anyone rush to wipe and reinstall before you've read to the end.

The trick to fixing this quickly is to stop guessing and answer one question first: is the drive even being detected by the firmware? That single check splits every version of this error into two very different problems with two very different fixes. This guide walks you through the free two-minute checks first, then how to make that detected-or-not call, and finally what each answer means.

First, the 30-second fix: unplug every USB drive and restart

Before anything else, do this — it's the single most common cause and it costs nothing. Unplug every USB flash drive, external hard drive, SD card, and even your phone from the computer, then restart. Here's why it works so often: your firmware tries each device in a set order until it finds one it can boot from. If a USB stick or memory card is sitting higher in that order than your internal drive, the firmware tries to boot from it, finds no Windows there, and throws exactly this error — even though your real drive is perfectly fine.

A huge share of "no boot device" panics are simply a flash drive left in a port overnight, or an external backup drive that was still plugged in. Pull everything out of every USB port, leave only the power cable and (on a desktop) the monitor and keyboard, and power on again. If Windows loads normally, that was it — you're done, and there's nothing wrong with your machine.

The one question that splits the problem: is the drive detected?

If unplugging everything didn't help, this is the check that tells you which of two problems you have. You want to get into the firmware setup or the one-time boot menu and see whether your internal drive is even listed. Restart and, as the maker's logo appears, tap the setup key — it varies by brand, commonly Del, F2, F10, or Esc, and the splash screen usually says which ("Press F2 for Setup," "Esc for Boot Menu"). On most Dell machines, tapping F12 brings up a boot menu and diagnostics; on many HP machines, Esc at power-on opens a menu of options.

Once you're in, look at the boot options or the list of detected storage/SATA/NVMe devices. The question is simple: does your internal drive (an SSD or hard drive, often shown by its model number) appear at all? The wording of the original error is a strong hint, too. "No boot device found" / "Boot Device Not Found" generally means the firmware isn't detecting a drive at all — a hardware or connection problem. "Operating system not found," by contrast, usually means the drive IS detected, but the copy of Windows (the boot files) on it is missing or damaged — a software problem. Same family of error, opposite causes. Which bucket you're in decides everything below.

If the drive IS listed: fix the boot order, then the boot files

Good news — if your drive shows up in the firmware, the hardware is almost certainly fine and this is a settings or software fix. Start with the boot order. In the firmware's Boot section, make sure your internal Windows drive is set as the first boot device. This setting can quietly get knocked out of place by a BIOS update, a firmware reset, or a dying CMOS coin-cell battery (the same little battery that, when flat, also makes your clock reset every restart). A quick, safe reset here is to load the firmware's defaults — often a key like F9 labelled "Load Setup Defaults" or "Load Optimized Defaults" — then save and exit (usually F10). That alone puts the boot order right on a lot of machines.

If the drive is detected but you get "Operating system not found," or it still won't boot after fixing the order, the boot files themselves are likely corrupted. The reliable fix is to boot from a Windows installation USB (made on another PC from Microsoft's free Media Creation Tool) and run Startup Repair, which repairs the bootloader automatically. If that doesn't take, the Command Prompt in the same recovery tools can rebuild the boot records by hand — the main command is bootrec /rebuildbcd, part of the set bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, bootrec /rebuildbcd. This is closely related to a machine that gets a little further and lands in a repair loop — if yours does that instead, our automatic-repair-loop guide below picks up exactly there.

If the drive is NOT listed: a loose connection or a failing drive

If your internal drive doesn't appear in the firmware at all, the firmware genuinely can't see it — which means either the connection came loose or the drive has failed. On a desktop, the usual culprit is a SATA data or power cable that worked itself loose over time (they're only friction-fit and vibration nudges them). Power off, unplug from the wall, open the side panel, and firmly reseat both the data cable and the power connector at the drive and at the motherboard; on many machines that one reseat brings the drive straight back. An M.2 SSD can likewise sit slightly proud in its slot. Laptops are less DIY-friendly — the drive may be behind a panel or, on many newer models, soldered down — so if reseating means major disassembly, that's a reasonable point to hand it to someone who opens laptops for a living.

To find out whether the drive is loose versus actually dead, use your computer's built-in hardware test — it runs from firmware and doesn't need Windows. On HP, tap Esc at power-on then F2 to open the System Diagnostics (choose Component Tests > Hard Drive, or the long DST/SMART test). On Dell, tap F12 and choose Diagnostics (SupportAssist / ePSA) to test the drive. Other makers have their own equivalent in the same boot menu. If the test passes but the drive isn't detected, suspect the cable or slot; if the test fails, or the drive is completely absent even after reseating, the drive has most likely died and needs replacing — after which Windows is reinstalled onto the new drive. That's a routine repair, not a lost cause.

Did this start right after cloning a drive or a BIOS change?

Timing is a giant clue. If the error appeared immediately after you cloned your old drive onto a new SSD, the drive is usually fine and the firmware just needs pointing at it correctly. Two things trip people up here. First, boot order: set the new SSD as the first boot device (and, if the old drive is still installed, either remove it or move it below the new one). Second, and less obvious, is a boot-mode mismatch — a modern Windows install expects UEFI mode with a GPT-style disk, and if the firmware is set to Legacy/CSM mode (or vice-versa relative to how the drive was set up), it can't find the bootloader and reports no boot device. Setting the firmware to the mode that matches the drive resolves it. Changing the SATA mode (AHCI vs RAID) after a clone can cause the same thing.

Likewise, if it began right after a BIOS/firmware update or you'd recently had the CMOS battery go flat, the update or the dead battery almost certainly reset your boot order and mode back to defaults. Going into the firmware, restoring your drive as the first boot device, and confirming the boot mode (UEFI for a typical modern PC) usually gets you straight back in. When a change like this is the trigger, it's a settings fix, not a hardware failure — no need to touch the drive at all.

Before you reformat or reinstall: your files are probably still there

This is the part worth slowing down for. A drive that won't boot has, in most cases, not lost your documents, photos, and email — the boot files can be damaged, or the drive can be failing, while the rest of your data sits there perfectly readable. So the one thing not to do in a panic is let anyone reformat the drive or do a "clean install" over the top of it before your files are safely copied off. A reinstall that wipes the drive is easy to trigger from the recovery menus, and it turns a recoverable situation into a permanent loss.

If the drive is detected but Windows won't start, your files can usually be pulled off by booting from a USB recovery tool or by connecting the drive to another computer. If the drive is failing — clicking, disappearing and reappearing, or failing the diagnostic — get the data copied off sooner rather than later, because a drive on its way out gets worse with every power cycle. Either way, once you're back up and running, this is the nudge to set up a backup so the next drive failure is a shrug instead of a crisis; our backups guide below covers the painless way to do it.

How we can help

A lot of "no boot device found" screens clear up with the free steps here — pull out the USB sticks, check the firmware, put the boot order right — and if that's all yours needed, brilliant, you've saved yourself a trip. We'd always rather tell you that than sell you anything, and there's no legitimate "boot repair" download to buy; the real fixes are a setting, a reseated cable, or, when it comes to it, a new drive.

When the drive genuinely won't show up, or the diagnostic says it's failing, that's where we come in. We help people across Southern California and the Coachella Valley work out fast whether it's a two-minute settings fix or a dead drive, reseat or replace the drive, recover the data off the old one before anything gets wiped, and get Windows reinstalled with your files and email back the way they were. Bring it in and we'll tell you honestly which it is before you spend a penny — and rescue your data first, whatever the drive is doing.