Boot Device Not Found (HP 3F0, Dell, Lenovo): Fixes, and When the Drive Has Failed

“Boot Device Not Found. Please install an operating system on your hard disk. Hard Disk (3F0)” on an HP, “No bootable devices found” on a Dell, “Default Boot Device Missing or Boot Failed” on a Lenovo — different words for the same event: the computer’s firmware could not find a drive with an operating system on it.

Sometimes the drive is fine and a setting or cable is wrong; sometimes the drive has failed and each restart makes the data on it harder to recover. This guide explains the causes, gives the fixes in the order that protects your data, and then covers the three brands’ own diagnostics so you can tell which situation you are in.

When a computer starts, its BIOS or UEFI firmware looks through the boot order for a device containing a boot loader. If none of the listed devices answers, or the one that answers has no valid boot record, the firmware stops with this message. It can therefore come from two very different places:

• The drive is not being detected at all — a connection fault, a changed setting, or a drive whose electronics, firmware or mechanics have failed.
• The drive is detected but the boot files on it are damaged — a corrupted Master Boot Record, Boot Configuration Data or EFI partition, usually after an interrupted update, a power cut or malware.

The single most useful thing you can do is find out which. The brand-specific sections below show where to look.

• Incorrect boot order or boot mode. The firmware is looking at the wrong device first, or is set to UEFI when Windows was installed in Legacy mode (or the reverse).
• A loose SATA cable or M.2 SSD. Common after a drop, a move, or a RAM upgrade.
• Corrupted boot files. MBR, BCD or the EFI system partition damaged by an interrupted update, a power loss or malware.
• Drive failure. Bad sectors in the boot area, a failed head or motor on a hard disk, or a failed controller on an SSD. The drive may still appear in the BIOS but cannot be read from.
• Outdated or corrupted firmware. Rare, but a BIOS update can reset the SATA mode or drop support for a drive.
• An external device in the way. A USB drive or SD card left in a port that sits first in the boot order.

Unplug every USB device, SD card and dock. Shut down, disconnect the charger (and the battery if it is removable), hold the power button for 15–20 seconds, reconnect and start. This clears more boot errors than anything else on the list.

Enter setup (HP: Esc then F10; Dell: F2; Lenovo: F1 or F2) and look for the drive under System Information, Storage or Boot Options. If it is listed with its model name and capacity, the hardware sees it — go to steps 3 and 5. If it is missing, go to step 4. If it appears with a wrong name or 0 GB, its firmware is damaged: stop restarting and read the recovery section below.

Make sure the internal drive is first in the boot order. Then check the boot mode: if Windows was installed in UEFI mode the firmware must be in UEFI mode with Legacy/CSM off, and vice versa. If you are not sure, choose Load Defaults / Apply Defaults, save and restart.

If the BIOS does not list the drive, open the base cover (check the service manual for your model; this may affect the warranty) and reseat the M.2 SSD or the SATA connector. Listen when you power on: a drive that clicks, buzzes or repeatedly spins up and down has a mechanical fault and should not be powered on again outside a lab.

Every brand has a pre-boot hardware test that runs without Windows and reports on the drive. The brand sections below cover HP, Dell and Lenovo. A drive that fails its test is failing; a drive that passes points the problem at the boot files, which are fixable.

On another computer, make a Windows installation USB with Microsoft’s Media Creation Tool. Boot the affected computer from it, choose Repair your computer → Troubleshoot → Startup Repair. If that fails, open the Command Prompt from the same menu and run:

• bootrec /fixmbr
• bootrec /fixboot
• bootrec /scanos
• bootrec /rebuildbcd

Restart. This repairs damaged boot records on a healthy drive. Do not run chkdsk /r at this stage: on a drive with bad sectors it writes to the disk and discards what it cannot read.

3F0 is HP’s code for “no bootable device found”. It is the most-searched version of this error because HP’s firmware shows the code prominently and because HP laptops are, by volume, the ones it happens to most. The HP-specific steps:

1. Hard reset as in step 1. HP’s own support article lists this first for a reason — it resolves a large share of 3F0 errors caused by the drive not initialising in time.
2. Run HP PC Hardware Diagnostics. Power on and tap Esc repeatedly, then F2. Choose Component Tests → Hard Drive → Quick Test (this is the drive’s Short DST). A pass means the drive is healthy and the boot files are the problem. A fail shows a 24-character Failure ID and a code — Hard Disk 1 Quick (303) or Hard Disk 1 Full (305) are the drive-failure codes — which is what HP asks for in a warranty claim. Our Short DST failed guide explains what to do next when the test fails.
3. Restore BIOS defaults. Tap Esc then F10, open File → Apply Defaults and Exit (older models: Restore Defaults). Then check System Information for the drive and Boot Options for the order.
4. Reseat the drive if it is missing from System Information.
5. HP Recovery — only after the data is safe. If the drive passes diagnostics but Windows cannot be repaired, F11 at power-on starts HP Recovery Manager, which reinstalls Windows and erases the drive.

Dell shows two different messages depending on how far the failure goes. “No bootable devices found” means the drive may be present but has no valid boot record — work through steps 3 and 6. “Hard Drive – Not Installed” in the BIOS, or “Alert! Hard drive not found”, means the drive is not being detected at all. Run the F12 diagnostics: code 2000-0141 confirms no drive is detected, 2000-0142 means the drive is present but failing its self-test. The full Dell procedure, including the SATA-mode trap, is in our Dell hard disk not installed guide.

Lenovo’s version usually appears with a prompt to insert recovery media. Enter the BIOS with F1 (ThinkPad) or F2 / the Novo button (IdeaPad), check the drive is listed under Storage or Information, and set Boot Mode to match the Windows installation — most Lenovo machines since 2015 use UEFI. Lenovo Diagnostics (F10 at power-on, or from the Novo menu) includes a storage Quick Test equivalent to the HP and Dell ones.

• Stop restarting. If the drive is not detected, fails diagnostics or shows the wrong capacity, further attempts do not help and can damage the platters or wear the last of an SSD’s controller life.
• Do not reinstall Windows or run HP/Dell Recovery until the data is copied or recovered — both erase the drive.
• Do not run CHKDSK, “repair” tools or recovery software on a drive that is failing its self-test. They read the damage repeatedly and write to the drive.
• Do not open the drive or swap its board. Platters are ruined by dust outside a clean room, and modern drives will not read with another drive’s board.

Bring the drive in — or the whole laptop — when the diagnostics fail, the drive is missing from the BIOS, or it appears with the wrong name or capacity. The analysis is free and takes 25–30 minutes; you get a firm quote and pay only if the data is recovered.

• Boot area unreadable, drive otherwise alive: the drive is imaged on a hardware imager that handles bad sectors, and the files are rebuilt from the image. From ₹3,000 for a single hard disk.
• Firmware fault (wrong name or 0 GB in the BIOS): service-area repair with manufacturer-level tools, then imaging. From ₹6,000.
• Mechanical fault (clicking, not spinning): head or motor replacement in the Class 100 clean room. From ₹10,500.
• SSD fault: controller in technological mode or direct NAND reads. See SSD data recovery cost, from ₹5,000.

We recover from laptop drives and desktop hard disks of every brand, on a no-data-no-charge basis. The lab is in Pune; drives reach us by courier from across India. Contact us or call +91 9859 070809.

• Shut down properly and use a UPS or surge protector on desktops — interrupted writes are the usual cause of corrupted boot files.
• Keep a backup of anything that matters somewhere other than the boot drive.
• Check the drive’s SMART health every few months (CrystalDiskInfo). Reallocated or pending sectors are the warning that a boot error is coming.
• Keep the BIOS and storage firmware updated, but never flash on a low battery.

Related guides

• BitLocker Hell: The Challenges of Recovering Data from an Encrypted and Failed PC Drive
• Data Loss from Water or Fire Damage: Can Your Device Be Saved?
• The Clicking Hard Drive: What That Terrifying Sound Means and What to Do