MBR Repair on Windows 10 and 11: Fix Boot Errors Fast

Prerequisites

• A second working PC to prepare recovery media if the target machine cannot boot.
• A bootable Windows 10 or 11 USB drive or DVD. Download the official Windows Media Creation Tool from Microsoft to build one.
• Physical or remote console access to the target machine.
• BIOS/UEFI access to change the temporary boot order.
• Basic familiarity with the Windows command prompt.
• A recent backup of critical data if the disk is accessible at all.

Step 1: Boot from Windows Installation Media

Insert your bootable USB or DVD before powering on the affected machine. Enter the BIOS or UEFI firmware by pressing the appropriate key during POST — commonly F2, F12, Delete, or Esc depending on the manufacturer. Change the boot order so the USB or optical drive is listed first, save, and exit.

When the machine restarts, press any key when prompted to boot from the installation media. The Windows Setup screen appears. Select your language and keyboard layout, then click Next.

Step 2: Open the Recovery Command Prompt

Do not click Install Now. Look for the Repair your computer link in the lower-left corner and click it. This launches the Windows Recovery Environment (WinRE), where all bootrec operations run safely outside the damaged installation.

Navigate through the menus as follows:

1. Click Troubleshoot
2. Click Advanced options
3. Click Command Prompt

A command prompt window opens with elevated privileges, isolated from the damaged Windows installation.

Step 3: Repair the Master Boot Record

Start with the lightest touch. The bootrec /fixmbr command rewrites only the MBR code sector without touching the partition table. This is the correct first step when malware or corruption has overwritten the boot code. As Microsoft's bootrec documentation confirms, /fixmbr targets the boot code exclusively, leaving partition data untouched.

bootrec /fixmbr

A successful run returns: The operation completed successfully.

If a third-party bootloader replaced the boot sector of the active partition — for example, after a failed Linux dual-boot removal — follow up with:

bootrec /fixboot

This writes a fresh Windows-compatible boot sector to the active partition.

Step 4: Rebuild the Boot Configuration Data (BCD)

A healthy MBR and boot sector are not sufficient if the Boot Configuration Data store is also missing or damaged. The BCD tells the Windows Boot Manager where to find the OS loader. Without it, the system cannot start Windows even with a clean MBR.

First, scan all partitions for Windows installations:

bootrec /scanos

bootrec /scanos lists any discovered installations directly. This step is especially useful on multi-boot machines. Then rebuild the BCD to include them:

bootrec /rebuildbcd

Windows displays any identified installations and asks whether to add each one. Press `Y` then `Enter` to confirm. After a successful rebuild, type exit and restart the machine to test.

Step 5: Full BCD Reset for Persistent MBR or BOOTMGR Errors

If bootrec /rebuildbcd alone does not resolve a BOOTMGR is missing error, the BCD store itself may be too corrupted to repair incrementally. The fix: export the broken store as a backup, delete it, then force a clean rebuild.

Run each command in sequence, pressing Enter after each line:

bcdedit /export C:\BCD_Backup
C:
cd boot
attrib BCD -s -h -r
ren C:\boot\bcd bcd.old
bootrec /rebuildbcd

Here is what each line does:

• bcdedit /export saves a copy of the current BCD to C:\BCD_Backup as a safety net.
• cd boot navigates to the boot directory on the system drive.
• attrib BCD -s -h -r removes the system, hidden, and read-only attributes from the BCD file so it can be renamed.
• ren C:\boot\bcd bcd.old renames the damaged store rather than deleting it permanently.
• bootrec /rebuildbcd finds no existing BCD and builds a fresh one from scratch.

Confirm the prompt to add Windows to the boot list, then type exit and reboot.

How to Confirm the MBR Repair Worked

After the machine restarts with the installation media removed, watch for the Windows logo and the login screen. A successful repair means no boot error messages appear and Windows loads normally.

If the machine still fails to boot, check the following:

• Confirm in BIOS that the correct internal drive sits first in the boot order after removing the USB.
• Run bootrec /scanos again. A result of Total identified Windows installations: 0 points to a deeper partition table or disk failure, not an MBR issue.
• Test drive health with the manufacturer's diagnostic tool, or run chkdsk /f /r from the recovery prompt to rule out bad sectors.
• On UEFI systems with GPT disks, the standard bootrec workflow needs bcdboot commands as well, since GPT disks use an EFI System Partition rather than a traditional MBR.

Troubleshooting: What to Do If the MBR Repair Fails

Some boot failures go deeper than the MBR. SafetyDetectives notes that bootloader rootkits infect the Master Boot Record and load before the operating system — and a full OS reinstall will not remove them. If bootrec commands complete without error but the machine still refuses to boot, consider these next steps.

First, check whether Secure Boot is active. Microsoft's Security Blog documents that UEFI bootkits run at startup before the OS loads, giving them the ability to disable BitLocker, HVCI, and Microsoft Defender Antivirus. A boot failure that bootrec cannot fix may indicate firmware-level compromise rather than simple corruption.

Ransomware is another culprit. Faronics documents that families like Petya overwrite the MBR and leave the OS unbootable — and the 2017 NotPetya variant discarded the original MBR entirely, so decryption keys provided no recovery path.

If malware is suspected after bootrec repairs fail:

1. Disconnect the drive and scan it from a clean system.
2. Check the EFI System Partition for unexpected files if the machine uses UEFI.
3. Consider a bare-metal restore from a known-good backup.
4. Review MITRE ATT&CK technique T1542.003 for indicators of bootkit compromise, including unexpected files in the EFI System Partition.

For enterprise environments managing Windows endpoints at scale, the Intune: Auto-Delete Old User Profiles step-by-step guide and the Dell Management Portal for Intune integration setup guide cover complementary recovery and provisioning workflows. The Deactivate an Entra ID App Registration step-by-step guide is also useful when compromised credentials are part of a broader incident.