Fix "Operating System Not Found" / "Missing Operating System"

The fast answer. "Operating system not found", "Missing operating system", and "An operating system wasn't found. Try disconnecting any drives that don't contain an operating system." all mean the same thing: the BIOS/UEFI firmware checked its boot devices and couldn't find a bootloader on any of them. Most often it's looking at the wrong device — unplug every USB drive and external disk, reboot, and enter BIOS/UEFI setup to confirm the internal drive is detected and first in the boot order. If the drive is detected and the order is right, the boot records are damaged. Boot a Windows 10/11 install USB, open Command Prompt (Repair your computer → Troubleshoot → Command Prompt, or press Shift+F10 at the first setup screen), and run:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

Then reboot. On UEFI systems bootrec /fixboot may return "Access is denied" — that's expected; use bcdboot instead (Step 5 below).

Why this happens

Wrong boot device — a non-bootable USB stick, external disk, or a second data drive is ahead of the Windows drive in the boot order. This is the most common cause, and it's exactly what the "try disconnecting any drives" wording is hinting at.
Drive not detected — a loose SATA or M.2 connection, a disabled controller port, or a failing/dead drive. If the firmware can't see the disk at all, no software command can fix it.
BIOS mode doesn't match the disk — a GPT-partitioned disk needs UEFI mode; an MBR disk needs Legacy/CSM mode. A CMOS reset, BIOS update, or motherboard swap can flip the mode and make a perfectly good Windows install invisible to the firmware.
Damaged MBR, boot sector, or BCD — an unclean shutdown, a failed update, malware, or a bad clone corrupted the structures the firmware reads to find Windows.
System partition not marked active — on legacy MBR disks, the partition holding the boot files must carry the active flag. A partition tool or clone job can clear it.

Step-by-step fix

Step 1 — Unplug external media and check the boot order

Unplug every USB drive, external disk, SD card, and CD/DVD, then reboot. If Windows starts, the firmware was booting the wrong device. Enter BIOS/UEFI setup (usually Del, F2, or Esc at power-on) and move the internal Windows drive to the top of the boot order so it doesn't happen again.

Step 2 — Confirm the firmware actually detects the drive

Still in BIOS/UEFI setup, look at the storage or boot-device list. If the internal drive is missing, power off and reseat the SATA data and power cables (or the M.2 module), and check that the controller port isn't disabled in setup. If the drive still doesn't appear after reseating, treat this as hardware: run the drive maker's diagnostics from a bootable tool if possible, and plan on recovering data and replacing the drive. None of the commands below can repair a drive the firmware can't see.

Step 3 — Match the BIOS mode to the disk's partition style

Boot from a Windows 10/11 install USB and press Shift+F10 at the first setup screen to open Command Prompt. Check whether the disk is GPT or MBR:

diskpart
list disk
exit

An asterisk in the Gpt column means the disk is GPT and the firmware must boot in UEFI mode. No asterisk means MBR, which needs Legacy/CSM mode. If the BIOS setting doesn't match, change it in firmware setup, save, and reboot — on many machines this alone clears the error, especially after a CMOS reset or board swap.

Step 4 — Run Startup Repair

From the install USB choose Repair your computer → Troubleshoot → Startup Repair. It detects and rebuilds missing or damaged boot files automatically. Let it finish and reboot. If it reports it couldn't repair the PC, continue to Step 5.

Step 5 — Repair the boot records manually

Open Troubleshoot → Command Prompt and run these in order:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

When bootrec /rebuildbcd finds a Windows installation, type Y to add it. On UEFI/GPT systems bootrec /fixboot often returns "Access is denied" — that's normal there. Rebuild the EFI boot files with bcdboot instead: assign a letter to the EFI System Partition, then point bcdboot at the Windows folder (confirm the Windows drive letter first — it may not be C: inside the recovery environment):

diskpart
list vol
sel vol <EFI-FAT32-vol#>
assign letter=S:
exit
bcdboot C:\Windows /s S: /f UEFI

You should see "Boot files successfully created." Reboot and test. The full walkthrough is on the 0xc000000e page.

Step 6 — Mark the system partition active (MBR/legacy only)

On an MBR disk, the partition holding the boot files must be marked active. In Command Prompt:

diskpart
list disk
sel disk 0
list partition
sel partition 1
active
exit

Replace sel partition 1 with the actual System Reserved or Windows partition — typically a small (100–500 MB) NTFS partition. Confirm the number before typing active; setting the wrong partition active moves the problem instead of fixing it. This flag applies only to MBR disks — GPT/UEFI systems don't use it.

Step 7 — Check the disk for damage

If the error keeps coming back, check the file system and surface for damage (replace C: with the Windows drive letter shown in recovery):

chkdsk C: /f /r

A large number of bad sectors — or a drive that intermittently disappears from the BIOS — means the drive is failing. Back up immediately and replace it.

Data safety: A drive that drops out of the BIOS or shows this error intermittently may be dying — image it to a known-good external disk before running repairs. bootrec, bcdboot, and the active flag only touch boot metadata, but chkdsk /r stresses weak sectors, and a failing drive can lose data under that load. Never run format, clean, or a reinstall to "get past" this error, and never run repairs on the only copy of irreplaceable data.

GRAM tip: Once the machine boots again, plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to check the drive's SMART health (critical here, since an intermittently detected drive is often a dying one), read the event logs, and let its AI agent confirm whether the real cause was boot order, damaged boot records, or a failing disk so the error doesn't come back.

Download GRAM free See AI pricing →

FAQ

Can I fix this without a second working computer?

Often, yes. The most common causes — wrong boot order, a loose cable, or a flipped UEFI/Legacy setting — are fixed in BIOS/UEFI setup with no media at all. But note one difference from blue-screen errors: this message appears before Windows starts loading, so forcing three failed boots usually can't trigger Automatic Repair. If the boot records themselves are damaged, you'll need a Windows 10/11 install USB to reach the repair tools — any existing one works, though creating a fresh one does require a working PC. (GRAM runs inside Windows, not from boot media — its role comes once the machine boots again: verifying disk health and confirming the root cause.)

Does "Operating system not found" mean my hard drive is dead?

Not necessarily. First check whether BIOS/UEFI setup detects the drive. If it's detected, the drive is almost certainly fine and the problem is boot order, a BIOS-mode mismatch, or damaged boot records — all fixable with the steps above. If the drive is missing from the BIOS even after reseating its cables, then it's a hardware problem: the drive, cable, or port has failed, and data recovery should come before anything else.

Will bootrec or marking a partition active erase my files?

No. bootrec and bcdboot rewrite only boot metadata, and the active flag is a single bit in the partition table — none of them touch your data. The real risks are selecting the wrong partition in diskpart, or running chkdsk /r on a drive that's already failing. If the data is irreplaceable, image the drive first.

Why did this appear right after a BIOS reset or motherboard swap?

A CMOS reset or new board often comes up with different firmware defaults: the boot mode may flip between UEFI and Legacy/CSM, and the boot order resets. A GPT disk is invisible to Legacy boot, and an MBR disk is invisible to pure UEFI boot — so a perfectly healthy Windows install "disappears." Check the disk's partition style with diskpart (Step 3) and set the firmware mode to match; don't rebuild boot records until the mode is right.