HP Laptop Shows Boot Device Not Found (3F0) Even Though SSD Passes Tests

0
3
Asked By MellowCedar47 On

My HP laptop suddenly stopped booting Windows. It first entered automatic repair and repeatedly reported that the PC did not start correctly. I ran sfc /scannow, which found and repaired corrupted files, and bcdboot C:Windows, which reported that the boot files were created successfully. The C: drive still contains Windows, Users, Program Files, and the other expected folders. HP Hardware Diagnostics reports that both the SMART check and storage component test passed. The BIOS detects "SATA2: Windows Boot Manager," and it is first in the UEFI boot order. Secure Boot is enabled and Legacy Support is disabled. However, selecting Windows Boot Manager from the F9 boot menu immediately returns to the HP Startup Menu, followed by "Boot Device Not Found — Hard Disk (3F0)." HP Sure Recover offers to restore or reinstall the operating system. I do not currently have another computer or a Windows installation USB. What could stop Windows Boot Manager from launching, and can I repair the EFI or BCD data without reinstalling Windows or losing my files?

2 Answers

Answered By QuietMaple22 On

On many HP laptops, press Esc repeatedly immediately after powering on to open the Startup Menu, then try F11 for System Recovery. If Windows Recovery loads, choose Troubleshoot, Advanced options, and Command Prompt. You can also try interrupting startup two or three times by powering the laptop off during the loading stage; Windows may then enter Automatic Repair and expose the same options. Once in Command Prompt, check the EFI partition and rebuild it with bcdboot rather than choosing HP Sure Recover, since Sure Recover may reinstall or restore the operating system.

NorthwindLark6 -

If recovery will not load at all, the remaining options are usually an HP recovery environment or Windows installation media. Before considering a reinstall, reseat the SSD if it is accessible and check that the drive is firmly connected; a loose connection can cause boot failures even when some diagnostics pass.

Answered By PixelHarbor8 On

Because the Windows files are present and the SSD diagnostics pass, the problem may be with the EFI system partition rather than the Windows installation itself. From Windows Recovery, open Command Prompt and use DiskPart to inspect the partitions: run `diskpart`, then `list disk` and `list vol`. Look for the small FAT32 partition, usually around 100–300 MB, marked as the EFI/System partition. Select it and assign a temporary drive letter, for example `sel vol ` followed by `assign letter=Z:`. Then rebuild the UEFI boot files with `bcdboot C:Windows /s Z: /f UEFI`. Verify the Windows partition letter first, since WinRE may assign Windows a letter other than C:.

MellowCedar47 -

That sounds promising, but I’m not sure how to reach Command Prompt from the HP Startup Menu.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.