"BOOTMGR is Missing" Error: Don't Reinstall Windows Yet
In this article
If you see "BOOTMGR is missing. Press Ctrl+Alt+Del to restart." on a black screen, your data is almost always still safe on the drive. BOOTMGR is the Windows Boot Manager. It's a single small file that lives on the boot partition and tells the rest of Windows where to find itself. When that file is gone or corrupted, Windows can't start. The rest of your drive (your photos, documents, downloads, all the user files on C:) is sitting there untouched. The wrong move now is to grab a Windows install USB and let it "reinstall" or "format". Both of those wipe your data. The right move is to extract your files first, then fix the boot issue separately.
This guide walks through what causes "BOOTMGR is missing", how to tell if the drive is failing or just confused, the bootrec commands that sometimes fix it without data loss, and how to pull your files off via Linux or a USB enclosure when the recovery commands can't get the system back.
What BOOTMGR Actually Is
BOOTMGR (the Windows Boot Manager) is a small executable that the PC's firmware looks for very early in the boot process. On older Windows systems and machines using legacy BIOS mode, BOOTMGR lives on the "System Reserved" partition, which is the first partition on your boot drive (usually 100MB to 500MB). On newer UEFI systems, the equivalent role is filled by a file called bootmgfw.efi inside the EFI System Partition. The "BOOTMGR is missing" error usually refers to the legacy version. UEFI systems show similar errors with slightly different wording ("No bootable device", "Operating system not found", "Boot Device Not Found").
What BOOTMGR does, in one sentence: the firmware finds it, runs it, and BOOTMGR reads a configuration file (BCD, the Boot Configuration Data store) that tells Windows where the actual operating system files live. Without BOOTMGR, the firmware has no idea where Windows is. So it stops and shows the error.
The important point: BOOTMGR is one tiny file (about 380KB), and the BCD is a database the size of an Excel spreadsheet. Both live on a different partition than your personal files. When they go missing, your data hasn't gone anywhere. It just can't be loaded automatically anymore.
Why BOOTMGR Goes Missing
We see this error coming from a handful of causes. Most are software-only and don't threaten the data. A few are hardware-related and need lab attention.
1. The Boot Partition Got Marked Inactive or Damaged
Sometimes a Windows update, a system tool, or a disk-management mistake flips the active flag on the boot partition. The firmware no longer sees it as bootable. Other times a power loss during a boot writes a half-finished BCD, and the next boot can't find BOOTMGR. Both are recoverable with bootrec commands without losing data, as long as the drive is healthy.
2. Cumulative Windows Update Damaged the Boot Files
A Windows update sometimes corrupts the boot configuration if the install process gets interrupted (power loss, forced shutdown, drive going to sleep). The next boot fails because the BCD points at the wrong files or has a bad checksum. See our guide to failed Windows updates.
3. A Drive Letter Got Changed Outside of Windows
If you installed a second drive and accidentally moved or hid the System Reserved partition during disk management work, the firmware can't find BOOTMGR anymore. Easily fixed by reassigning the boot partition, but a confusing-looking error.
4. Switching Between MBR and GPT
Some users follow online guides that suggest converting MBR drives to GPT (or vice versa). If the conversion fails halfway, the boot sector is mangled. The data partitions are usually still readable, but the firmware loses track of where to find BOOTMGR.
5. Accidental Format or Deletion
People sometimes assume the "System Reserved" partition is junk and delete it. Or they format the wrong partition during a Windows install. Both situations remove BOOTMGR. Both are fixable in principle, but if you've deleted the partition entirely, the data on the C: partition may still be intact even though boot doesn't work.
6. The Drive Is Failing
The scariest cause. A hard drive or SSD that's developing bad sectors can produce "BOOTMGR is missing" intermittently. Today it boots. Tomorrow the sectors that hold BOOTMGR aren't readable, so the firmware reports it as missing. The data partition might still mostly read, but the drive is dying. We see this on older spinning hard drives and on heavily-used SSDs past their endurance rating.
Is Your Data Still There?
In most "BOOTMGR is missing" cases: yes, your data is fine. Here's why.
Your personal files live on the main system partition (typically C:), which is a completely separate partition from the small System Reserved partition where BOOTMGR lives. When BOOTMGR goes missing, only the boot path breaks. C: is untouched. The error happens before Windows even tries to read your data partition.
The cases where data IS at risk:
- You ran the Windows installer and clicked "Custom install" and selected a partition to format. If you formatted C:, the data is gone in the normal sense. Lab recovery is sometimes possible but expensive.
- You ran bootrec commands repeatedly with no understanding of what they do. Bootrec /fixboot and bootrec /rebuildbcd write to the disk. On a failing drive, those writes can damage the file system.
- The drive is actually failing. If BOOTMGR is missing because of bad sectors, your C: partition probably has bad sectors too. Reading it normally may not work.
- You let an "automatic repair" tool format the drive. Some recovery USB tools will silently format the drive if the user picks the wrong option. Read every screen carefully before clicking.
What NOT to Do Right Now
This is the section most people skip. Read it. Each item below has destroyed someone's data permanently. None of these things are necessary to fix "BOOTMGR is missing".
- Boot a Windows install USB and pick "Install Windows". Even if you select "Custom" instead of upgrade, choosing a partition to install onto and formatting it wipes your data.
- Click "Reset this PC" in the Windows recovery menu. Same destructive outcome as a fresh install. Both "Keep my files" and "Remove everything" can fail and leave you with neither.
- Run diskpart and use "clean" on any drive. The clean command erases the partition table. Catastrophic on the wrong drive.
- Convert MBR to GPT (or vice versa) with mbr2gpt without imaging first. If anything goes wrong, the drive's partition layout is destroyed.
- Run chkdsk /f on a failing drive. Chkdsk on a sick drive can scramble file system metadata. Diagnose drive health first.
- Click any "auto-repair" button in random USB recovery tools. Some of them format partitions silently. If you don't know what a tool does, don't run it on the only copy of your data.
- Update the BIOS while in this state. A failed BIOS update on top of a boot issue often turns a recoverable problem into a paperweight.
The bootrec Commands and When They Work
If you've researched "BOOTMGR is missing" online for more than 30 seconds, you've seen the bootrec commands. They work in many cases. They can also damage a failing drive further. Use them only after you know the drive is healthy. The Linux rescue described below is the way to verify drive health before touching bootrec.
Getting Into the Recovery Console
You need a Windows installation USB. If you don't have one, make one on a working PC from Microsoft's official download page. Boot the broken PC from the USB. When the install screen appears, click "Next" then "Repair your computer" at the bottom-left, then "Troubleshoot", then "Command Prompt".
The Four bootrec Commands
Rewrites the Master Boot Record on the active drive. Safe if the drive is healthy. Doesn't touch user data. Useful when the MBR is corrupted (most common after a bad uninstall of dual-boot Linux).
Writes a fresh boot sector to the system partition. On Windows 10/11, this command sometimes fails with "Access is denied" because the boot partition isn't mounted. There's a workaround: run "bcdboot C:Windows /s X: /f ALL" (replacing X: with whatever letter the boot partition has).
Scans the drive for installed Windows versions. Read-only command. Safe. Tells you whether Windows is detectable at all, which is a useful diagnostic.
Rebuilds the Boot Configuration Data store. Run this if /scanos found Windows but /fixmbr and /fixboot didn't help. Prompts you to add detected installations to the BCD. Type Y to confirm.
MBR vs GPT and Why It Matters
A mismatch between the boot mode and partition layout can prevent booting. Older PCs used MBR (Master Boot Record) partitioning with a legacy BIOS. Newer PCs use GPT (GUID Partition Table) with UEFI firmware. Windows 11 requires UEFI/GPT. Windows 10 can run on either.
The "BOOTMGR is missing" error specifically belongs to legacy/MBR systems. On UEFI/GPT systems, the equivalent failure usually shows as "Boot Device Not Found" or "No Operating System Found". If you're seeing "BOOTMGR is missing" on a modern UEFI Windows 11 PC, that's a clue that something has switched the BIOS into legacy compatibility mode (CSM mode), and the firmware is now looking for a legacy boot file that isn't there.
| You're Seeing | Likely System Type | What to Try |
|---|---|---|
| "BOOTMGR is missing" | Legacy BIOS / MBR | bootrec commands or System Reserved repair |
| "Boot Device Not Found" | UEFI / GPT | Check BIOS boot order, rebuild EFI partition |
| "Operating system not found" | Either | Check drive in BIOS, then bootrec or bcdboot |
| "No bootable device" | UEFI on modern PCs | Check Secure Boot setting, drive in BIOS |
| "BOOTMGR is missing" on a Windows 11 PC | UEFI accidentally in CSM/legacy mode | Enter BIOS, disable CSM, re-enable UEFI boot |
If your machine was working in UEFI mode and now shows the legacy BOOTMGR error, the BIOS settings have changed. Going into the BIOS and switching boot mode back from "Legacy" or "CSM" to "UEFI only" sometimes fixes it without anything else. Check for a "Boot Mode" or "Boot List Option" setting in the BIOS.
Boot Linux to Extract Files Before You Fix Anything
This is the safest path. You boot a small Linux operating system from a USB drive, ignore the broken Windows install entirely, and copy your files off to a second USB drive. None of the broken Windows install gets touched. You can then do whatever boot repair you want afterward, knowing your files are safe.
On a working PC, download Ubuntu 24.04 LTS from ubuntu.com/download/desktop. Get balenaEtcher or Rufus to write the ISO to an 8GB or larger USB drive. This makes a USB that boots a complete operating system without installing anything.
Plug the USB into the broken PC. Power it on. Hit the boot menu key as soon as the manufacturer logo shows (F12 for Dell/Lenovo/Acer, F11 for HP, F9 for some HP, Esc for others, F8 for older PCs). Select the USB. Choose "Try Ubuntu" (not Install Ubuntu).
Open a terminal (Ctrl+Alt+T). Run `lsblk` to list drives. Your internal drive is `/dev/sda` for SATA or `/dev/nvme0n1` for NVMe. Run `sudo smartctl -a /dev/sda` (substitute the right device name). Look for "Reallocated_Sector_Ct", "Pending_Sector", "Offline_Uncorrectable", or NVMe critical warnings. Anything above zero on those fields means the drive is failing.
Open the Files application. Look for a partition that has Windows folders (it's usually labeled "Windows" or has a Windows logo icon). Click to mount. Navigate to Users, your username. Plug in a separate USB drive with enough free space. Copy Documents, Desktop, Downloads, Pictures, Videos, and Music to the external drive. If you want browser bookmarks, copy AppData/Local/Google/Chrome/User Data or AppData/Roaming/Mozilla/Firefox/Profiles.
Unplug the external drive. Plug it into a working PC. Open it. Open a few files (a photo, a document). Make sure they open. Only after verification should you go back to trying to fix the broken PC. Now if anything goes wrong with bootrec or a reinstall, your data is safe somewhere else.
Pull the Drive and Read It in a USB Dock
If you can't get the broken PC to boot from a USB (some BIOSes are locked down, some Secure Boot settings refuse external boot), you can physically remove the drive and connect it to a working PC via a USB enclosure or dock.
What You Need
- A small Phillips screwdriver (and maybe a Torx T5 for some laptops)
- The right enclosure for your drive type:
- 2.5" SATA SSD or HDD: any 2.5" SATA-to-USB enclosure ($15)
- 3.5" desktop HDD: a 3.5" SATA dock with its own power adapter ($30)
- M.2 NVMe SSD: an NVMe-to-USB enclosure ($20)
- A working computer to read the drive on
The Process
Power off the PC completely. Unplug the power cable. Open the case (laptop bottom or desktop side panel). Locate the drive. For laptops, it's usually a 2.5" SATA SSD held by a few screws and a cable, or an M.2 NVMe SSD held by a single screw on the motherboard. Remove the drive. Place it in the enclosure or dock. Connect the dock to a working PC.
If the drive is healthy and not BitLocker-encrypted, Windows on the working PC will see it as an external drive and let you browse the files normally. Copy what you want to keep, then put the drive back in the original PC and fix the boot issue from there. If Windows says "You need to format the disk before you can use it", DO NOT click Format. That means the file system is damaged and lab recovery is needed.
When BOOTMGR Means the Drive Is Actually Failing
The unhappy version of this story. A drive with developing bad sectors will sometimes throw "BOOTMGR is missing" because the sectors containing BOOTMGR have just become unreadable. Today the boot fails. Tomorrow the directory entries fail to read. Next week the entire drive is unreliable. The pattern below tells you when you're in this category.
- You hear clicking, beeping, or grinding from the drive (only applies to spinning hard drives, not SSDs)
- The BIOS sometimes sees the drive, sometimes doesn't (intermittent detection is a hardware sign)
- SMART data shows reallocated sectors above zero (run from Linux Live USB with smartctl)
- The PC takes a very long time to POST (the BIOS is waiting for the drive to respond)
- You used to see "Windows is checking disk for errors" frequently before this failure (the system was already finding bad sectors)
- The drive is more than 5 years old and used daily (especially spinning hard drives in laptops)
If any of these match, stop attempting boot. Each power cycle on a failing drive can be the one that finishes it. Either send it to a lab, or pull the drive immediately and connect it to a working PC via USB to copy what you can while it still works. Our BSOD-from-failing-drive guide covers more warning signs.
Inside the Lab: How We Handle "BOOTMGR is Missing"
When a BOOTMGR case arrives at MDrepairs, here's roughly what happens. Exact steps vary by drive type and condition.
Intake and Drive Health Check
First we connect the drive (or laptop) to a hardware imager that monitors current draw, head behavior on spinning drives, and SMART data. We do this before any read attempt. A drive that's drawing weird current at idle, or has SMART reporting hundreds of pending sectors, tells us to slow down and use specialized tools rather than treating it as healthy.
Sector-Level Imaging
We make a sector-by-sector copy to a separate disk in our lab. For healthy drives, that's a quick copy. For failing drives, we use slow-read settings that give the drive time to respond on questionable sectors. We never work on the original after imaging is done. If the original dies during recovery, we have everything we read up to that point.
Boot File Rebuild on the Image
Once we have a clean image, we mount it as a virtual disk. We can then run the equivalent of bootrec on the imaged copy without any risk to the original. If the boot files are recoverable, we extract a working virtual machine. If they're not, we just pull the user data directly from the imaged C: partition and skip the boot fix entirely.
NTFS Reconstruction When Needed
Sometimes the same damage that destroyed BOOTMGR also damaged parts of the NTFS file system on C:. We rebuild the Master File Table from its backup copies, then walk the directory tree to find every recoverable file. More on our general recovery process.
Returning the Files
We hand back the recovered data on a USB drive or external HDD that we send to you (or you provide one when you ship the drive in). The data is organized by what it was on the original drive: Documents, Pictures, Videos, Downloads, plus AppData if you wanted browser and email data. You then copy it to a new PC or restored Windows install.
How Much Does BOOTMGR Recovery Cost?
Cost depends on whether the drive is healthy. If it's just a software issue, you can usually do it yourself for free with the Linux rescue. If the drive is failing or the file system is damaged, lab pricing kicks in.
| Scenario | Typical Cost | Why |
|---|---|---|
| You did the Linux rescue yourself | $0 to $50 | Just USB drive + external drive cost |
| Lab fix on a healthy drive (logical recovery) | $1,000 to $1,500 | Imaging plus boot file rebuild |
| File system reconstruction on damaged NTFS | $1,000 to $1,500 | Master File Table rebuild from backups |
| Failing HDD with bad sectors | $1,000 to $3,000+ | Slow imaging, head clean room work if needed |
| Failing SSD with controller issues | $1,000 to $2,000+ | Possible chip-level recovery |
| BitLocker-encrypted with key | $1,000 to $1,500 | Extra decryption step |
The $100 diagnostic is credited toward a successful recovery and is non-refundable once diagnostics start. Approved donor or parts charges are non-refundable once ordered, even if recovery fails. You approve the estimate before recovery work starts. Full pricing guide covers other recovery scenarios.
Stop This From Happening Again
BOOTMGR errors don't have to be a one-way trip. There are a few habits that keep the data safe even when the boot blows up.
Run an Image-Based Backup Once a Week
Macrium Reflect Free, Acronis, Veeam Agent for Windows, or the built-in Windows Backup. Any of them. The important thing is that the backup contains the entire drive (boot files included) not just user files. With an image backup, a BOOTMGR error is a 10-minute fix instead of a multi-day ordeal: you restore the image to the drive or to a new drive and you're back.
Keep Documents on OneDrive or Equivalent Cloud Sync
Not as a backup (a sync isn't a backup), but as a redundancy. If your Documents folder syncs to OneDrive, you can access your files from any web browser even when the local PC is broken. That alone takes most of the panic out of a boot failure.
Don't Mess With Disk Management Unless You Know What You're Doing
The Disk Management tool in Windows is powerful and unforgiving. People accidentally mark the wrong partition active, delete System Reserved, or convert formats and lose data. If you're not 100% sure what a button does, don't click it.
Replace Hard Drives Before They Die
Spinning hard drives have a finite life. Most start failing somewhere between 3 and 7 years. Run CrystalDiskInfo monthly. When you see "Caution" instead of "Good", buy a new drive and clone the old one before it gets worse. Cheap insurance.
Don't Install Windows Updates on a Drive That's Almost Full
Updates need free space. A drive that's at 98% capacity is a candidate for a failed update mid-install, which is a common path to a BOOTMGR error. Keep at least 20GB free on C: at all times. More if the system has a small SSD.
FAQ
Does running bootrec /fixmbr erase my data?
No, not by itself. /fixmbr rewrites only the Master Boot Record on track zero of the drive. It doesn't touch partitions, file systems, or user data. The risk is that if the drive is already failing, the write operation can put extra stress on a sick drive. On a healthy drive, it's safe.
Why does bootrec /fixboot give me "Access is denied"?
This happens on Windows 10 and 11 when the EFI System Partition isn't mounted. The workaround is to use `bcdboot C:Windows /s X: /f ALL` after assigning a temporary drive letter to the EFI partition with diskpart. If you don't know how to do that, leave it to the Linux rescue route which doesn't depend on bootrec at all.
I see "BOOTMGR is missing" but the drive shows up fine in BIOS. What does that mean?
The drive is alive electrically. The firmware can see it. The boot sector or boot files on the drive are corrupted or pointing wrong. This is almost always recoverable with bootrec or by extracting files via Linux and reinstalling Windows clean.
Can I just clone the drive to a new one and boot from the new drive?
Only if the source drive is healthy enough to clone cleanly. Standard clone tools like Macrium Reflect or Clonezilla will abort on bad sectors. If the source has any read errors, the clone will be incomplete or corrupt. Lab cloning uses specialized hardware that handles bad sectors without aborting.
I dual-booted Linux and now Windows won't boot. Help?
This is a known pattern. Removing Linux without removing GRUB leaves the bootloader confused. Booting a Windows install USB and running bootrec /fixmbr usually fixes it. Your Windows data is safe. The Linux partition can be removed afterward with Disk Management.
My BOOTMGR error came after a power outage. Is that bad?
Common cause, usually fixable. A power loss during Windows boot, update, or shutdown can leave the boot files in a half-written state. The boot config rebuild commands usually handle it. If the power outage was extreme (lightning strike directly hitting the PC), check for actual hardware damage too.
What if I have BitLocker but never set it up?
Many Windows 11 PCs enable BitLocker silently the first time a Microsoft account signs in, especially on Pro editions or on hardware that supports it. You may have it enabled without ever clicking a switch. The recovery key was uploaded to your Microsoft account automatically. Look there first at account.microsoft.com/devices/recoverykey.
Will the Linux Live USB approach work on a MacBook running Windows via Boot Camp?
Yes, though MacBook firmware is finicky. Hold Option (Alt) at startup to get the boot picker. Pick the USB. Sometimes you need to hold the keys at the right moment. The data extraction part works the same way once Linux is running.
How long does the Linux rescue actually take?
About 90 minutes if you've never done it before, 30 minutes once you know the steps. The slowest part is downloading the Ubuntu ISO (about 4GB).
Do you accept mail-in cases from outside New Jersey?
Yes. Free UPS 2nd Day Air shipping (contiguous US) — both ways, insured. How to ship a drive safely walks through packing.
What if I already started a Windows reinstall and stopped partway?
Depends on how far you got. If you formatted C:, your data is no longer accessible by normal means. Stop the PC immediately. Do not let the install finish writing the new Windows files. Power it off, pull the drive, and call a lab. Similar scenarios are covered here.
MDrepairs is an independent data recovery lab in New Jersey serving customers nationwide via mail-in. We're not affiliated with Microsoft or any drive manufacturer. We get data off broken Windows machines. That's the job.
How MDrepairs can help
Real cases like this come through our New Jersey lab every week. If you are dealing with one now, start here.
