The "no bootable device found" error indicates that your computer’s firmware cannot locate a storage drive containing a valid operating system. This usually stems from incorrect BIOS/UEFI settings, loose internal cables, or corrupted boot sectors. By systematically checking physical connections and adjusting startup configurations, you can often restore normal booting functionality without data loss.
Verify Physical Connections
Before diving into software settings, ensure that the hardware itself is properly connected. A loose SATA or power cable is a common culprit for this specific error message. If you are using a desktop PC, shut down the machine completely and unplug the power cord. Open the case to inspect the drives.
Check that the SATA data cable connecting the hard drive or SSD to the motherboard is secure on both ends. Also, verify that the power connector is firmly seated in the drive. For M.2 NVMe drives, ensure the drive is fully inserted into the slot and secured with the mounting screw. Reseating these components can resolve connectivity issues that prevent the system from detecting the storage media during the Power-On Self-Test (POST).
Check BIOS/UEFI Detection
Once physical connections are verified, restart the computer and enter the BIOS or UEFI setup utility. This is typically done by pressing
F2,
Delete,
F10, or
Esc immediately after powering on, depending on the manufacturer. Look for a section labeled "Storage," "SATA Configuration," or "Boot Devices."
If your drive does not appear in this list, it suggests a hardware failure or a disconnected component. If the drive is listed but still shows as non-bootable, proceed to the next steps. Note the model number of the detected drive to confirm it matches your installed hardware. This step helps distinguish between a total hardware failure and a configuration error.
Adjust Boot Order and Mode
Navigate to the "Boot" tab in the BIOS/UEFI interface. Ensure that your primary storage drive is set as the first option in the boot priority list. Sometimes, USB devices or network boot options may take precedence, causing the system to skip the hard drive entirely. Move your HDD or SSD to the top of the list and save changes before exiting.
Additionally, check the "Boot Mode" setting. Modern systems use UEFI, while older installations may rely on Legacy BIOS or CSM (Compatibility Support Module). If your operating system was installed in Legacy mode, switching to pure UEFI will result in a no bootable device error. Conversely, if you recently reset BIOS defaults, the mode may have reverted. Toggle between UEFI and Legacy/CSM to see if the system recognizes the boot partition.
Repair Boot Sector
If the drive is detected and configured correctly, the Master Boot Record (MBR) or GUID Partition Table (GPT) may be corrupted. You will need a Windows installation media or recovery drive to address this. Boot from the USB installer and select "Repair your computer" instead of installing Windows.
Navigate to Troubleshoot > Advanced Options > Command Prompt. Use the following commands to rebuild the boot configuration:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
These commands scan for Windows installations and rewrite the boot sector files. After running them, restart the computer to see if the issue is resolved. This method is particularly effective after unexpected shutdowns or disk failures.
Consider Hardware Failure
If none of the above steps work, the storage drive itself may be failing. Listen for unusual clicking sounds from HDDs, which indicate mechanical failure. You can also test the drive in another computer or use a USB enclosure to check if it is recognized externally. If the drive fails to appear in other systems, it likely requires replacement.
For critical data, consider professional recovery services before attempting further fixes. If the drive is accessible in another machine, back up your files immediately. Replacing a faulty drive and reinstalling the operating system is the final solution when hardware integrity is compromised. For related display issues that might mask boot problems, see
PC Still Using GPU: No Display or Boot Issue After Turning it On at Night.
Frequently Asked Questions
Why does my PC say no bootable device after a BIOS update?
A BIOS update often resets settings to their factory defaults, which can change the boot mode from UEFI to Legacy or vice versa. This mismatch prevents the system from recognizing the existing operating system installation. Re-enter the BIOS and adjust the boot mode to match your original OS installation type.
Can I fix this error without losing my data?
Yes, most troubleshooting steps such as checking cables, adjusting BIOS settings, and repairing the boot sector do not erase your files. Data loss only occurs if you format the drive or replace the hardware. Always attempt software repairs and connection checks before considering any actions that modify partition tables.
What if the drive is missing from the BIOS entirely?
If the drive does not appear in the BIOS storage list, it indicates a hardware communication failure. This could be due to a faulty cable, a bad port on the motherboard, or a dead drive. Try swapping the SATA cable or connecting the drive to a different port to isolate the problem component.
Does this error mean my hard drive is broken?
Not necessarily. The error primarily indicates that the firmware cannot find a valid bootloader, which can happen due to software corruption or misconfiguration. However, if the drive is undetectable in BIOS and reseating cables fails, the drive may indeed be physically damaged. Diagnostic tools can help determine if the drive is alive but unreadable.
How do I enter BIOS if my keyboard doesn't work?
Try using a USB keyboard plugged directly into the motherboard ports rather than front panel connectors. Some motherboards require specific keys like
Delete or
F2 to be pressed repeatedly right after powering on. If the keyboard fails, you may need to clear the CMOS by removing the motherboard battery for a few minutes to reset settings automatically.