"Boot Device Not Found. Please install an operating system on your hard disk" (3F0): how to fix it

Published Sources checked By helps.wiki editorial team

The PC's firmware could not find a drive with a working Windows boot loader, so it stopped before Windows started. Unplug USB devices, check that the drive is detected in the BIOS, and check the boot order and boot mode. If the drive is healthy, rebuild the boot files with BCDBoot. Find your BitLocker recovery key before changing firmware settings.

Applies to:Windows 10Windows 11HP laptops and desktopsmenu keys vary by model
On this page

What it means

This message comes from the PC's firmware (UEFI or BIOS), not from Windows. Before Windows can start, the firmware has to find a drive that holds a valid boot loader and hand control to it. Here it found nothing usable, so it shows the message and stops. On HP machines it reads "Boot Device Not Found. Please install an operating system on your hard disk. Hard Disk (3F0)", and 3F0 is the code HP shows for this situation.

Behind that one screen there are a few different problems: the drive is not seen at all, the drive is fine but its boot files are damaged or missing, or the boot order or boot mode in the BIOS no longer matches how Windows was installed. The steps below go from quick checks to repairs, so stop as soon as the PC starts.

One thing to sort out before you touch firmware settings: many Windows 10 and 11 PCs have an encrypted system drive (BitLocker or device encryption). Changing BIOS settings can make Windows ask for a recovery key on the next start. Sign in to your Microsoft account on another device and look up the BitLocker recovery key first, so you are not locked out.

Symptoms and causes

You are likely dealing with this problem if:

  • A black screen at power-on with the message and the code 3F0, and no Windows logo.
  • It often starts after a power cut, a failed update, a BIOS update or reset, a drive swap, or after plugging in a USB or external drive.
  • The internal drive may be missing from the BIOS.

The usual causes, most common first:

Boot order or boot mode changed
The Windows drive is no longer first, or the UEFI/Legacy setting does not match the mode Windows was installed in. Microsoft documents that a PC boots in the same mode it was installed with.
Damaged or missing boot files
The boot configuration data or the system partition that holds the boot files is corrupted, so the firmware sees the drive but finds nothing to start. Microsoft says BCDBoot can repair a corrupted system partition by recreating the boot files from the Windows partition.
Failing, loose or undetected drive
A dying HDD or SSD, a loose cable or connector, or a dead NVMe drive. If the BIOS cannot see the drive at all, reinstalling Windows will not help.
BIOS settings reset or corrupted
A BIOS reset or a faulty BIOS can lose the boot settings, including the boot order and boot mode.
A drive with no operating system
A new or wiped drive has no Windows on it, so there is nothing to boot.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Remove external devices and restart

Easy

The firmware may be trying to boot from a USB stick, disc or card and giving up. This takes a minute and costs nothing.

  1. Shut the PC down completely and unplug USB drives, external disks, discs and memory cards.
  2. Power on again and see whether Windows starts.

2.Check that the BIOS can see the drive

Easy

If the drive is not listed, no software fix will work, and you need to know that before changing anything else.

  1. Turn the PC on and press the firmware setup key repeatedly. Microsoft lists Esc, Delete, F1, F2, F10, F11 and F12 as common keys, and the right one depends on the model. Watch the first screen for an on-screen hint.
  2. Look in the boot menu or the system information page for your internal drive (HDD, SSD or NVMe).
  3. If the drive is listed, go on to the next step. If it is missing, power the PC off, unplug it, and reseat the drive and its cable or connector. If it is still not detected, the drive or its connection is faulty (see the last solution).
  4. If your PC has a built-in hardware test in its startup menu, you can run its drive test here. The exact key and test names differ by model, so check your model's support page.

3.Check the boot order and boot mode

EasyChanges settings

A reset or corrupted BIOS can leave the wrong boot order or boot mode. Correcting them fixes the error when the boot files are intact.

Before you start: First find your BitLocker recovery key (sign in at your Microsoft account on another device). Changing the boot mode, Secure Boot or other firmware settings can trigger a BitLocker recovery prompt. Write down any settings you change so you can put them back. If your BIOS offers a load-defaults option, it also clears custom settings such as RAID/AHCI choices.

  1. Open BIOS setup with the key for your model.
  2. Open the boot order or boot options page and put the Windows drive first. If you want to try the firmware's factory defaults, use the load-defaults option on the exit or main page (the key or menu name varies by model), then check the order again.
  3. Check that the boot mode (UEFI or Legacy) matches how Windows was installed. Windows keeps booting in the mode it was installed with, so switching the mode on an existing installation can cause exactly this error.
  4. Save and exit using the option shown on the BIOS screen.

4.Rebuild the boot files with BCDBoot

AdvancedChanges settings

If the drive is detected and healthy but the boot files are damaged, BCDBoot recreates them from the Windows folder on the drive.

Before you start: Work only on the Windows partition and double-check drive letters before running anything. Letters seen from the setup environment often differ from the ones you see in Windows. If the drive holds important files you have no copy of, copy them off first. If the drive is BitLocker-encrypted, it shows as locked from installation media and you cannot repair it until it is unlocked with the recovery key (step below). If you do not have the key, stop here.

  1. On another working PC, create Windows installation media. Plug it into the affected PC and boot from it (use the firmware's boot menu if it has one, or set the USB drive first in the BIOS boot order). On the first setup screen, press ShiftF10 to open a command prompt.
  2. List the volumes and find the one that contains the Windows folder.
    Command Prompt
    diskpart
list vol
exit
  3. If the Windows volume shows as locked or unreadable, the drive is encrypted. Unlock it with your 48-digit recovery key (replace D: and the key with your own), then check dir D:\ shows the Windows folder.
    Command Prompt
    manage-bde -unlock D: -RecoveryPassword 111111-222222-333333-444444-555555-666666-777777-888888
  4. Find the EFI System Partition (ESP) and give it a letter. It is a small FAT32 partition, roughly 100 to 300 MB. Replace the disk and partition numbers with the ones diskpart shows for your system.
    Command Prompt
    diskpart
list disk
select disk 0
list partition
select partition 1
assign letter=S
list vol
exit
  5. If no FAT32 system partition of that size exists on the disk, this repair cannot work. Go to recovery or reinstall (last solution) instead of continuing.
  6. Run BCDBoot, naming the Windows folder and the ESP. Match /f to the mode Windows is installed in: /f UEFI for a UEFI install (the usual case with an ESP), /f BIOS for a Legacy install, or /f ALL for both. Do not pick a different mode from the existing installation. Replace the letters with your own.
    Command Prompt
    bcdboot D:\Windows /s S: /f UEFI
  7. Close the prompt, remove the installation media and restart.

5.Try the bootrec repair sequence

AdvancedChanges settings

An alternative that rewrites the boot sector and rebuilds the boot configuration. It comes mainly from community guides and a Microsoft Q&A answer rather than a Microsoft support article, so treat it as a second choice after BCDBoot.

Before you start: These commands change the boot area of the disk. Make sure the drive is detected and healthy first. Same BitLocker rule as above: an encrypted volume must be unlocked before it can be repaired.

  1. Open a command prompt from installation media as described above (ShiftF10), then run the commands one at a time.
    Command Prompt
    bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
  2. If /scanos finds 0 Windows installations, use the BCDBoot method instead.
  3. Restart and check whether Windows loads.

6.Recover or reinstall Windows, or replace the drive

AdvancedBack up first

The last resort. It only helps when the drive is healthy. A failed drive needs replacing, and a new drive needs Windows installed on it.

Before you start: Reinstalling can erase the drive. Back up anything you need first if the files are still readable, and never install onto a drive that failed a hardware test. Have your Microsoft account details and BitLocker recovery key to hand.

  1. If the drive is healthy, reinstall Windows with installation media made by the Media Creation Tool. Check your PC maker's support page for any recovery option built into your model.
  2. If the drive failed or is missing from the BIOS, replace it, then install Windows.

Check that it worked

  • The PC starts past the HP logo and loads the Windows sign-in screen.
  • The Windows drive is listed first in the BIOS boot order and the PC restarts normally two or three times in a row.

If it still fails

  • If the drive is not detected in the BIOS or fails a hardware test, the problem is the drive or its connection. Back up what you can and have it replaced.
  • If the drive is healthy and BCDBoot did not help, check that the boot mode matches the installation, then consider recovery or a clean install with a backup first.
  • Contact HP Support with the 3F0 code and what you have already tried. Menu keys and recovery options differ by model, so the support page for your exact model is the best reference.

Questions

Does 3F0 mean my hard drive is dead?

Not necessarily. It can come from the boot order, boot mode or damaged boot files. But if the BIOS cannot see the drive at all, suspect the drive or its connection first.

Should I reinstall Windows right away?

No. If the drive is failing or not detected, a reinstall will not work and you may lose data. Check that the drive is detected first.

Sources

  1. BCDBoot Command-Line OptionsOfficial · Microsoft Learn
  2. Boot to UEFI Mode or Legacy BIOS modeOfficial · Microsoft Learn

Browse