BOOTMGR Is Missing: Causes and Repair Order

When a Windows machine displays “BOOTMGR is missing” (or “BOOTMGR is missing Press Ctrl+Alt+Del to restart”) on a black screen, the firmware has found a bootable device but the Boot Manager file (bootmgr) was not located on the active system partition. This is different from a BCD error, which appears after bootmgr runs but cannot read the Boot Configuration Data. The machine has passed the POST, selected a boot device, and read the first sector of that device; the boot code in that sector looked for bootmgr on the active partition and did not find it.

Three conditions produce this message:

1. Wrong boot order – The firmware is trying to boot from a device that does not contain Windows (e.g., a USB stick left plugged in, a second hard drive, or a network boot).
2. Inactive system partition – The partition that holds bootmgr is not marked active, so the boot code looks in the wrong place.
3. Missing or corrupted bootmgr – The file is deleted, damaged, or the partition structure is broken.

Hardware failure is possible but less common. A dead disk usually produces a different message (e.g., “No bootable device”) because the firmware cannot read the disk at all. If the disk is readable enough to display this error, the disk itself is likely functional.

First: Check Boot Order and Remove External Media

Before touching any repair tool, confirm what the firmware is trying to boot. Restart the machine and enter the firmware setup (usually by pressing Del, F2, F10, or Esc during startup – the exact key appears on the first screen). Look for a “Boot Order” or “Boot Priority” list. Ensure the hard drive containing Windows is first. Remove any USB drives, external disks, or optical discs, then restart.

This step costs nothing and resolves a large share of these errors, especially on machines that recently had a USB drive inserted or a BIOS update that reset the order.

If the boot order is correct and the error persists, proceed to the next steps.

Determine Which Partition Holds bootmgr

bootmgr lives on the system partition – the small (100–500 MB) partition that also holds the Boot Configuration Data (BCD). In a typical Windows installation, this partition is separate from the C: drive and is marked active. If that partition is not active, or if bootmgr is missing from it, the error appears.

To see the partition layout, boot from Windows installation media (USB or DVD) and open a command prompt:

• Boot from the Windows installation media.
• On the first screen, press Shift+F10 to open a Command Prompt.

Then run:

diskpart
list disk

Identify the disk that contains Windows (usually Disk 0). Then select it and list partitions:

select disk 0
list partition

The output shows partitions with sizes and types. Look for a partition of about 100–500 MB marked “System” or with a type of “Primary”. That is the system partition. Note its number (e.g., Partition 1).

To see if it is active, run:

select partition 1
detail partition

The output shows “Active: Yes” or “Active: No”. If it is not active, that is the cause.

Repair Order: Least Destructive First

1. Mark the System Partition Active

If the system partition exists but is not active, marking it active is a low-risk fix that does not touch any data. This is a common cause after a disk cloning operation or a third-party partitioning tool changed the active flag.

This step changes only the partition flag. It does not delete or modify any files.

In the same diskpart session, select the system partition and type:

active

Then exit diskpart and restart the machine:

exit

If the error was due to an inactive partition, Windows should boot normally.

2. Rebuild the BCD and Repair Boot Files

The next step is to rebuild the Boot Configuration Data and copy bootmgr to the system partition. This is more invasive than changing the active flag but still does not touch user data. It rewrites the BCD store and copies boot files from the Windows installation media.

This step overwrites the existing BCD store. If the BCD contains custom entries (e.g., dual-boot configurations), they will be lost. User files on C: are not affected.

From the Command Prompt (Shift+F10), run the following commands one at a time:

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

• /fixmbr writes a new Master Boot Record to the system partition. It does not affect the partition table.
• /fixboot writes a new boot sector to the system partition.
• /scanos scans for Windows installations.
• /rebuildbcd rebuilds the BCD from the scan results.

After these, restart. If the error persists, continue.

3. Copy bootmgr Manually

If the bootmgr file is missing but the partition structure is intact, copying it from the installation media can work. This step does not modify the BCD or the partition table.

This step copies a single file. It does not delete or modify other files.

First, identify the drive letters assigned in the recovery environment. Run:

notepad

In Notepad, click File > Open, and look at the “Computer” or “This PC” view to see which drive letter corresponds to the system partition (often D: or E:) and which is the Windows drive (often C:). Close Notepad.

Then copy bootmgr from the installation media (usually the DVD or USB drive, often X:) to the system partition:

copy X:\bootmgr D:\bootmgr

Replace X: with the installation media drive letter and D: with the system partition drive letter. If the system partition is the same as the Windows drive (rare but possible), copy to that drive instead.

Restart and see if the error is gone.

4. Run Startup Repair (Automatic)

Windows installation media includes an automatic repair option that can fix boot problems. It is less precise than the manual steps but can handle cases where the manual commands fail.

Startup Repair may modify the BCD and boot files. It does not delete user files, but it can change boot configuration.

From the installation media, select Repair your computer > Troubleshoot > Advanced options > Startup Repair. Follow the prompts. This may take several minutes.

5. Check Disk for Errors

If the above steps fail, the disk may have bad sectors or file system corruption. Run a disk check on the system and Windows partitions.

chkdsk can take a long time and may report errors. It does not delete user files, but if the file system is severely damaged, it may attempt repairs that could affect data integrity. Back up important data if possible before running.

From the Command Prompt, run:

chkdsk C: /f /r

Replace C: with the Windows drive letter. Then run the same on the system partition (if different). After the check, restart.

6. Rebuild the BCD with bcdedit (Advanced)

If bootrec /rebuildbcd fails, the BCD store may be corrupted beyond automatic repair. Manual recreation is possible but requires careful steps.

This step deletes the existing BCD store and creates a new one. All boot entries are lost. User files are not affected.

From the Command Prompt, identify the Windows drive letter (e.g., C:). Then run:

bcdedit /export C:\BCD_Backup
ren C:\boot\BCD BCD.old
bootrec /rebuildbcd

The first command backs up the BCD. The second renames the old BCD (so it is not deleted, but no longer used). The third rebuilds it. Follow the prompts to add the Windows installation.

7. Reinstall Windows (Last Resort)

If all repairs fail, the system partition or boot files may be unrecoverable. Reinstalling Windows is the final option.

Reinstalling Windows erases the Windows partition (usually C:) and all user files on it. Back up data before proceeding.

Boot from installation media, select Install now, and choose Custom installation. You can delete and recreate the system partition, or install over the existing Windows (which moves old files to Windows.old).

Comparison of Causes and Fixes

What People Get Wrong About This Error

A common misdiagnosis is assuming the hard drive is dead. The error “BOOTMGR is missing” actually proves the firmware can read the disk – it found a boot sector and executed it. A dead disk would produce a different message like “No bootable device” or “Disk read error”. This mistake leads people to replace hardware unnecessarily.

Another frequent error is immediately running bootrec /fixmbr without checking the boot order or the active flag. That command can overwrite a valid MBR and, in rare cases, cause more problems if the partition table is unusual. The natural instinct is to jump to the most aggressive repair, but the least destructive steps – checking boot order and the active flag – resolve many cases with zero risk.

Also, people often confuse “BOOTMGR is missing” with a BCD error. The BCD error appears after bootmgr loads, showing “Windows failed to start” or a blue screen with a BCD code. The distinction matters because the repair steps differ: a BCD error needs BCD rebuilding, while a missing bootmgr may need a file copy or active flag change.