Repair “BOOTMGR is missing” when the wrong MBR partition is Active

On a BIOS/MBR Windows installation, firmware starts the selected physical disk and the disk's boot code continues from a primary partition marked Active. If a data, recovery, OEM, or other non-system partition is Active instead of the real Windows system partition, the computer can stop at BOOTMGR is missing even though the Windows volume is intact.

This writeup does not require the reader to know or guess a firmware mode. It detects the on-disk partition style. The Active flag is relevant only after DiskPart proves that the intended Windows disk is a basic MBR disk. If the disk has an asterisk in DiskPart's GPT column, stop: a UEFI/GPT installation uses an EFI System Partition and firmware boot entry, not an MBR Active flag.

This is primarily a Windows 10 legacy-BIOS repair. Supported Windows 11 systems require UEFI and Secure Boot capability, so a legacy MBR Windows 11 installation is outside the normal supported Windows 11 layout. An MBR disk is necessary for this repair but does not itself prove that the computer still exposes a BIOS/CSM-compatible boot path; do not change firmware settings to manufacture one.

Searchable Windows error codes and exact messages

If a Windows Recovery code appears, search the complete code together with the displayed file, such as \Boot\BCD or \Windows\System32\winload.exe. Do not convert every BCD code into an Active-partition diagnosis.

Use this procedure when all of the following are true:

• the computer contains a verified Windows 10 installation, or a legacy Windows 11 installation whose unsupported-layout implications are accepted;
• the Windows disk is consistently detected;
• DiskPart proves that the Windows disk is a basic MBR disk, not GPT;
• a different primary partition on that same disk is currently marked Active;
• the intended Windows system partition can be identified from its contents and role; and
• the visible symptom is BOOTMGR is missing, an operating-system-not-found message, or a boot result that changes when the intended physical disk is selected.

The intended system partition can be a separate NTFS System Reserved partition or the Windows partition itself. Do not assume that every MBR installation has a separate System Reserved partition.

Do not use this procedure on a GPT disk, an EFI System Partition, a dynamic disk, removable media, or a disk whose partition style is unknown. Do not use it when the Windows disk disappears, reports I/O errors, contains a damaged partition table, or has no unambiguous Windows installation.

It also does not apply when the only demonstrated defect is damaged MBR/volume boot code, missing boot files on an already-correct Active partition, a wrong physical disk first in firmware boot order, a missing UEFI entry, a deleted EFI System Partition, or a controller-mode change. A multiboot computer whose non-Windows boot manager intentionally owns the Active partition requires a multiboot-specific plan; marking that partition inactive can remove access to every installed operating system.

Stop if firmware no longer offers the documented legacy/CSM disk-boot path. The existence of an MBR disk does not authorize switching a working UEFI configuration to legacy mode.

The exact Windows build, the utility or event that changed the flag, and the date the original system partition was created may remain unknown.

The following may not remain unknown before a write:

• the Windows volume and its physical disk number;
• whether that disk is basic MBR rather than GPT or dynamic;
• every currently Active partition on the intended disk;
• the exact partition proposed as the system partition;
• whether the proposed system partition is separate from or identical to the Windows volume;
• whether another boot manager intentionally uses the current Active partition; and
• whether a readable BCD store exists and has been copied before BCDBoot is used.

The computer's marketing name for its firmware mode is not required. The detected partition style controls this procedure.

• Windows Recovery Environment or current Windows 10/11 installation media
• Administrative Command Prompt
• A consistently detected basic MBR Windows disk
• A verified backup of important files
• A record or photograph of list disk, list volume, list partition, and every relevant detail partition result
• An unused temporary drive letter for the verified Windows volume and, when separate, the system partition
• Space on the Windows volume or a healthy external volume for copies of the readable BCD and boot files
• The original physical-disk boot order and Active flags recorded before changes
• Other bootable internal disks isolated when that can be done safely, or an unambiguous disk model/size/number mapping when they cannot be disconnected

Do not proceed if a qualified backup cannot be made and the partition roles are ambiguous.

Disconnect external hard disks, memory cards, optical discs, and unrelated USB storage. Keep only the keyboard, display, recovery media, and any healthy evidence/backup destination that is deliberately being used. If the computer has other internal bootable disks, disconnect them only when the device can be serviced safely; otherwise record their model, size, disk number, and boot order so the Windows disk cannot be confused with them.

Enter Troubleshoot > Advanced options > Command Prompt. Do not change legacy/UEFI mode, Secure Boot, storage-controller mode, or the partition layout. Do not run clean, convert, create, delete, format, or set id.

This procedure uses W: for the detected Windows volume and S: for a separate intended system partition. Before either assignment, list volume must show that the letter is unused. If the Windows volume itself is the intended system partition, use W: for both roles and do not assign S:.

1. Photograph the complete startup message. Record whether BOOTMGR is missing appears immediately after the manufacturer screen or whether Windows Recovery displays a numeric code and file path.

2. Open DiskPart and inspect without changing the layout:

   diskpart
   list disk
   list volume
   

3. Locate the already-identified Windows volume by its size, file system, label if useful, and contents. Confirm that W: is unused, select that volume, and assign the letter:

   select volume <Windows-volume-number>
   detail volume
   assign letter=W
   detail volume
   exit
   

   Stop if the assignment fails or the second detail display no longer describes the intended volume.

4. Verify the installation rather than relying on the label:

   dir W:\Windows\System32\Config\SYSTEM
   dir W:\Windows\System32\winload.exe
   

   A BIOS/MBR Windows loader normally uses winload.exe. If only a different installation is found, stop and correct the volume identification.

5. Map the Windows volume back to its physical disk and inspect that disk:

   diskpart
   select volume <Windows-volume-number>
   detail volume
   select disk <Windows-disk-number>
   detail disk
   list partition
   

6. Examine the GPT column from list disk:

   • If the intended Windows disk has a * in the GPT column, exit DiskPart and stop. Route the case to the UEFI/EFI System Partition procedure.
   • If the disk is dynamic, removable, read-only for an unexplained reason, or not the disk containing W:, stop.
   • Continue only for the verified fixed, basic MBR disk.

7. For every primary partition on that disk, select it and record its detail output:

   select partition <partition-number>
   detail partition
   

   Record which partition or partitions say Active: Yes. Do not type active or inactive yet.

8. Identify the intended system partition from evidence, not size alone:

   • A separate standard system partition is an NTFS primary partition on the same MBR disk, often labelled System Reserved, that contains \bootmgr and \Boot\BCD.
   • On an installation without a separate system partition, the verified Windows partition W: can contain \bootmgr and \Boot\BCD and serve both roles.
   • A recovery or OEM tools partition can also be small and NTFS. Its size or position does not make it the system partition.
   • A data partition containing only user files is not a Windows system partition.

9. If the proposed system partition is separate from W:, confirm from list volume that S: is unused, assign it, and inspect it:

   select partition <proposed-system-partition-number>
   detail partition
   assign letter=S
   detail partition
   exit
   

   Then run:

   dir /a S:\
   dir /a S:\Boot
   dir /a S:\Boot\BCD
   dir /a S:\bootmgr
   

   If the Windows volume is also the proposed system partition, use the same commands with W:.

10. Inspect the currently Active but allegedly wrong partition. Assign an unused temporary letter only when necessary, then list its root and boot directory. A recovery partition, data partition, or OEM tools partition that is Active but lacks Windows BIOS boot files supports the diagnosis. If it contains GRUB, another operating system's boot manager, or a deliberately configured multiboot chain, stop.

11. Establish the practical evidence threshold. Proceed only when at least two independent facts agree, for example:

    • DiskPart proves the disk is MBR and the current Active partition is a recovery/data partition;
    • the proposed system partition contains a readable \Boot\BCD and \bootmgr for this Windows installation;
    • the Windows volume itself is the only viable primary system volume and the current Active partition cannot start Windows; or
    • a documented clone/restore operation changed the Active flag and the before/after layout confirms the intended partition.

12. Check the relevant NTFS volumes without repair switches:

    Separate system partition:

    chkdsk W:
    chkdsk S:
    

    Combined Windows/system partition:

    chkdsk W:
    

    Stop if either check reports I/O failures, a RAW file system, unreadable metadata, or an unstable disk. Active-flag repair is not a substitute for storage recovery.

13. Preserve every readable BIOS BCD store before BCDBoot changes it. For a separate system partition:

    md W:\BootRepairBackup\BP004
    copy S:\Boot\BCD W:\BootRepairBackup\BP004\BCD-before-BP004
    copy S:\bootmgr W:\BootRepairBackup\BP004\bootmgr-before-BP004
    bcdedit /store S:\Boot\BCD /enum all /v > W:\BootRepairBackup\BP004\bcd-before-BP004.txt
    

    For a combined Windows/system partition, replace S: with W:. If a file is missing, the relevant copy or enumeration will fail; record that result. Do not claim a backup exists when the source file could not be read.

14. Review the readable BCD, when present. The Windows loader entry for this BIOS installation should resolve to the verified Windows volume, use \Windows\System32\winload.exe, and specify \Windows as systemroot. If the store points to a different Windows installation, stop and use the BCD-specific procedure.

Choose one branch. The ordered flag change marks the proven correct partition Active before marking the old partition inactive, but it is not transactional: interruption between writes can leave multiple Active partitions and an indeterminate boot target. Keep stable power, verify every write, and remain in WinRE until exactly one intended partition is Active.

Branch A — The intended system partition already contains a readable, correct BCD and BOOTMGR

1. Reconfirm the Windows disk number, correct system partition number, and currently wrong Active partition number from the recorded DiskPart output.

2. Mark the correct partition Active first:

   diskpart
   select disk <Windows-disk-number>
   select partition <correct-system-partition-number>
   detail partition
   active
   detail partition
   

3. Continue only if the second detail display identifies the same partition and reports Active: Yes.

4. Select the previously Active wrong partition, verify it again, and mark it inactive:

   select partition <previously-wrong-active-partition-number>
   detail partition
   inactive
   detail partition
   

5. Continue only if the final detail display identifies the intended old partition and reports Active: No.

6. Before leaving DiskPart, enumerate every primary partition on the verified disk again. Select and run detail partition for each primary partition, then require exactly one intended Windows system partition to report Active: Yes:

   list partition
   select partition <first-primary-partition-number>
   detail partition
   select partition <next-primary-partition-number>
   detail partition
   exit
   

   Repeat the select/detail pair for every primary partition. If none or more than one is Active, restore the recorded flags and stop in WinRE.

7. Remove only the drive letters that this procedure assigned temporarily. Reidentify every volume by its recorded volume number and details before removal; do not remove a letter that existed before the procedure:

   diskpart
   list volume
   select volume <separate-system-volume-number-if-S-was-assigned>
   detail volume
   remove letter=S
   select volume <Windows-volume-number>
   detail volume
   remove letter=W
   exit
   

   Omit the S: lines when the Windows volume is also the system partition. Also remove any other letter assigned temporarily to inspect the former Active partition, using its recorded volume number and letter.

8. Shut down, remove the recovery media, and use the one-time boot menu to select the verified physical Windows disk once. Do not change firmware mode or controller mode.

9. If Windows starts, complete section 12. If a BCD code replaces BOOTMGR is missing, the Active selection now reaches Boot Manager and the remaining defect is BCD-specific; follow the displayed code rather than repeating the flag change.

Branch B — The intended system partition is proven, but its BIOS boot files are missing or unusable

1. Use this branch only when the Windows installation, MBR disk, and exact intended system partition are unambiguous, storage is stable, and any readable old BCD has been copied.

2. If the intended system partition is separate, provision BIOS boot files explicitly to S::

   bcdboot W:\Windows /s S: /f BIOS /v
   

   If the Windows volume itself is the intended system partition, use:

   bcdboot W:\Windows /s W: /f BIOS /v
   

3. Require the message Boot files successfully created. If BCDBoot reports Failure when attempting to copy boot files, do not change either Active flag. Recheck the letters, NTFS status, free space, Windows source, and disk stability.

4. Verify the files and new store. For a separate system partition:

   dir /a S:\bootmgr
   dir /a S:\Boot\BCD
   bcdedit /store S:\Boot\BCD /enum all /v
   

   For a combined partition, replace S: with W:.

5. Confirm that the loader uses \Windows\System32\winload.exe, device and osdevice resolve to the verified Windows installation, and systemroot is \Windows. Stop if BCDBoot created an entry for the wrong installation or if multiple installations remain ambiguous.

6. Mark the correct partition Active first, then the previously wrong partition inactive, enumerate all primary partitions, and remove only the temporarily assigned letters using the exact verification and cleanup sequence in Branch A.

7. Shut down, remove recovery media, select the verified physical disk from the one-time boot menu, and test once.

Branch C — The current Active partition belongs to a deliberate multiboot configuration

1. Make no Active-flag change.

2. Preserve the current partition map, boot-manager configuration, and every readable BCD store.

3. Decide which boot manager is intended to own the first stage. Repair that multiboot chain or reinstall its loader using its supported procedure.

4. If Windows Boot Manager is meant to become the sole first-stage loader, plan the change with a tested way to restore the other operating system's entry. This consumer Windows-only procedure is not sufficient for that conversion.

Branch D — The disk is GPT, dynamic, unstable, or otherwise outside the proven MBR case

1. Exit DiskPart without a write.

2. For GPT, use the existing EFI System Partition, Windows Boot Manager entry, and UEFI BCD procedure.

3. For an unstable disk, preserve data and diagnose storage before boot repair.

4. For a dynamic or multiboot disk, escalate with the captured partition map. Do not attempt to force the active command.

Before leaving Branch C, Branch D, or any earlier stop path, remove only letters that this procedure assigned temporarily. Reidentify each volume by its recorded volume number and detail volume; never remove a pre-existing letter or change the partition itself.

• Windows starts after only the flag correction: The wrong Active partition was the operative failure. Do not rebuild BCD or rewrite boot code afterward.
• Windows starts after BCDBoot plus the flag correction: The Active selection and missing/unusable BIOS boot files were both involved. Preserve the before/after BCD evidence.
• 0xc000000f, 0xc0000098, 0xc000000e, or 0xc0000225 replaces BOOTMGR missing: Boot Manager is now being reached. Follow the exact BCD/device/file branch; do not keep toggling Active flags.
• BOOTMGR is still missing although the correct partition is Active and contains the verified files: The physical disk order, MBR/volume boot code, or readability of the system partition remains suspect. Stop before bootrec /fixmbr, bootrec /fixboot, or bootsect; those are separate writes with separate rollback requirements.
• DiskPart refuses active: The disk or partition is outside this procedure. Do not bypass the check.
• Another operating system's boot menu disappears: Reverse the Active flags as described in section 11 and restore the multiboot plan.
• The disk produces I/O errors or disappears: Stop software repair and protect the data.

• Do not mark any partition Active on a GPT disk.
• Do not select a system partition by size, label, or position alone.
• Do not mark the old partition inactive before the correct partition is verified and marked Active.
• Do not mark every primary partition Active to “see what boots.”
• Do not use clean, convert, format, delete partition, create partition, or set id.
• Do not delete the old recovery, OEM, or data partition after correcting its flag.
• Do not run bootrec /fixmbr, bootrec /fixboot, bootsect, and bootrec /rebuildbcd as a generic sequence.
• Do not change legacy/UEFI mode, Secure Boot, controller mode, and Active flags in one attempt.
• Do not use bcdedit /export from WinRE and assume that it exported the offline Windows BCD; copy and enumerate the explicit offline store.
• Do not overwrite a deliberate third-party or multiboot loader without a restoration plan.

If only the Active flags changed, reverse them in the safer order:

1. Boot to WinRE and verify the same MBR disk and partition numbers again.

2. Mark the previously Active partition Active first:

   diskpart
   select disk <Windows-disk-number>
   select partition <previously-active-partition-number>
   detail partition
   active
   detail partition
   

3. After the original partition reports Active: Yes, select the newly chosen system partition and mark it inactive:

   select partition <new-system-partition-number>
   detail partition
   inactive
   detail partition
   

4. Re-enumerate every primary partition on the verified disk before leaving DiskPart. Select and inspect each one, require exactly the original intended partition to report Active: Yes, then exit:

   list partition
   select partition <first-primary-partition-number>
   detail partition
   select partition <next-primary-partition-number>
   detail partition
   exit
   

   Repeat the select/detail pair for every primary partition. If none or more than one is Active, remain in WinRE and do not attempt to boot.

If BCDBoot changed an existing BCD store and the pre-repair copy is readable, first reidentify and remap the volumes in the current WinRE session. Letters from the earlier session are not stable:

diskpart
list disk
list volume
select volume <recorded-Windows-volume-number>
detail volume
assign letter=W
select volume <recorded-separate-system-volume-number>
detail volume
assign letter=S
exit

If an intended volume already has a verified letter in this WinRE session, leave that letter unchanged and substitute it consistently below. Otherwise, before assign, prove each proposed letter is unused; if it is occupied by another volume, choose a different unused letter. For a combined Windows/system volume, map only one verified letter. Stop unless the selected volume details, disk association, file system, and contents match the recorded volumes. Then reverify the source backup and target store before renaming anything:

dir W:\Windows\System32\Config\SYSTEM
dir W:\BootRepairBackup\BP004\BCD-before-BP004
dir S:\Boot\BCD
bcdedit /store S:\Boot\BCD /enum all /v

For a combined partition, replace both S: references with W:. Restore the BCD only to that reverified system partition. For a separate system partition:

attrib -h -s -r S:\Boot\BCD
ren S:\Boot\BCD BCD.after-BP004
copy W:\BootRepairBackup\BP004\BCD-before-BP004 S:\Boot\BCD
attrib +h +s S:\Boot\BCD

Replace S: with W: for a combined partition. Do not run these commands if the backup copy was never created or the target partition is uncertain. This is a BCD-only rollback: BCDBoot can also add or replace other boot-environment files, so restoring the BCD does not return the complete partition to its earlier state. A full BCDBoot rollback requires the preserved system-partition or disk image, even when a prior BCD existed. If BCDBoot created files where no prior store existed, leaving those files dormant on an inactive partition is safer than deleting them manually while arranging image-based recovery.

After the BCD enumeration and copy succeed, remove only the letters newly assigned in this rollback session. Reidentify the same volumes with detail volume before each removal; omit S: for the combined layout:

diskpart
list volume
select volume <recorded-separate-system-volume-number>
detail volume
remove letter=S
select volume <recorded-Windows-volume-number>
detail volume
remove letter=W
exit

• DiskPart still identifies the intended Windows disk as MBR.
• Exactly the intended BIOS system partition on that disk is Active; the proven wrong partition is inactive.
• Windows starts twice normally and completes one cold start with recovery media removed.
• The firmware selects the intended physical disk without falling through to another disk or network boot.
• bcdedit /enum all /v from running Windows shows the expected Windows loader and no unintended installation.
• If a separate system partition is used, it contains \bootmgr and \Boot\BCD and Disk Management labels that partition System. Windows terminology labels the running Windows volume Boot; those two labels can refer to different partitions.
• No 0xc000000f, 0xc0000098, 0xc000000e, or 0xc0000225 remains.
• Recovery, OEM, and data partitions remain present and unchanged except for the corrected Active flag.
• The before-repair partition map and BCD copy remain preserved.

Confidence is approximately 85% when DiskPart proves a basic MBR disk, the current Active partition is demonstrably a non-system recovery/data partition, the proposed system partition contains or successfully receives the correct BIOS boot files, and selecting the intended physical disk starts Windows after the flag correction. Confidence is approximately 75–80% when the Windows volume is the only defensible system-partition candidate but the original layout is undocumented; that can still be a practical repair, but the uncertainty must be recorded.

Stop before any write if the disk is GPT, dynamic, intermittent, read-only for an unexplained reason, or shared by an intentional multiboot loader; if the firmware has no documented legacy/CSM disk-boot path; if two partitions remain plausible; if BCDBoot targets cannot be verified; if CHKDSK reports storage I/O failure; if another internal disk may contain the actual first-stage loader; or if the next proposed action would rewrite boot code, convert the disk, create/delete/format a partition, or erase a boot manager without a recoverable image.