GuideHQ

What does "No bootable device" or "Operating system not found" mean?

Black screen, one line of text, no Windows. What the machine is actually telling you, the three-minute check that separates a settings problem from a dead drive, and what not to click.

Difficulty
intermediate
Time
40 min
Read
6 min
Safety
caution

Short answer

The machine has completed its own self-test and then found nothing it can start from. Go into the firmware setup screen — usually F2, F10, Del or Esc at the logo — and look at the list of storage devices. If your drive is listed there, this is a boot order or boot record problem and your data is almost certainly fine. If the drive is not listed at all, the firmware cannot see it, and that is hardware.

The wording varies by manufacturer — No bootable device, Operating system not found, No boot device available, Reboot and select proper boot device, an inserted-media prompt — and they all mean the same thing. The firmware has powered up, tested the hardware, gone looking for something to hand control to, and found nothing. That is genuinely useful information, because it tells you the power supply, the board and the memory are all working well enough to get that far. The whole diagnosis from here is one question: can the firmware see the drive?

Safety

This message can mean the drive is fine and merely unlisted, or that the drive has died with your only copy of everything on it. Until you know which, do not run anything that offers to repair, initialise, format or partition the disk. Initialising a disk that Windows cannot read is the single most common way people destroy recoverable data at this exact screen.
The boot chain: how far the machine got before it stopped

Step by step

  1. Unplug every USB device and try again.A USB stick, an external drive, a card reader with a card in it, even a phone left charging can be selected ahead of the internal drive and produce this exact message. It is free, it takes twenty seconds, and it is the single most common cause of a one-off appearance of this screen.
  2. Open the firmware setup screen and read the storage list.Power on and press the setup key repeatedly — F2 on many machines, F10 on HP, F1 or Enter on Lenovo, Del on most desktops, and there is usually a prompt for a second at the logo. Find the boot or storage page. Everything depends on whether your drive appears there.
  3. If the drive is listed, fix the boot order.Set the internal drive as the first boot device, save and exit. If Windows was installed in UEFI mode there will also be a Windows Boot Manager entry — that is the one to select, not the raw drive. A firmware battery that has died resets these settings on every power-off, which is worth suspecting on an older desktop that also shows the wrong date.
  4. If the drive is listed and the boot order is right, rebuild the boot record.The drive is healthy but the pointer to Windows has gone. This happens after a failed update, a cloning job, removing a second operating system, or a partition tool going wrong. You need Windows installation or recovery media to get to a command prompt, and the repair does not touch your documents.
  5. Check the security mode settings before assuming the worst.Secure Boot being switched on or off, or the storage mode changing between AHCI and RAID, will make a perfectly good Windows installation unbootable. If someone has been in the firmware recently, or it has been reset to defaults, put those settings back rather than reinstalling.
  6. If the drive is not listed, reseat it — on a desktop.Powered off and unplugged, check the data and power cables at both ends, and try a different data cable and a different port on the board. Cables and connectors fail more often than drives. On a laptop this is a strip-down and usually a job for a shop.
  7. Treat a drive the firmware cannot see as a data problem, not a repair problem.If the firmware genuinely cannot find it after reseating, the drive has failed electrically. Nothing you do from Windows will help. Whether the data is recoverable is now a question for a recovery service, and every further power-on reduces the odds on a mechanical drive.
  8. Confirm with a live USB before spending money.Booting the machine from a Windows installation USB and looking at whether the drive appears in the install screen's disk list is a second, independent opinion on the same question. If two separate environments cannot see it, it is gone.

Common mistakes

  • Accepting an offer to initialise or format the disk — Windows offers this whenever it meets a disk it cannot interpret, and it sounds like a repair. It writes a fresh empty structure over the one holding your files, and it turns a recoverable situation into an expensive one.
  • Reinstalling Windows to fix it — If the drive is visible and healthy, a boot record rebuild fixes it in minutes with nothing lost. If the drive is not visible, reinstalling is impossible anyway. There is no version of this fault where reinstalling first is the right move.
  • Assuming the machine is dead because the screen looks final — Getting as far as this message proves the power, board and memory all work. It is one of the more optimistic failure screens, and on many machines the fix is a setting.

If it doesn't work

Appeared once, then the machine started normally

Cause: A USB device was selected first, or the drive was slow to spin up — Fix: Unplug USB devices at shutdown and see whether it recurs. An intermittent version of this message on an older mechanical drive is a genuine early warning and a reason to check your backups.

Says "Reboot and select proper boot device" every time

Cause: Boot order, or a boot record that no longer points anywhere — Fix: Firmware setup, set the internal drive or Windows Boot Manager first. If it is already first, the boot record needs rebuilding from recovery media.

Started after cloning to a new SSD

Cause: The clone copied the data but not a working boot configuration, or both drives are still attached — Fix: Disconnect the old drive entirely and try again. If it still fails, the clone needs its boot partition repaired — a common outcome when cloning across a firmware mode change.

The firmware clock is also wrong

Cause: A flat CMOS battery on the motherboard — Fix: The firmware is losing all its settings at every power-off, boot order included. A coin cell costs very little and is a straightforward replacement on a desktop.

Drive shows in firmware but Windows install media sees it as unallocated

Cause: The partition table has been lost or overwritten — Fix: Do not accept the offer to initialise it. Partition recovery software read from another machine can often rebuild the table with the data intact. Initialising writes over exactly what recovery needs.

Machine was moved or knocked before this started

Cause: A dislodged cable or a damaged mechanical drive — Fix: Reseat cables first on a desktop. On a laptop that was dropped while running, expect physical drive damage and go straight to the data question.

Questions people ask

Is my data gone?

Not necessarily, and the firmware storage list tells you which world you are in within three minutes. A listed drive almost always still holds everything. An unlisted drive may still be recoverable by a specialist, because the fault is often the drive's own controller rather than the storage inside it — but that is a paid service, not a home job.

What is the difference between this and a blue screen?

A blue screen means Windows started, ran, and then hit something it could not handle. This message means Windows never started at all — the firmware never found it. They are different layers, and the catalogue's blue screen guide is the one to read if you get a stop code rather than this.

Why does it say "Insert boot media" when there is a drive right there?

Because the firmware can see the drive as hardware but cannot find anything bootable written on it. That is the boot record case, and it is repairable without losing files.

Can I just take the drive out and use it in another computer?

For getting your files back, yes — an external caddy or dock turns almost any internal drive into a USB drive, and it is the standard way to rescue documents. Booting another computer from it is a different matter and usually will not work because of driver and activation differences.

What to do next

Sources

  • Microsoft Learn — BCD boot configuration and the bootrec repair commands in the Windows Recovery Environment
  • Microsoft Learn — UEFI firmware, Secure Boot and boot order behaviour on Windows PCs

Written and maintained by the GuideHQ editorial team. More in Technology.