Whynotwin11

How to fix Boot Method and GPT failures with MBR2GPT

Convert a Windows system disk from MBR to GPT without reinstalling, then switch the firmware to UEFI so the Boot Method and Partition Type checks pass.

  • Updated
  • Checked against WhyNotWin11 2.7.0.0
Feature image for the guide: How to fix Boot Method and GPT failures with MBR2GPT

Two red lines in WhyNotWin11 often appear together: Boot Method shows "Legacy" and Disk Partition Type shows "GPT Not Detected". They have the same root cause. Windows was installed to boot through the old BIOS compatibility path on a disk that uses the older MBR partition layout. Windows 11 needs UEFI boot from a GPT disk.

The good news is that you do not need to reinstall Windows to fix this. Microsoft's built-in MBR2GPT tool converts the system disk from MBR to GPT while keeping your files, and a firmware setting then switches the PC to UEFI. This guide explains both steps in the safe order, with the requirements, commands and recovery options you need.

MBR, GPT, Legacy and UEFI explained

Partition styles

A disk's partition style describes how the list of partitions is stored.

FeatureMBR (Master Boot Record)GPT (GUID Partition Table)
Introduced1980sPart of the UEFI standard
Maximum disk size2 TB (with common 512-byte sectors)Far beyond current disk sizes
Primary partitionsUp to 4 (or 3 plus an extended partition)128 by default on Windows
RedundancyOne partition tablePrimary and backup tables, with checksums
Boot mode on WindowsLegacy BIOSUEFI

Firmware boot modes

  • Legacy BIOS (CSM) reads the first sector of an MBR disk and runs the code it finds there.
  • UEFI reads a small FAT32 partition called the EFI System Partition on a GPT disk and runs the Windows Boot Manager from it.

Windows on PCs requires these pairs: Legacy with MBR, or UEFI with GPT. That is why you must change both together, and in the right order.

Step 1: Confirm your current state

Boot mode

  1. Press Win + R, type msinfo32 and press Enter.
  2. Read BIOS Mode in System Summary. It shows Legacy or UEFI.

Partition style

  1. Right-click Start and choose Disk Management.
  2. Right-click Disk 0 (the label on the left, not a partition) and choose Properties.
  3. Open the Volumes tab and read Partition style.

You can also use PowerShell:

Partition style · PowerShell
Get-Disk | Select-Object Number, FriendlyName, PartitionStyle, Size

If msinfo32 already shows UEFI and the disk is GPT, the red lines in WhyNotWin11 were probably caused by missing administrator rights. Run it again and accept the UAC prompt.

Step 2: Prepare

Suspend BitLocker

From an administrator Command Prompt:

Suspend BitLocker · Command Prompt
manage-bde -protectors -disable C: -RebootCount 3

Check your firmware supports UEFI

Restart into firmware setup and look for a Boot Mode, UEFI/Legacy or CSM option. If your firmware has no UEFI support at all, the conversion will not help, because the PC could not boot from GPT.

Step 3: Understand MBR2GPT's requirements

MBR2GPT is included with Windows 10 version 1703 and later, in the System32 folder. It converts the disk in place by adding GPT structures and creating an EFI System Partition. Before converting, it checks that the disk is suitable.

The disk must meet these conditions

  • It currently uses MBR.
  • It has no more than three primary partitions, because MBR2GPT needs space for the new EFI System Partition.
  • One partition is marked active and is the system partition.
  • There are no extended or logical partitions.
  • The Windows boot configuration points to the Windows partition.
  • Every volume with a drive letter can be identified.
  • All partition types are recognised by Windows, or are mapped with the /map option.

The most common blocker

Many older installations have four partitions: a system partition, the Windows partition and one or two recovery or OEM partitions. The fourth partition makes validation fail. A recovery partition from an old Windows version can sometimes be removed safely, but only after a backup and only if you are confident about which partition it is.

Step 4: Validate the disk

Open Command Prompt as administrator and run:

Validate · Command Prompt
mbr2gpt /validate /disk:0 /allowFullOS
  • /validate checks the disk without changing anything.
  • /disk:0 selects disk 0, normally the system disk.
  • /allowFullOS lets the tool run inside full Windows. Without it, MBR2GPT expects to run from Windows PE.

A successful result reports that validation completed successfully. If it fails, read the logs described below before going further.

Step 5: Convert the disk

When validation succeeds, run:

Convert · Command Prompt
mbr2gpt /convert /disk:0 /allowFullOS

The conversion usually takes less than a minute. MBR2GPT then reminds you that the firmware must be switched to boot in UEFI mode. Do not restart into Legacy mode expecting the old setup to keep working — follow the next step instead.

Useful options

OptionPurpose
/validateCheck without changing the disk
/convertValidate and then convert
/disk:<number>Choose the disk to convert
/logs:<folder>Write logs to a folder of your choice
/map:<source>=<destination>Map an unrecognised MBR partition type to a GPT type
/allowFullOSAllow running inside full Windows

Reading the logs

By default, MBR2GPT writes setupact.log and setuperr.log to the Windows folder. Open them with Notepad and search for the word "error" to see the exact reason for a failed validation.

Step 6: Switch the firmware to UEFI

  1. Restart and enter firmware setup (often Del, F2, F10 or Esc).
  2. Find CSM, Legacy Support or Boot Mode.
  3. Disable CSM, or set Boot Mode to UEFI only.
  4. Make sure Windows Boot Manager is first in the boot order.
  5. Save and restart.

Windows should start as before. Check msinfo32 again: BIOS Mode should say UEFI.

Step 7: Finish and re-check

  1. Resume BitLocker if you suspended it (it also resumes automatically after the restart count you set).
  2. Run WhyNotWin11 as administrator.
  3. Boot Method should show UEFI and Disk Partition Type should show GPT Detected.
  4. Secure Boot will now be detected as supported. You can enable it in the firmware for full protection.

Troubleshooting

ProblemLikely causeSolution
Validation fails: too many partitionsFour primary partitions on disk 0Back up, then remove an unneeded recovery or OEM partition
Validation fails: cannot find OS partitionBoot configuration points elsewhere, or a second disk holds the system partitionCheck which disk has the active system partition; use /disk: for the right one
"No boot device" after switching to UEFIThe disk was not converted, or the wrong disk was convertedSwitch back to Legacy, confirm the disk, then convert
Black screen after disabling CSMGraphics card lacks UEFI supportUse onboard video or reset the firmware; plan a newer card
BitLocker recovery screenProtection was not suspendedEnter the recovery key; suspend before future firmware changes

Converting from Windows PE

If MBR2GPT will not run inside Windows, boot Windows PE or the Windows recovery environment and run the same commands without /allowFullOS. Technicians often prefer this, because no files are in use during the conversion.

When a clean installation is the better choice

Converting is usually the fastest route, but a clean installation of Windows 11 on a GPT disk is sometimes simpler:

  • the disk has a complex layout with extended or logical partitions;
  • the current Windows installation is slow or unstable anyway;
  • you are replacing the drive with a new SSD at the same time.

A clean installation from Windows 11 installation media in UEFI mode creates a GPT disk automatically.

What the disk looks like before and after

Understanding the layout helps you recognise what MBR2GPT has done.

Typical MBR layout before conversion

  • System Reserved partition (often 50 to 500 MB) marked active, containing boot files.
  • Windows partition (C:).
  • Sometimes a recovery partition after Windows.

Typical GPT layout after conversion

  • EFI System Partition (FAT32) holding the Windows Boot Manager, created by MBR2GPT.
  • Windows partition (C:), unchanged.
  • Recovery partition, if one existed.

Disk Management shows the new partition as an EFI System Partition, and the disk's Properties report the partition style as GUID Partition Table (GPT).

A checklist before you start

  • Full backup completed and tested.
  • BitLocker recovery key saved and protection suspended.
  • Laptop connected to mains power.
  • Firmware confirmed to offer UEFI boot.
  • Disk 0 confirmed as the disk that holds Windows.
  • No more than three partitions on that disk.
  • mbr2gpt /validate completed successfully.

A checklist after conversion

  • Firmware switched to UEFI and CSM disabled.
  • Windows Boot Manager first in the boot order.
  • msinfo32 shows BIOS Mode UEFI.
  • Disk Management shows the disk as GPT.
  • BitLocker resumed.
  • WhyNotWin11 run again: Boot Method UEFI and GPT Detected.

Why Windows 11 insists on UEFI and GPT

UEFI with GPT is not only a requirement on paper. It is the foundation for Secure Boot, which only exists in UEFI mode, and for start-up measurements recorded by the TPM. GPT also stores a backup copy of the partition table at the end of the disk and protects both copies with checksums, which makes partition information more resilient than the single table used by MBR. Moving a PC to UEFI and GPT therefore improves security and robustness, not just eligibility.

Signs the conversion worked

After switching to UEFI and starting Windows, you should see:

  • msinfo32 reports BIOS Mode UEFI;
  • Disk Management shows an EFI System Partition on the Windows disk;
  • the disk's Properties report the partition style as GUID Partition Table (GPT);
  • Secure Boot State reads Off or On rather than Unsupported;
  • WhyNotWin11 shows Boot Method UEFI and GPT Detected.

If any of these differ, check the firmware boot order and confirm the correct disk was converted.

Summary

Back up, suspend BitLocker, run mbr2gpt /validate and then /convert, switch the firmware to UEFI and confirm the result in msinfo32 and WhyNotWin11. Always convert the disk before changing the firmware. When the layout is too complex, a clean installation in UEFI mode is a reliable alternative.

Frequently asked questions

Does MBR2GPT delete my files?

No. It is designed to convert the system disk in place without deleting data. A backup is still essential in case of power loss or an unexpected disk problem.

Can I convert a second data disk with MBR2GPT?

MBR2GPT is designed for system disks. For data disks, Disk Management can convert an empty disk to GPT; converting a data disk with files on it in Disk Management requires deleting its partitions first.

Do I need Windows PE to use MBR2GPT?

No. With the /allowFullOS option it runs from Windows 10 itself.

What happens to Secure Boot after the conversion?

Once the PC boots in UEFI mode, Secure Boot becomes available. WhyNotWin11 will report it as supported, and you can enable it in the firmware.

Can I switch back to Legacy mode afterwards?

A GPT disk will not boot in Legacy mode. Keep the firmware in UEFI mode from now on.

How long does MBR2GPT take?

The conversion itself normally finishes in under a minute, because it changes partition structures rather than copying data. Preparation and the backup take much longer.

What if my PC has two disks?

Make sure you validate and convert the disk that holds Windows and its system partition. Disk Management shows which disk has the System and Boot labels. The second disk can stay MBR if it only stores data.

Can I convert a disk larger than 2 TB that currently uses MBR?

Yes. After conversion to GPT, Windows can use the full capacity of large disks, but space that was outside the MBR limit may need to be added to a partition in Disk Management.

Is MBR2GPT the same as third-party conversion tools?

It is Microsoft's own tool, included with Windows 10 version 1703 and later, and it is the method Microsoft documents for converting a Windows system disk.

Should I update the BIOS before converting?

Updating the firmware first is a good idea when an update is available, because newer firmware often improves UEFI and Secure Boot support. Install it before the conversion, following the manufacturer's instructions, and never interrupt a firmware update. After it finishes, check that your boot settings were not reset.