Diagnose and correct “No bootable device” or a missing system drive

Firmware reports No bootable device, Boot device not found, or a similar message. The affected system drive may be a SATA HDD, SATA SSD, NVMe SSD, or another ordinary consumer boot device.

Searchable Windows error codes and exact messages

If firmware cannot find a boot target, Windows has not started and there may be no Windows error code. Search the exact firmware message and computer model. Common phrases and vendor identifiers include No bootable device, No bootable devices found, Boot device not found, BootDevice Not Found 3F0, Hard Disk 3F1, Default Boot Device Missing or Boot Failed, Operating System not found, Error 1962: No operating system found, UEFI Interactive Shell, Shell>, HTTP Boot, HTTPS Boot, SupportAssist OS Recovery, Checking media presence, Start PXE over IPv4/IPv6, PXE-E61, and PXE-M0F. The 3F0, 3F1, 1962, PXE, UEFI-shell, network-boot, and OEM-recovery identifiers are firmware/vendor text, not Windows codes.

If the machine reaches Windows boot code or fails after the boot handoff, these Windows identifiers can apply:

Do not treat a PXE code as a network problem automatically. It often appears only because firmware did not find a usable local boot target and moved to the next item in boot order.

Use this procedure before performing any Windows boot-file repair. It determines whether the failure is hardware visibility, firmware boot order, recovery-environment visibility, or missing Windows boot metadata.

Do not use this as a Windows repair procedure when the computer cannot complete power-on self-test, cannot display firmware setup, or has confirmed motherboard failure.

The Windows build and precise moment the problem began may remain unknown. Whether firmware and WinRE can detect the system drive may not remain unknown.

• Access to firmware setup or the one-time boot menu
• Windows recovery or installation USB if the drive is visible to firmware
• For desktop SATA devices, safe access to power and data cables if hardware inspection becomes necessary

Power the computer off completely. Disconnect nonessential USB storage, memory-card readers, docks, and external drives. Leave the keyboard, mouse, display, and Windows recovery USB disconnected until directed.

1. Turn the computer on and enter firmware setup.
2. Open the storage, information, or device page—not only the boot-order page.
3. Determine whether the system HDD/SSD/NVMe is detected by model or capacity.
4. Record the result before changing anything.

If the drive is absent from firmware

Continue with the hardware-visibility branch in section 8. Windows commands cannot repair a drive firmware cannot see.

If the drive is present in firmware

1. Check whether Windows Boot Manager appears in the boot list.

2. If present, select it once from the one-time boot menu.

3. If absent or unsuccessful, start the Windows recovery USB.

4. Open Command Prompt and run:

   diskpart
   list disk
   list volume
   exit
   

5. Determine whether the same physical drive and its partitions appear in WinRE.

Branch A — Drive absent from firmware

1. Power the computer off and disconnect AC power. On a laptop with no serviceable storage access, skip physical disassembly and use the manufacturer's diagnostic procedure.
2. For a desktop SATA HDD or SSD, reseat both the SATA data cable and power connector.
3. If still absent, test one known-good SATA cable and another motherboard SATA port.
4. For an accessible M.2 device, reseat it only when the computer is powered down, service access is permitted, and electrostatic precautions are available.
5. Run the firmware or manufacturer storage diagnostic.
6. If the drive appears only intermittently, stop repair attempts and create an image or recover important data before further reboot cycles.
7. Replace a cable, drive, slot, or board only after comparative testing isolates it.

Branch B — Drive visible in firmware but absent from WinRE

1. Confirm the recovery USB itself appears as a separate disk so it is not being mistaken for the internal drive.
2. Record the current storage-controller setting without changing it.
3. If the failure began immediately after a BIOS reset or a known AHCI/Compatibility change, restore the previously used setting.
4. If the prior setting is unknown or the system uses RAID/VMD/SCSI, stop here and use the deferred specialist storage-driver procedure. Do not cycle blindly through controller modes.

Branch C — Drive and partitions visible in WinRE

1. Do not initialize or format the drive.
2. If Windows Boot Manager is absent while the EFI partition exists, use FIX-003.
3. If the recovery screen identifies missing or corrupt BCD, use FIX-004.
4. If the disk is visible but file reads fail or the device repeatedly disappears, stop and treat it as a storage-health case before writing boot files.

Branch D — Wrong boot target selected

1. In firmware boot order, move the verified Windows Boot Manager entry for the intended drive ahead of USB, network/PXE, and unrelated disks.
2. Save changes and restart without the recovery USB.

• Drive absent in firmware and diagnostics fail: Hardware path is the primary problem.
• Drive present in firmware and WinRE, but Windows Boot Manager absent: Repair the UEFI entry.
• Drive present only after reseating or power cycling: Treat the device or connection as unreliable; do not declare a permanent repair yet.
• Drive appears in firmware but not WinRE: Controller mode or a storage driver is implicated.
• Windows starts after correcting boot order: No Windows-file repair is required.

• Do not initialize the disk when Disk Management or setup offers to do so.
• Do not format any partition.
• Do not rebuild BCD before establishing that the drive is stable and readable.
• Do not repeatedly power-cycle a failing drive when data recovery matters.
• Do not assume “SSD” when the system may use an HDD or another storage type.

Restore any changed boot-order or controller setting to its recorded original value if it does not improve detection or booting. Cable and port changes can be reversed after testing, but retain the configuration that comparative testing proves stable.

• Firmware detects the drive on at least two cold starts.
• WinRE consistently detects the drive and its expected partitions.
• Windows Boot Manager points to the intended drive.
• Windows starts successfully twice.
• Storage diagnostics do not report a failure.

Confidence is approximately 90% for the decision path because the firmware/WinRE visibility split sharply narrows the problem. Stop if the drive is intermittent, makes abnormal mechanical sounds, reports diagnostic failure, or requires RAID/VMD/SCSI drivers not covered in this priority batch.