ThisCalculator

Everyday

Fixed Operating System Cannot Be Booted? Fix It Now

Updated · Standard formula, shown below

If your computer shows a message like “Fixed Operating System Cannot Be Booted” or “No bootable device,” it means the BIOS/UEFI cannot find a valid operating system on the hard drive. This is a common startup error, and in most cases you can fix it yourself by checking boot order, reconnecting drives, or repairing the boot loader—no data loss required.

What This Error Means

The message appears during the Power-On Self-Test (POST), before Windows, Linux, or macOS loads. The firmware (BIOS or UEFI) looks for a bootable device in the order you set (e.g., USB, then hard drive, then network). When it finds a drive but cannot locate a valid boot sector or EFI system partition, it reports that the fixed disk has no bootable operating system.

This is different from a blue screen or a kernel panic—those happen after the OS starts loading. This error means the OS never even began to load.

Most Common Causes

  • Wrong boot order – The system tries to boot from a USB stick or DVD that isn’t bootable, or the hard drive is not first in the list.
  • Loose or failed data cable – On desktop PCs, the SATA cable may have come loose or the drive may be failing.
  • Corrupted boot loader – The Master Boot Record (MBR) or GUID Partition Table (GPT) is damaged, often after a power outage, improper shutdown, or a failed update.
  • BIOS/UEFI settings changed – A recent BIOS update or a reset to defaults may have disabled the drive controller or changed the boot mode from UEFI to Legacy (or vice versa).
  • Dead CMOS battery – If the battery that stores BIOS settings is drained, the system may lose its boot configuration each time it powers off.

Step-by-Step Fixes to Try

  1. Restart and enter BIOS/UEFI. Press the key shown on screen (often Del, F2, F10, or Esc) during startup. Look for a “Boot” or “Startup” menu.
  2. Check boot order. Ensure your main hard drive or SSD is first. If a USB stick is plugged in, remove it—it may be interfering.
  3. Verify the drive is detected. In the BIOS, look for a list of connected drives. If your drive is not listed, power off, open the case (for desktops), and reseat the SATA cable and power connector. For laptops, reseat the drive if accessible.
  4. Toggle UEFI/Legacy mode. If your system uses UEFI, try switching to Legacy/CSM, or vice versa. This often fixes mismatched boot modes.
  5. Reset BIOS to defaults. In the BIOS, choose “Load Optimized Defaults” or “Reset to Factory Settings.” Save and exit.
  6. If the drive is detected but still won’t boot, you need to repair the boot loader using recovery media (see next section).

Repairing the Boot Loader

If the drive is detected but the boot loader is corrupt, you can repair it using installation media. For Windows, create a bootable USB with the Windows installation tool (from Microsoft’s website). Boot from that USB, select “Repair your computer,” then go to Troubleshoot → Advanced Options → Command Prompt.

Type the following commands, pressing Enter after each:

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

For UEFI systems, you may also need to run bootrec /fixboot and then bcdboot C:\Windows (adjust the drive letter if Windows is not on C:). For Linux, you can use a live USB and run grub-install or update-grub depending on your distribution.

If these commands fail, the drive may have physical issues—back up your data immediately if you can access it via another computer.

When It’s a Hardware Problem

If the drive is not detected in BIOS at all, it’s likely a hardware issue. Try the drive in another computer (if possible) to confirm. Common hardware failures include:

  • Failed SATA cable or power connector
  • Dead hard drive motor or corrupted firmware
  • Faulty motherboard SATA port
  • Loose M.2 SSD (reseat it firmly)

If you have a second drive, try booting from it to isolate the problem. If the error persists with a known-good drive, the motherboard or PSU may be at fault.

How to Prevent This Error

  • Always shut down properly—don’t force power off.
  • Keep your BIOS/UEFI updated, but only from the manufacturer’s official site.
  • Use a surge protector or UPS to avoid power spikes.
  • Back up your data regularly, so a boot failure is an inconvenience, not a disaster.
  • If you have a desktop, periodically check that SATA cables are firmly connected.

Frequently Asked Questions

Will I lose my files if I get this error?

Usually no. The error is about the boot loader, not your data. Your files remain on the drive. If you can’t boot, you can often recover files by connecting the drive to another computer or using a live Linux USB.

What’s the difference between MBR and GPT?

MBR (Master Boot Record) is an older partitioning scheme, GPT (GUID Partition Table) is newer. UEFI systems typically use GPT, while Legacy BIOS uses MBR. If your boot mode doesn’t match the partition style, the system can’t boot.

Can a dead CMOS battery cause this?

Yes. If the battery dies, BIOS settings reset each time you power off. If the default boot order doesn’t include your drive, you’ll get this error. Replacing the coin-cell battery (CR2032) on the motherboard usually fixes it.

Why does it say “Fixed” disk?

“Fixed” is an old term for a non-removable hard disk, as opposed to a floppy or removable USB drive. The message means the fixed disk (your internal drive) lacks a bootable OS.

Should I try a system restore?

If you have a restore point, you can try System Restore from the recovery environment. However, if the boot loader is corrupt, you’ll need to repair it first. System Restore doesn’t fix boot loader issues.

Is this error the same as “No bootable device”?

Yes, they are essentially the same. Different manufacturers phrase it differently. Both mean the firmware cannot find a valid OS to start.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.