It means the firmware looked where it expected a bootloader and did not find one. That can be a setting, a mode mismatch, a damaged boot sector, or a failed disk — and they are worth separating before assuming the worst.
Half the time the disk is perfectly healthy and something about where or how the machine was looking has changed. The other half, the drive is failing — and the difference is visible in the BIOS.
Enter the BIOS or UEFI setup — usually F2, F12, Del or Esc at power-on. First question: is the drive listed at all? If it is not, skip to the hardware section below. If it is listed, check the boot order: a plugged-in USB stick, an added second drive, or a settings reset after a flat CMOS battery can all push the real boot device down the list.
Then check the mode. A disk installed in UEFI mode will not boot in Legacy or CSM mode and vice versa, and firmware updates sometimes flip this. The disk is entirely healthy; the machine is simply looking for the wrong kind of bootloader. Toggling it back is free and instant.
If the drive appears in the BIOS and the mode is right, the boot structures themselves may be damaged — the MBR or GPT, the EFI system partition, or the boot configuration. Causes include a failed update, an abrupt power loss during a write, malware, or a cloning tool that finished untidily.
Your data is intact underneath. That is worth stressing, because this is the point where people reinstall Windows and lose it. If the files matter, the safe order is to remove the drive, read it on another machine or from a live USB, copy the data off, and only then repair the boot structures.
If the BIOS does not list the drive, or lists it with a blank model or a nonsensical capacity, the fault is hardware. Listen: clicking or ticking means heads and the machine should be switched off immediately; silence with no spin means the board or motor; a normal spin with no detection points at the board or firmware, which is among the more recoverable faults.
An intermittently detected drive is the most dangerous of these, because it invites repeated reboots. Each one costs reads you would rather have kept.
Check boot order and boot mode. Reseat the cable, or try another SATA port and cable on a desktop. Try the drive in another machine or in a USB caddy — if it mounts, copy the data off before doing anything else. If it is not detected anywhere, or makes noise, stop.
A single drive is from £300 +VAT after a free 48-hour diagnostic and a written quote, and most jobs are no fix, no fee. Send the drive rather than the whole machine where you can — a local shop will remove it in minutes.
That the firmware searched its configured boot devices and found no valid bootloader. It does not necessarily mean the drive has failed — a changed boot order, a UEFI/Legacy mode mismatch, or a damaged boot sector all produce the same message on a perfectly healthy disk.
Usually not. In most cases the data is intact and something about the boot path has changed or been damaged. The risk is the standard response: Startup Repair and reinstalling both write to the disk and can destroy what a recovery would have read.
Look in the BIOS or UEFI setup. If the drive is listed with the correct model and capacity, the hardware is working and the problem is logical. If it is missing, shows a blank model, or reports an odd capacity, the fault is hardware — and if it is clicking, switch off immediately.
Not before the data is safe. Both write to the disk. If the files matter, take the drive out, read it in another machine or a USB caddy, copy everything off, and repair the boot structures afterwards.
A single drive is from £300 plus VAT, fixed in a written quote after a free 48-hour diagnostic. Most jobs are no fix, no fee; clean-air or donor-part work carries a 50% deposit with the balance due only on success.