Missing OS After Upgrading Windows 10: Fixes

If you see a “Missing operating system” or “No bootable device” error right after upgrading to Windows 10, the upgrade likely corrupted the boot configuration or the BIOS lost the boot order. You can usually fix it by rebuilding the Boot Configuration Data (BCD) from the Windows recovery environment, or by re-selecting the correct drive in BIOS—no reinstall needed.

Why This Happens After an Upgrade

Windows 10 upgrades rewrite the boot loader on your system drive. If the process is interrupted—power loss, forced restart, or a failed driver update—the master boot record (MBR) or the EFI boot partition can end up incomplete. On older BIOS/MBR systems, the active partition flag may also get cleared. On UEFI systems, the EFI System Partition (ESP) may lose the Windows Boot Manager entry.

Another common trigger is a secondary drive. If your BIOS is set to boot from a USB or a second hard drive that contains an old boot loader, it will show “Missing operating system” even though Windows is intact on the primary drive. This is especially frequent after upgrades because the installer often changes the boot order.

How Windows 10 Boots (and Where It Breaks)

Windows 10 uses one of two boot methods:

UEFI (GPT): The firmware reads the EFI System Partition, which contains bootmgfw.efi. The BCD store is at EFI\Microsoft\Boot\BCD on that partition.
Legacy BIOS (MBR): The BIOS reads the first sector of the disk, which points to bootmgr on the active partition. The BCD store is at \Boot\BCD on the system partition.

When you see “Missing operating system,” it means the firmware found no valid boot loader. That could be a missing BCD, a corrupted bootmgr, or simply the wrong disk selected in the boot menu.

First: Check BIOS Boot Order and Secure Boot

Before doing anything complex, restart and enter your BIOS/UEFI setup (usually by pressing Del, F2, F10, or Esc during startup). Look for the Boot tab and make sure your Windows drive (the one with Windows installed) is first in the boot order. If you have multiple drives, disable or move down any USB or second hard drive. Also, if you upgraded from Windows 7 or 8, ensure that Secure Boot is disabled if your system uses legacy MBR, or enabled if it uses UEFI—mismatches cause the same error.

If the drive appears in the boot menu but still fails, move on to rebuilding the boot files.

How to Rebuild the Boot Configuration (Step-by-Step)

You need a Windows 10 installation USB or DVD. If you don’t have one, you can create it on another PC using Microsoft’s Media Creation Tool (download from the official Microsoft website). Then:

Boot from the installation media. When the Windows Setup screen appears, click Next, then Repair your computer (bottom-left corner).
Choose Troubleshoot → Advanced options → Command Prompt.
At the prompt, type diskpart, then list disk. Identify your Windows drive (usually Disk 0). Type select disk 0, then list volume. Look for the volume labeled System Reserved (MBR) or EFI (UEFI) and note its drive letter (e.g., C: or D:). Also note the Windows volume letter (often D: or E: in recovery). Exit diskpart with exit.

Now run the boot repair commands. For UEFI systems:

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

If you get an error on /fixboot saying “access denied,” you may need to manually assign a drive letter to the EFI partition. In diskpart, select the EFI volume and type assign letter=S:. Then run bcdboot C:\Windows /s S: /f UEFI (replace C: with your Windows volume letter).
For legacy MBR systems, the same bootrec commands usually work. If they don’t, run bootsect /nt60 SYS /mbr.
After the commands complete, type exit and restart without the installation media.

If the BCD was rebuilt successfully, Windows should start. If not, you may need to run sfc /scannow and chkdsk /f C: (replace C: with your Windows drive) to repair system file corruption.

Common Problems and What to Try Next

If the above doesn’t work, consider these scenarios:

Multiple drives: Unplug all other drives except the Windows one, then try booting. This eliminates the chance of the BIOS picking a stale boot loader.
Corrupted BCD: If bootrec /rebuildbcd says “Total identified Windows installations: 0”, your Windows partition may not be detected. Check that the partition is still intact with diskpart and list volume. If the volume is there but not recognized, try bootrec /scanos again.
UEFI vs. Legacy mismatch: If you upgraded from a system that used Legacy BIOS but your disk is GPT, or vice versa, the boot mode may be wrong. Enter BIOS and switch between UEFI and Legacy (CSM) modes to see which one lets you boot.
After a failed upgrade rollback: Windows 10 keeps a Windows.old folder for rollback. If the upgrade failed, you may see the error because the boot loader points to a non-existent installation. Use the same bootrec commands to force it to find the current Windows.

When You Must Reinstall (and How to Keep Your Files)

If the boot repair commands fail and you cannot access Windows, you still have options before a full wipe:

Startup Repair: In the same Advanced options menu, choose Startup Repair. It automatically fixes common boot issues.
System Restore: If you have a restore point from before the upgrade, try rolling back to it.
Reset this PC: In the recovery environment, you can choose Troubleshoot → Reset this PC → Keep my files. This reinstalls Windows while preserving your personal files (but removes installed apps).
Backup manually: If none of those work, you can boot from a Linux live USB and copy your files to an external drive, then do a clean install.

Only as a last resort should you wipe the drive. A clean install will definitely fix the boot problem, but you’ll lose installed programs and settings unless you back them up.

How to Prevent This in Future Upgrades

To avoid the same issue next time:

Back up your data before any feature update.
Ensure your system has at least 20 GB free space for the upgrade.
Disconnect unnecessary USB drives and external HDDs during the upgrade.
Keep your BIOS firmware up to date (check your motherboard manufacturer’s site).
If you use multiple drives, set the Windows drive as the first boot option in BIOS.

Frequently Asked Questions

Why does it say “Missing operating system” when Windows is still on the drive?

The BIOS is looking for a boot loader in the wrong place. This usually means the boot configuration data is corrupted, the active partition flag is missing on MBR disks, or the boot order points to a different drive. Rebuilding the BCD as described above usually resolves it.

Can I fix it without a Windows installation USB?

If you have a system repair disc or a recovery drive, that works too. Without any media, you might still access the recovery environment by pressing F11 (or the manufacturer’s key) during startup if your PC has a hidden recovery partition. If not, you’ll need to create bootable media on another computer.

Will I lose my files if I run bootrec commands?

No. The bootrec commands only rebuild boot files; they do not touch your personal data. However, if you proceed to “Reset this PC” or a clean install, you could lose files unless you choose “Keep my files” or back up first.

What’s the difference between MBR and GPT, and why does it matter?

MBR (Master Boot Record) is the older partitioning scheme, while GPT (GUID Partition Table) is newer and required for UEFI boot. Windows 10 can use either, but the boot repair commands differ slightly. If you mix them up (e.g., trying UEFI repair on an MBR disk), the fix won’t work. Check your disk type in diskpart with list disk—GPT disks have an asterisk under the Gpt column.

Should I disable Secure Boot to fix this?

Only if your Windows installation was originally done with Secure Boot off (e.g., after upgrading from Windows 7). If your system came with Windows 10 preinstalled, Secure Boot should stay on. Disabling it may allow a non-secure boot loader, but it’s not a permanent fix for a corrupted BCD.

How long does the repair take?

The bootrec commands themselves take less than a minute. The entire process, including booting from the USB and running the commands, typically takes 10–15 minutes. If you need to run chkdsk or sfc, add another 5–10 minutes.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →