A Bootable Device Has Not Been Detected | Quick Fixes

Seeing “a bootable device has not been detected” in white text on a black screen feels harsh, especially when you just need your laptop or desktop to start. The good news is that this message usually points to a short list of causes that you can check in a calm, methodical way.

This guide walks you through what the error means, how to spot the most common triggers, and the practical steps that fix the issue in many Windows setups. You will learn what to try first, when to touch firmware settings, and when the drive itself may have failed.

What A Bootable Device Has Not Been Detected Error Means

When this message appears on your screen, the firmware has finished its basic checks and tried to hand control over to an operating system. At that handoff point it either cannot see any drive at all or does not find valid boot files on the device it tried first.

On many machines this error appears under slightly different wording such as “No bootable device found” or “Boot device not found”. All of these messages describe the same core problem: the firmware has nothing it can start.

Under the surface, three broad conditions usually create this situation.

• No boot drive detected — The internal SSD or hard drive is missing, disconnected, or not powered, so the firmware does not list it as a device.
• Boot order points to the wrong device — The firmware tries to start from an empty USB stick, a data drive without an operating system, or a network entry instead of your system disk.
• Boot files are damaged — The drive is present, yet its partitions, file system, or boot records are corrupted, so startup files cannot load.

Understanding which of these matches your situation helps you pick the right fix and avoid steps that add risk without a clear benefit.

Many times the problem sits in simple configuration, such as a boot list that changed after a firmware update or after adding a new disk. In other cases the pattern of errors, strange noises from a hard drive, or complete absence of the disk in setup menus points more clearly toward failing hardware.

Common Triggers For This Boot Error

The phrase on the screen looks serious, yet the root cause is often simple. Recent hardware changes, loose connections, or a one line setting in firmware can all lead to the same “bootable device not detected” message.

In other cases the disk itself is failing. Repeated clicking from a hard drive, long pauses when the logo appears, or a history of file errors often line up with a physical fault on the drive.

Laptops that travel often see this message after a bump loosened the storage module or its adapter. Desktops that were moved to a new desk sometimes show the same error when a data cable was strained or an older power supply struggles to deliver a steady line to the drive.

Quick Checks Before You Change Settings

Before you change boot menus or reinstall Windows, clear a few simple checks. These steps often restore normal startup with minimal effort and no extra tools.

1. Remove external drives — Unplug USB sticks, memory card readers, and external hard drives, then restart to see if the internal disk now boots.
2. Power cycle the computer — Turn the machine off, disconnect the power cable and battery if it is removable, hold the power button for ten seconds, wait a short moment, then reconnect and start again.
3. Check for stuck buttons — Make sure no button is wedged down on the keyboard, especially the function row or special boot shortcuts that might send you into a boot menu.
4. Run any built in diagnostics — Many laptops from brands such as HP, Dell, Lenovo, and Acer have a startup shortcut that opens hardware tests for memory and drives. If your menu offers a short disk test, run it now.

If none of these steps change the message, you can move on to the firmware level checks that control which device the machine starts from first.

Fixing The Bootable Device Not Detected Error On Windows

The next stage is to confirm that the system disk appears in firmware setup and to adjust the boot order if needed. This often resolves a repeating bootable device error loop after a new USB device or secondary drive was added.

1. Enter firmware setup — Restart and tap the usual startup shortcut for your brand, such as F2, F10, F12, Delete, or Escape, until the setup screen opens instead of the error message.
2. Find the boot or startup page — Use the arrow keys or mouse to open the section that lists boot order, boot options, or startup devices.
3. Confirm the system disk is listed — Look for your SSD or hard drive by model name or by size. If it does not appear, the issue is likely a loose cable, failed drive, or adapter problem.
4. Set the system disk first — Move that drive to the top of the boot list above USB, DVD, and network entries so firmware picks it before anything else.
5. Check UEFI and legacy modes — If your system uses UEFI with Secure Boot, confirm that the Windows Boot Manager entry linked to your disk sits near the top. Only switch between legacy and UEFI mode when you know how the disk was originally set up.
6. Save and restart — Use the on screen hint, usually F10, to save changes and reboot, then see whether Windows starts normally.

If the system disk never appears in firmware, work on the physical side. For a desktop that means opening the case, reseating data and power cables, and trying a different port. For a laptop, reseating or replacing the drive usually needs a small Phillips screwdriver and care with any warranty seals.

Fix Drive Issues And File System Problems

When the disk shows up in firmware but the “a bootable device has not been detected” message still appears, the next likely cause is damage to partitions, boot records, or the file system. At this stage you often need Windows installation media or a recovery drive created on another computer.

1. Boot from Windows install media — Create a bootable USB with the official Media Creation Tool, plug it in, choose it as the first boot device, and start the installer until the language screen appears.
2. Open repair options — Instead of installing, pick the repair link to reach the advanced options menu with tools for startup repair and command prompt.
3. Run startup repair — Choose the automatic startup repair tool and let it scan for damaged boot files, then restart to test whether the error clears.
4. Repair boot records manually — If the automatic tool cannot fix startup, open command prompt from the same menu and run the standard bootrec commands to rebuild boot configuration data.
5. Check disk health — Still at the command prompt, run a basic chkdsk scan on the system volume to look for file system errors that block startup.

When boot files are repaired and the file system is healthy, most systems start as before. If problems keep coming back or repairs fail, that often points to a drive that is reaching the end of its life.

If you feel unsure once commands and repair tools appear, pause instead of guessing. A careful visit to a local repair shop or a trusted technician is usually cheaper than risking extra damage to a drive that still holds work documents, photos, or other data that matters to you.

Reinstall Windows Or Replace The Drive

Sometimes the only clean way past a bootable device error is to reinstall the operating system on top of your existing disk or on a fresh replacement drive. Before you take that step, decide first whether you need to rescue data from the old installation.

1. Back up what you can — If you still reach recovery tools or can attach the disk as a secondary drive to another computer, copy personal files to an external disk or cloud storage.
2. Install Windows on the same disk — When hardware tests say the drive is healthy, a fresh installation on the same disk can clear deep boot issues and software conflicts.
3. Replace a failing drive — Frequent clicking, grinding noises, or repeat “boot device not found” messages after repairs all point toward a drive that needs replacement.
4. Install on a new SSD — Swapping an older hard drive for a modern SSD brings a smoother start and often a clear performance boost once you reinstall Windows and drivers.
5. Keep the old disk for data recovery — When possible, keep the old drive untouched until you decide whether you need a specialist to attempt further recovery.

A fresh Windows installation followed by drivers and updates normally removes any remaining software based triggers for boot errors. From there your attention shifts to staying protected against future problems.

Before you give up on the machine, take a moment to check warranty options from the maker.

Prevent Future Boot Errors And Protect Data

Once your system starts again without the “a bootable device has not been detected” warning, it helps to add a few habits that lower the chance of seeing the same screen later. Small steps with backups, updates, and physical care of the device go a long way.

1. Set up regular backups — Use built in Windows backup tools or trusted third party software to keep copies of personal files on another disk or in cloud storage.
2. Shut down cleanly — Avoid forcing power off unless the system is frozen, since sudden cuts raise the chance of corrupted boot data.
3. Keep firmware and drivers current — Install stable updates from your laptop or motherboard maker that improve storage handling and start up behavior.
4. Handle the device gently — If your computer still uses a mechanical hard drive, avoid sharp bumps during use and carry the machine in a padded bag.
5. Give the interior fresh air — From time to time, have dust cleared from vents and fans so heat does not shorten the life of drives and other parts.

When you treat your system disk as the core of the machine and give it steady backups, handling, and clear startup settings, this message on screen becomes a rare event instead of a constant worry.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback