One question hides behind this error, and it has two wildly different answers: can the machine still see the drive it’s meant to boot from? A minute in the BIOS tells you — and your next move, your risk, and the fate of your files all turn on which answer you get.
Go into the BIOS and look for the drive. Listed but not booting → a fault in the software layer, usually very recoverable. Absent from the list → the drive or its connection has failed, and it’s a hardware job.
Press the power button and the firmware wakes, takes a headcount of the hardware, and works down its boot list hunting for a device that carries a startable operating system — inspecting each candidate for the signature and boot files that say ‘begin here’. The message on your screen is simply the firmware reporting that the search came up empty. Note what it did not mention: not a word about your documents, your photos, or the drive’s contents at large. The hunt for a working ignition failed; nobody has looked at the rest of the car.
Before you reach the BIOS fork, dismiss the two silly impostors: pull out every USB stick and external drive (machines will cheerfully try to boot an empty memory stick and then give up), and on a desktop, reseat the drive’s power and data cables — a knocked connector throws this precise screen.
If the drive shows up by name at its correct size, the hardware is answering and the trouble lives in software: a boot order aimed somewhere daft (put the internal drive first and try again — a free fix, and more common than you’d think), boot files scrambled by a power cut or a forced shutdown, or a partition map damaged badly enough that the firmware no longer sees a system on the disk. Every one of those leaves your files exactly where they were. The careful route: if the data matters, get it to safety before repairing around it — the drive can be read from a bootable USB or on another computer, or imaged professionally; our missing partition work rebuilds torn maps from a read-only copy. Repair-first is tempting and usually survivable on a healthy drive — but it’s a bet with no upside when the documents can’t be replaced.
A drive missing from the firmware’s own hardware list — or showing as a garbled name or an impossible 0 GB — hasn’t lost its boot files; it has stopped answering as a device at all. On a hard drive that means failing electronics, mechanics or firmware; on an SSD it’s almost always the controller. No software can address a drive the computer can’t see, so this branch has precisely one useful move: power down and keep it down. Every hopeful restart spins failing mechanics or re-crashes broken firmware. On the bench, drives in this state are coaxed back to a readable condition just long enough to image — the substance of our drive not recognised service — and the files come off that image.
And the warning that deserves bold on either branch: reinstalling Windows is not a recovery method. It builds you a bootable machine by writing a fresh system across the disk — clearing the error and burying the files in the same stroke. Machine-first or data-first is a genuine choice; no one should make it by accident at a setup screen.
It means the machine couldn’t find a working system to start from — a symptom with several suspects, of which a dead drive is only one. Settings, cables, scrambled boot files and a lost partition map all throw the identical message. The BIOS fork below sorts the harmless majority from the real hardware failures in about a minute.
By design, no — it rewrites boot components and leaves your documents untouched. Two cautions in practice: on a physically weakening drive, repeated repair passes are heavy reading that hurries the decline; and a repair caught in an endless loop is telling you the problem runs deeper than boot files. One attempt is fair on a healthy-sounding drive; a campaign of them isn’t.
Both, by different routes. Hard drives usually land here through failing mechanics or corrupted sectors in the boot area; SSDs through controller and firmware faults that drop the whole drive off the boot list at once. The BIOS test reads the same either way — listed-but-not-booting versus not listed — and a not-listed SSD is very much a lab case, the data typically intact behind a failed controller.
Free 48-hour diagnostic on the bench, drives imaged before any repair, written quote before any work — and no fix, no fee on most jobs.