How to Repair a Broken Master Boot Record (MBR) or EFI Partition

Few Windows problems feel as absolute as a machine that no longer boots.

When that happens, people start collecting commands very quickly.
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
bcdboot C:\Windows

The dangerous part is not that these commands exist.
The dangerous part is that they often get passed around as one universal recipe, even though Windows startup repairs usually split into two different stories:

• older BIOS-style systems with MBR-style boot repair;
• newer UEFI systems with an EFI System Partition and BCD boot files.

That distinction is what finally made this topic feel manageable to me.

Start with WinRE and Startup Repair before you start typing repair commands

Microsoft’s current guidance is clear about the first move: use the Windows Recovery Environment, then try Startup Repair.

Microsoft describes Startup Repair as a built-in recovery tool that runs from WinRE, scans the machine for common startup issues, and tries to repair them automatically. The official support article specifically lists problems such as corrupted boot configuration data, damaged system files, and even a damaged MBR among the issues it can attempt to fix.

I think this matters because people often skip directly to command-line repair out of panic. But the calmer order is better:

1. get into WinRE;
2. run Startup Repair;
3. only move to manual repair if the automatic path does not resolve it.

That order is not just tidier. It is safer. You let Windows try the least destructive built-in recovery path first before deciding that the bootloader itself needs manual intervention.

The big mental model is simple: MBR and EFI are not the same repair target

What confused me most when I first learned this topic was that many tutorials mix all boot failures into one bag. Microsoft’s current documentation makes the split much easier to understand.

In the boot-issues troubleshooting article, Microsoft treats one class of problems as boot-loader damage and lists symptoms such as:

• Boot Configuration Data (BCD) missing or corrupted
• Boot file or MBR corrupted
• Boot sector missing or corrupted
• Bootmgr missing or corrupted

But Microsoft’s BCDBoot documentation also explains something crucial: on UEFI systems, boot files live in the EFI System Partition, while on BIOS systems they are handled through the active system partition and BIOS-style boot flow.

That means the repair path depends on what kind of boot structure your machine is actually using.

My practical interpretation is this:

• if you are thinking in terms of classic MBR, master boot code, and boot sector repair, you are on the BIOS/legacy side of the story;
• if you are thinking about the EFI System Partition, firmware entries, and rebuilding boot files from C:\Windows, you are on the UEFI side of the story.

Once that clicks, the commands stop feeling interchangeable.

bootrec is the tool family for classic boot-code repair

Microsoft’s Windows boot troubleshooting article gives the clearest official sequence for the bootrec path.

For boot-code repair, Microsoft says:

• run BOOTREC /FIXMBR to repair boot codes;
• run BOOTREC /FIXBOOT to repair the boot sector;
• if the issue is BCD-related, use Bootrec /ScanOS, then export and rename the old BCD store, then run bootrec /rebuildbcd.

There is also one very important note in Microsoft’s article that people should not ignore: Fixmbr overwrites only the master boot code. If corruption affects the partition table itself, Fixmbr may not solve the issue.

That is one of the reasons I do not like oversimplified advice such as “just run /fixmbr and you’re done.”

Sometimes it helps.
Sometimes it is the right command for the wrong problem.

The emotional trap here is assuming that every boot failure is an MBR failure. On modern Windows systems, that is often not true at all.

bcdboot is the more relevant repair tool when the EFI system partition is the problem

For UEFI systems, Microsoft’s BCDBoot documentation is the more useful anchor.

Microsoft says BCDBoot is used to configure boot files and can repair a corrupted system partition by recreating the system-partition files using fresh copies from the Windows partition. Microsoft also explains that on UEFI systems, BCDBoot copies boot files either to the EFI System Partition or to the partition specified with /s, and creates the BCD store there.

That changes the way I think about EFI repair completely.

Instead of focusing first on “rewrite the MBR,” the better question becomes:

“Can Windows still see the installed OS, and can I identify the EFI system partition so I can rebuild the boot files correctly?”

Microsoft’s repair sequence for the system partition is very direct:

1. boot to a command line, such as Windows setup media with Shift+F10;
2. use diskpart and list vol to identify the Windows partition and the system partition;
3. optionally format the system partition if that is really part of the repair plan;
4. run bcdboot D:\Windows or the matching Windows path you identified in WinRE.

That last point matters a lot: in recovery mode, Windows is not always C:.
Drive letters in WinRE can shift.
So a command copied blindly from the internet can be correct in theory and wrong on the machine in front of you.

The safest way to think about the repair flow is as a decision tree

If I were describing a clean recovery mindset, it would look like this:

First, confirm you are really in startup-repair territory

Microsoft’s troubleshooting guidance also reminds us that not every black screen is a bootloader problem. If the machine is stuck in the BIOS phase or the disk is not being seen correctly, the issue may be hardware-related rather than something bootrec or bcdboot can solve.

That is a valuable reality check.

Second, let Startup Repair try the easy win

It is built for exactly this class of problem and may save you from unnecessary manual edits.

Third, separate legacy boot repair from UEFI repair

If the machine is using a BIOS-style boot path and the issue really looks like damaged boot code or BCD in that model, the bootrec commands make sense.

If the machine uses UEFI, focus on locating the EFI System Partition and rebuilding boot files with bcdboot instead of acting as though MBR repair is the universal cure.

Fourth, be careful with assumptions about partition letters and scope

The recovery console is where sloppy assumptions become expensive. The installed Windows folder might be D:\Windows, not C:\Windows. The system partition may be hidden until you identify it. A command can be syntactically valid and still target the wrong place.

That is why Microsoft keeps pushing people back toward identifying partitions first.

What usually goes wrong in real life is not the command syntax but the mental model

I think most boot-repair confusion comes from one of these mistakes:

• treating MBR and EFI as if they were the same repair scenario;
• running bootrec commands on a UEFI system without first thinking about the EFI partition;
• assuming C: is always the Windows partition in WinRE;
• skipping Startup Repair and moving straight to destructive-looking commands;
• assuming a successful command automatically means the boot path is now correct.

The last one is especially worth remembering.

A command completing without an error is not the same thing as a correct diagnosis. Boot repair is one of those areas where correct context matters more than typing confidence.

Verification note: Commands, terminology, and support details in this guide were cross-checked against Microsoft’s BCDBoot documentation.

For broader context, continue with How to Map a Network Drive in Windows for Easy File Sharing and Why Total Commander Still Has a Cult Following Among Techies.

Conclusion

Repairing a broken Windows boot path gets much less intimidating once you stop hunting for one magic command. Startup Repair in WinRE should usually be the first step because Microsoft designed it to fix many common startup failures automatically. After that, the real skill is choosing the right branch. bootrec is the classic toolset for BIOS and MBR-style boot repair. bcdboot is the more relevant tool when a UEFI system needs its EFI boot files rebuilt from the Windows installation.

That is the distinction I wish more guides led with. Not more drama, not more random command blocks, just a cleaner separation of repair targets. Once you know whether you are repairing old-style boot code or rebuilding a UEFI boot environment, the recovery process starts feeling like troubleshooting again instead of ritual.

FAQ

Should I always run bootrec /fixmbr when Windows will not boot?

No. Microsoft’s current guidance shows bootrec as part of boot-loader troubleshooting, but that does not make it universal. On many modern UEFI systems, the more relevant repair path is identifying the EFI System Partition and rebuilding boot files with bcdboot.

Why does the Windows drive letter sometimes change in recovery mode?

Because WinRE does not always assign letters the same way your normal Windows session does. That is why Microsoft’s own repair instructions tell you to use diskpart and list vol first instead of assuming the installed Windows partition is still C:.