MBR or GPT Corruption: No Boot? Fix It

If your PC shows “No bootable device” or similar after MBR or GPT corruption, the fix is to repair the boot records or rebuild the partition table, not to immediately reinstall Windows. This article explains how to diagnose and repair both MBR and GPT boot corruption, what causes it, and how to prevent it.

What MBR and GPT Are

MBR (Master Boot Record) and GPT (GUID Partition Table) are two ways to store partition information on a drive. MBR is the older standard, introduced in 1983, and works with BIOS and UEFI systems (using CSM). It supports drives up to 2 TB and a maximum of four primary partitions. GPT is the newer standard, part of the UEFI specification, supporting drives larger than 2 TB and up to 128 partitions. Modern Windows, macOS, and Linux all support both, but GPT is required for UEFI boot on 64-bit Windows.

When you see a boot failure, the problem is often not the partition table itself but the boot code stored in the first sector (MBR) or the EFI System Partition (ESP) on a GPT disk. Corruption can happen from power loss during writes, improper shutdown, malware, or accidental deletion of boot files.

How Boot Corruption Manifests

Typical error messages include:

• “No bootable device — insert boot disk and press any key”
• “Bootmgr is missing” (MBR systems)
• “An operating system wasn’t found”
• “Reboot and Select proper Boot device”
• “The boot configuration data for your PC is missing or contains errors” (BCD error)

These errors appear before Windows loads, so you cannot access the desktop. The system may still show the BIOS/UEFI screen, which confirms the hardware is fine.

Diagnosing the Corruption

First, determine if the drive is even detected. Enter your BIOS/UEFI (usually by pressing Del, F2, F10, or Esc during startup) and check the storage section. If the drive appears, the issue is likely boot records, not a dead disk. If it doesn’t appear, check cables (SATA power and data) or try another port.

If the drive is detected, boot from a Windows installation USB (created with Media Creation Tool) and choose “Repair your computer” instead of “Install now.” Then open Command Prompt from Troubleshoot > Advanced Options. From there, you can run tools to inspect and repair.

For MBR disks, run bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, and bootrec /rebuildbcd. For GPT disks, the BCD store lives on the EFI System Partition, and you may need to assign it a letter and rebuild the store manually. A common command sequence is:

1. diskpart
2. list disk then select disk 0 (your system disk)
3. list partition and find the EFI partition (usually 100 MB, type System)
4. select partition 1 then assign letter=S
5. Exit diskpart and run bcdboot C:\Windows /s S: /f UEFI

If the partition table itself is damaged (e.g., you see “The partition table is invalid” or the drive shows as unallocated), you may need to rebuild it with tools like TestDisk, which can recover lost partitions by scanning the disk. This is more complex and should be done carefully to avoid further data loss.

Common Causes and Prevention

Corruption rarely happens without a trigger. Common causes include:

• Power failure during a disk write (especially while updating boot files)
• Forced shutdowns (holding the power button)
• Malware that targets the boot sector (e.g., bootkits)
• Accidentally deleting the EFI partition or formatting it
• Using disk management tools incorrectly (e.g., shrinking the system partition too far)
• Dual-boot setups where one OS overwrites the other’s boot loader

To reduce risk, use a UPS for desktops, always shut down properly, keep antivirus updated, and back up your boot configuration. Tools like Macrium Reflect or built-in Windows System Image Backup can create a full image of the system partition, allowing quick restore.

MBR vs GPT: Which One Should You Use?

If you are reinstalling Windows, choose GPT if your motherboard supports UEFI (most since 2012). GPT is more robust, has CRC32 checksums for partition entries, and supports unlimited partitions (Windows caps at 128). MBR is only needed for very old 32-bit systems or when you must boot in legacy BIOS mode. Windows 11 requires GPT and UEFI, so if you plan to upgrade, GPT is the only option.

Converting between MBR and GPT without data loss is possible with tools like mbr2gpt (built into Windows 10/11) if the disk has no more than three primary partitions and is not a dynamic disk. The tool converts the partition table and updates the firmware boot mode automatically. Always back up before converting.

Data Recovery and Backup Strategies

If boot corruption prevents access to your files, you can still recover data by booting from a Linux live USB (e.g., Ubuntu) and mounting the Windows partition. This works even if Windows boot files are gone, as long as the partition itself is intact. Copy important files to an external drive before attempting repairs.

For partition table corruption, TestDisk can often rebuild the table by scanning for actual partition boundaries. It is free and open source. If the disk has physical issues (clicking, not spinning), stop using it immediately and seek professional recovery, as further attempts can worsen the damage.

Regular backups are the only real safety net. Use File History for personal files, and create a system image after installing Windows and all updates. Store backups on a separate physical drive or cloud service.

Frequently Asked Questions

Can I repair MBR corruption without reinstalling Windows?

Yes, in most cases. Using the Windows Recovery Environment’s Command Prompt, you can run bootrec commands to fix the MBR, rebuild the BCD, and restore boot files. This works if the partition structure is intact. If the partition table itself is damaged, you may need TestDisk, but that is still possible without a full reinstall.

What is the difference between “Bootmgr is missing” and “No bootable device”?

“Bootmgr is missing” appears when the MBR is found but the boot manager file (bootmgr) is missing or corrupted. “No bootable device” means the BIOS/UEFI cannot find any valid boot sector or EFI partition at all. The former is easier to fix with bootrec; the latter may indicate a dead drive or a completely wiped partition table.

Does GPT corruption affect data on other partitions?

Not necessarily. If only the boot files are corrupted, your data partitions remain untouched. If the GPT itself is corrupted, the entire disk may appear unallocated, but the data is still there until overwritten. Tools like TestDisk can often recover the partition table and make data accessible again.

How do I know if my system uses MBR or GPT?

Open Disk Management (right-click Start > Disk Management), right-click the disk (e.g., Disk 0), and select Properties. Under the Volumes tab, look at “Partition style.” It will say either “Master Boot Record (MBR)” or “GUID Partition Table (GPT).” Alternatively, in Command Prompt, run diskpart, then list disk; GPT disks have an asterisk (*) under the GPT column.

Is it safe to convert MBR to GPT on a working system?

Yes, with the built-in mbr2gpt tool, but you must meet conditions: the disk must have fewer than four primary partitions, and the system must support UEFI. The tool converts without data loss, but it does change the firmware boot mode. Always back up first, and ensure your firmware is set to UEFI mode before running it.

What should I do if bootrec /fixboot says “Access is denied”?

This often happens on GPT systems because the EFI partition is not mounted. You need to assign a drive letter to the EFI partition using diskpart, then run bcdboot C:\Windows /s S: /f UEFI (replacing S: with your assigned letter). If that fails, check that the partition is formatted as FAT32, which is required for EFI.

Related

• Best Steam Multiplayer Games: Top Picks
• Bronze vs Cast Iron Cannons: Corrosion Resistance
• MPEG Compression Artifacts: Causes and Real Fixes