Error Messages

Reboot and Select Proper Boot Device: How to Fix It Safely

Updated October 2, 2026 •6 min read

You press the power button and instead of Windows you get a black screen: “Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key.” Pressing a key just brings the message back. The “reboot and select proper boot device” error looks serious, but it’s the firmware (BIOS/UEFI) saying something simple: I looked for a drive I can start from and didn’t find one. In many cases, your files are still on the drive, untouched.

The trick is figuring out why the firmware couldn’t find a bootable drive, and fixing that without doing anything that overwrites your data.

What “reboot and select proper boot device” actually means

Before Windows loads, the motherboard firmware walks through its boot order, a list of devices like the internal SSD, a USB stick, or the network. On each one it looks for valid boot code. If nothing on the list has it, you get this message. (It’s most familiar on desktops and custom-built PCs, but laptops show the same problem with different wording; see Boot Device Not Found / No Bootable Device.)

That means the error tells you where the process stopped, not what broke. The cause could be a setting, a cable, damaged boot files, or the drive itself.

Common causes

Wrong boot order. A USB drive, external disk, or DVD sits ahead of the Windows drive, or the Windows drive dropped off the list entirely.
A removed or unplugged drive. A loose SATA or power cable on a desktop, an M.2 drive that isn’t fully seated, or a drive taken out during an upgrade.
Legacy vs. UEFI mismatch. Windows on a GPT disk boots in UEFI mode; older installs on an MBR disk need Legacy/CSM mode. If a BIOS update, a CMOS reset, or a dead CMOS battery flips that setting, the firmware no longer recognizes the drive as bootable.
Corrupted boot records. A power loss, failed update, or partitioning mistake can damage the EFI system partition, boot sector, or Boot Configuration Data. That’s the same family of problems as BOOTMGR is missing.
A failing drive that can no longer be read reliably, or that has stopped responding entirely.

Fixes, in order from safest to strongest

1. Unplug external media

Remove USB flash drives, external hard drives, SD cards, and discs, then restart. If the PC was trying to boot from a USB stick with no operating system on it, this ends the problem.

2. Check that the drive is detected

Enter BIOS/UEFI setup right after power-on. The key is usually F2, Del, F10, or Esc, depending on the manufacturer. Look at the storage or boot section and confirm your Windows drive is listed by name or model.

Listed: good. The hardware is responding. Continue to step 3.
Not listed: on a desktop, power off, unplug the PC, and reseat the drive’s data and power cables (or the M.2 drive). If it’s still missing after that, jump to “When it’s the drive, not the settings” below.

3. Fix the boot order

In the boot section, move your Windows drive to the top. On UEFI systems the entry is usually labeled Windows Boot Manager rather than the drive’s model name. You can also test with the one-time boot menu (often F12, F11, or Esc) and pick the drive manually. Save and exit, usually with F10.

4. Check Legacy vs. UEFI mode

If the drive is listed but won’t boot, look for a Boot Mode, CSM, or Legacy Support option. A Windows 10 or 11 install on a modern PC almost always expects UEFI with CSM disabled. If you recently updated the BIOS or replaced the CMOS battery, the setting may have reset. Switch it back, save, and try again. Changing this setting doesn’t write anything to your drive.

5. Run Startup Repair

Boot from a Windows installation USB (made on another PC with Microsoft’s Media Creation Tool), choose your language, then Repair your computer → Troubleshoot → Advanced options → Startup Repair. It tries to rebuild damaged boot files automatically.

6. Rebuild the boot files manually

From Troubleshoot → Advanced options → Command Prompt, these commands rewrite boot information only. They don’t touch your documents:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

On UEFI systems, bootrec /fixboot sometimes returns “Access is denied.” In that case, bcdboot C:\Windows recreates the boot files instead. In the recovery environment, Windows may not be on C:, so run dir C:\ and dir D:\ first to find the drive that contains the Windows folder.

Don’t reinstall Windows over your files

If none of that works, a clean install looks like the obvious next step. Don’t format, delete partitions, or choose “Custom: Install Windows only” on a drive holding files you haven’t backed up. That’s the move that actually destroys data, not the boot error.

Get your files off first:

Connect the drive to another computer with a USB-to-SATA or USB-to-NVMe adapter or enclosure, then copy everything you need.
If the drive is BitLocker-encrypted (common on Windows 11 laptops and many prebuilt desktops), you’ll need the recovery key to read it elsewhere. See how to find your BitLocker recovery key.
If Windows on the other PC says the disk needs to be formatted or initialized, say no. Initializing or formatting is what puts the data at risk.

Once your data is safe, reinstall however you like.

When it’s the drive, not the settings

Stop troubleshooting and power the computer down if:

The drive isn’t detected in BIOS even after reseating cables.
A hard drive clicks, beeps, grinds, or buzzes.
The drive shows up some boots and disappears on others.
The error appeared after a drop, spill, or power surge.

At that point the boot error is a symptom of hardware failure. Repeated restarts, repair tools, and recovery software all add wear to a failing drive and can lower the odds of getting everything back. SSDs usually fail silently, so a missing SSD deserves the same caution as a noisy hard drive.

The bottom line

“Reboot and select proper boot device” means the firmware couldn’t find something to boot from. Most of the time the cause is a boot-order setting, a loose cable, a Legacy/UEFI mismatch, or damaged boot files, and your data is fine. Work through the safe fixes in order, rescue your files before any reinstall, and stop if the drive isn’t detected or starts making noise. Close cousins of this error include INACCESSIBLE_BOOT_DEVICE and Operating System Not Found.

If the drive itself has failed, our desktop & PC data recovery service can help. ClearQuote recovers single drives for one flat $1,200 price with free prepaid shipping, and you pay nothing unless we recover your data.