"No Bootable Device" Error? Your Files Are Probably Still There

Direct answer: "No bootable device" means the firmware could not find a valid boot loader. That is often a boot-record or partition-table problem on a perfectly healthy drive, and your files are usually intact. Do not reinstall Windows and do not let a repair tool repartition the disk until you know which case you have.

The error goes by several names depending on the machine: "No bootable device", "Operating system not found", "Reboot and select proper boot device", or an Inaccessible Boot Device stop code. They all mean the same thing at the firmware level.

No-bootable-device diagnostic table

Step one: is the drive detected at all?

Enter the firmware setup (usually F2, F10, or Del at power-on) and look at the storage list. This tells you which branch you are on.

If the drive is listed with the correct model and capacity, the hardware is probably alive and the problem is logical. If it is absent, or shows a wrong capacity, you likely have a hardware fault and further boot attempts are working against you.

Step two: look without touching

The safest way to check your files is a live USB - a Linux distribution booted from a flash drive, which reads the disk without writing to it. If your documents are visible, this is a boot-record problem, not a data-loss event.

Copy the important files off to an external drive at this point, before attempting any repair. Repair tools that rebuild boot records occasionally rewrite partition structures, and doing that before you have a copy is how a recoverable situation becomes a recovery job.

What not to do

• Do not click "Reset this PC" or reinstall Windows. A reinstall writes a fresh file system over your data. This is the single most common cause of permanent loss after this error.
• Do not run automatic partition repair first. Rebuilding a partition table on a drive with an unrelated hardware fault can overwrite the very structures needed to find your files.
• Do not run CHKDSK on a drive that clicks or drops out. It writes to the disk and forces reads on failing hardware.
• Do not initialize the disk when Windows Disk Management offers to. That destroys the existing partition table.

When it is a hardware failure

If the drive is missing from firmware, reports the wrong size, clicks, or makes the machine hang for minutes at boot, treat it as hardware. Power it down and stop. From that point, a read-only image is the only safe next step, and that needs bench hardware rather than a live USB.

Our evaluation is a flat $50, same day. It tells you plainly whether you have a boot-record problem you could fix yourself in twenty minutes or a failing drive that needs imaging - and there is no recovery fee if no usable data is recovered.

Frequently asked questions

Does "No bootable device" mean my files are gone?

Usually not. The error only means the firmware could not find a boot loader. In most cases the files are intact and the boot record, partition table or drive connection is the problem.

Can I just reinstall Windows to fix it?

You can, but a reinstall writes a new file system over the old one and is the most common cause of permanent data loss after this error. Copy your files off first, or get an evaluation.

Is it safe to run CHKDSK?

Only on a drive that is fully detected, silent and reporting its correct capacity. CHKDSK writes to the disk, so on failing hardware it can make the case substantially worse.