MBR vs GPT: Which Partition Style and How to Convert

Every disk a PC boots from carries a small table that says where its partitions start and end, and Windows reads that table before it reads anything else. Two formats exist for it, one from 1983 and one that came with UEFI, and the old one still ships on plenty of fleets. Here's how MBR vs GPT plays out on a real disk, which one each job needs, and how to convert without reinstalling.

TL;DR: MBR is the old partition table: four primary partitions, 2 TB per disk, one copy of the table, and it only boots on legacy BIOS. GPT is the UEFI-era replacement: 128 partitions in Windows, disks far past 2 TB, a backup copy of the table with checksums, and it's the only style a UEFI PC (and so any Windows 11 PC) can boot from. New disks get GPT. An old boot disk converts in place with Microsoft's MBR2GPT tool, no data loss, as long as it passes validation and you switch the firmware to UEFI afterward. A data disk converts the blunt way: back up, wipe, convert, restore.

MBR vs GPT: What Each One Is

MBR stands for Master Boot Record. It's the first sector of the disk, 512 bytes, holding a tiny piece of boot code and a partition table with room for exactly four entries. Microsoft's own description is a table of disk locations and lengths that the firmware reads at boot to find the operating system. That table has been the same shape since the IBM PC XT.

GPT stands for GUID Partition Table. It arrived as part of the UEFI specification and fixes the parts of MBR that stopped scaling. Each partition gets a globally unique ID and a type GUID instead of a one-byte code. The table has a primary copy at the start of the disk and a backup at the end, both protected by CRC32 checksums. The first sector still holds a "protective MBR" with one partition covering the whole disk, so old tools see a full disk rather than an empty one and leave it alone.

The two styles are tied to the two firmware types. Legacy BIOS boots from MBR. UEFI boots Windows from GPT only, and the UEFI vs BIOS split is where this story starts. A UEFI machine can still read and write MBR data disks, which is why old external drives keep working on new laptops.

Where MBR Runs Out

Three limits come up in tickets, and all three are structural.

The 2 TB wall is the one that catches storage projects. MBR addresses sectors with a 32-bit number, so with 512-byte sectors the table can describe 2 TB and nothing beyond it. Put a 4 TB drive on MBR and Windows shows the rest as unallocated space you can't use. Microsoft's deployment docs put the same cap on a Windows partition on a BIOS-based PC and say tools that stretch past it aren't supported.

The four-partition limit is the one that catches conversions. Windows Setup on a BIOS machine creates three partitions (system, Windows, recovery), which leaves one slot. Add a vendor recovery partition or a second OS and the disk is full, or someone has already created an extended partition to get around it. Both states block MBR2GPT, as the conversion section explains.

The single table is the quiet one. If sector 0 gets corrupted on an MBR disk, the partition map is gone and the data behind it is intact but unreachable until a recovery tool rebuilds the table. GPT keeps a second copy at the far end of the disk and a checksum on each, so Windows can detect a damaged header and repair it from the backup.

How to Check Which Style a Disk Uses

Three ways, and the PowerShell one works across a fleet.

powershell
Get-Disk | Format-Table Number, FriendlyName, Size, PartitionStyle -AutoSize

PartitionStyle reads MBR, GPT or RAW for each disk. In Disk Management, right-click the disk number on the bottom pane, pick Properties, then the Volumes tab, and read "Partition style". In diskpart, list disk shows an asterisk in the Gpt column for GPT disks and leaves it blank for MBR. Diskpart is the one that works inside WinPE when PowerShell isn't loaded.

Check the firmware mode at the same time, because the two have to agree. System Information (msinfo32) shows "BIOS Mode" as UEFI or Legacy. The combination tells you what you're looking at: UEFI plus GPT is a modern install, Legacy plus MBR is a conversion candidate, and Legacy firmware with a GPT boot disk, or UEFI with an MBR one, won't start at all.

The conversion itself is fast once the checks pass. An r/sysadmin thread from January 2025 asked how long a 1.8 TB disk would take, and the replies agreed on seconds, with the firmware change afterward taking longer than the conversion:

Which One to Pick

The decision has four gates, and they're the same for a hard drive, an SSD and an NVMe stick. Partition style has nothing to do with speed. It's a table at the start of the disk, read once, and the drive performs the same either way.

Is it the boot disk on a UEFI PC? GPT, no choice. Windows boots UEFI only from GPT, and every PC that meets the Windows 11 requirements is UEFI. Windows Setup picks GPT on its own when it installs in UEFI mode.

Is it the boot disk on a legacy BIOS PC? MBR, also no choice. Microsoft's deployment docs say Windows doesn't support GPT on BIOS-based computers. If the hardware supports UEFI, the better move is to convert the disk and switch the firmware, covered below.

Is it a data disk over 2 TB? GPT. MBR can't address the space.

Is it a data disk that has to work in something old? MBR is the only reason left. A 32-bit Windows XP box, a media player that only reads MBR, a tool that predates GPT. For everything from Windows Vista on, GPT data disks read fine on both firmware types.

For a new SSD on a current PC, the answer is GPT every time. When Windows asks "MBR or GPT" while initialising a blank disk, that prompt is the only moment the choice is free. Picking MBR there and discovering the 2 TB cap or the four-partition limit later means a wipe, which is why the default matters.

Converting a Boot Disk With MBR2GPT

Windows ships the tool. MBR2GPT.exe sits in Windows\System32 on any supported version of Windows, and Microsoft's documentation (updated July 2026) describes it as converting a system disk from MBR to GPT "without modifying or deleting data on the disk". It only converts the system disk. For data disks it refuses, and the next section covers those.

The tool was built for WinPE, and the /allowFullOS switch lets it run from inside Windows. Running it from the full OS changes one thing: the existing system partition is in use, so the tool shrinks the OS partition and creates a fresh EFI System Partition of 100 MB (260 MB on 4K-sector disks), formatted FAT32. Validate first, then convert:

code
mbr2gpt /validate /disk:0 /allowFullOS
mbr2gpt /convert /disk:0 /allowFullOS

Before touching the disk, the tool checks that it is MBR, has at most three primary partitions, has no extended or logical partitions, has one active system partition, has a BCD store with a default OS entry, and has a little free space at both ends (16 KB plus two sectors at the front, 16 KB plus one sector at the end). Fail any check and nothing changes.

Four rules keep the conversion boring:

1. Image the disk first. The tool's own output says the changes can't be undone. The r/sysadmin reply in the thread above said the same thing in plainer words: a complete backup and a tested restore plan before you start.
2. Suspend BitLocker. An encrypted volume that isn't suspended fails with return code 6. After conversion, Microsoft says to delete and recreate the protectors. Escrow the recovery key before any of that, as the BitLocker guide walks through.
3. Switch the firmware afterward. The last line of a successful run reads "Before the new system can boot properly you need to switch the firmware to boot to UEFI mode!" Convert, reboot into firmware, set UEFI, disable CSM. Do it in that order.
4. Only on supported Windows. Offline conversion of Windows 7, 8 or 8.1 disks isn't supported. Upgrade the OS first, then convert.

Return code 0 is success. Code 7 means the layout failed validation, 6 means encryption, and 100 means the disk converted but some BCD entries didn't come back. The detail is in setupact.log and setuperr.log in %windir%, and those are different files from the Windows Setup logs in the Panther folder.

Bytes N Bits walks the same ground with a live disk, including what the two layouts look like side by side:

Converting a Data Disk

There's no in-place tool from Microsoft for a non-system disk. Microsoft's Windows Server guide (June 2025) is blunt about it: you can change a disk's partition style only when it has no partitions or volumes. The procedure is back up, wipe, convert, restore.

powershell
Get-Disk
Clear-Disk -Number 2 -RemoveData -Confirm:$false
Initialize-Disk -Number 2 -PartitionStyle GPT

The diskpart version is select disk 2, clean, convert gpt. Disk Management does it through Delete Volume on each volume, then "Convert to GPT Disk" on the disk. All three destroy the data on the disk, so the backup isn't optional.

That's the case an r/sysadmin thread from October 2024 ran into: a VM data disk at the 2 TB wall, a management rule that two directories couldn't be touched, and a question about tools. The replies pointed at MBR2GPT, which won't take a data disk, and at third-party partition managers (AOMEI Partition Assistant, EaseUS, MiniTool) that convert a data disk in place. Those work, and the thread's poster ended up using one. The restore-from-backup route is still the one to plan around, because the in-place tools carry the same "could lose everything" caveat with no vendor on the hook.

Going the other way, GPT to MBR, is the same wipe-and-initialise procedure with convert mbr, and it only makes sense for a disk under 2 TB that has to boot a legacy BIOS machine or feed an old device. A USB stick for a vendor's firmware flashback port is the usual example, which the FAT32 vs NTFS post covers from the file-system side.

When MBR2GPT Says No

Validation failures come down to a short list, and each one has a fix.

Four primary partitions. The vendor recovery partition is the usual fourth. If the recovery image is also in the Windows Recovery Environment partition that Setup created, the vendor one is dead weight: back it up, delete it in Disk Management, run validate again. The tool needs a free slot because it adds the EFI System Partition.

An extended partition. The tool rejects any disk with extended or logical partitions. Move the data off the logical drives, delete the extended partition, recreate what you need as primary partitions, and keep the count at three or fewer.

BitLocker still on. Return code 6. Suspend it (Suspend-BitLocker -MountPoint C: from an elevated prompt) and run again.

No active partition or a broken BCD. The tool needs one active system partition and a BCD store that points at an OS. bcdboot C:\Windows rebuilds the store on a disk that boots but has lost its default entry. If the system partition isn't marked active, diskpart's active command on that partition fixes it.

Not enough free space at the ends of the disk. Rare, and usually a disk that was imaged sector-by-sector from a smaller drive. Shrinking the last partition by a few megabytes clears it.

Converted, then no boot. This one isn't a validation failure, it's step three from the list above. The conversion worked and the firmware is still set to legacy. Reboot into the firmware screen, switch to UEFI, disable CSM, and the PC comes back. If the disk was moved to a machine with no UEFI support, there's no fix except moving it back.

The order matters more than the commands. The ticket that comes back is never "MBR2GPT failed"; it's "I converted and now it says no operating system found", with the firmware untouched and a backup nobody can find.

Doing It Across a Fleet

A Windows 11 project turns this from a one-off into a list. Every device that's still legacy BIOS with an MBR boot disk needs the conversion before it can take Secure Boot, and Secure Boot is on the requirements list next to TPM 2.0. Inventory first:

powershell
$fw = (Get-CimInstance -ClassName Win32_ComputerSystem).BootupState
$style = (Get-Disk | Where-Object IsBoot).PartitionStyle
$uefi = if (Test-Path HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot\State) { 'UEFI' } else { 'Legacy' }
[pscustomobject]@{ Host = $env:COMPUTERNAME; Firmware = $uefi; BootDisk = $style }

The SecureBoot\State key only exists on UEFI-booted systems, so its presence is a quick firmware check that needs no elevation. Run that across the estate and you get three buckets: UEFI plus GPT (done), Legacy plus MBR (convert), and the odd one that needs a reimage because the hardware can't do UEFI at all.

For the convert bucket, Microsoft supports running MBR2GPT from a Configuration Manager or MDT task sequence, which handles the validate, convert and firmware steps on the same reboot cycle. Dell, HP and Lenovo each ship a command-line tool that flips the firmware to UEFI from inside Windows, so the task sequence can finish without anyone pressing a key. Suspending BitLocker and re-enabling it belong in the same sequence, and the TPM 2.0 guide covers the firmware setting that usually needs turning on at the same time. OpenFrame can run the inventory script above across a client's devices and collect each machine's firmware mode and partition style into one list.

The Short Version

GPT for every new disk and every UEFI boot disk. MBR only when a legacy BIOS machine or a pre-Vista device gives you no choice. Check with Get-Disk and msinfo32 before touching anything. Convert a boot disk with mbr2gpt /validate then /convert, with an image taken, BitLocker suspended, and the firmware switched to UEFI straight after. Convert a data disk by backing it up, wiping it and initialising it as GPT. And across a fleet, inventory first, so the Windows 11 rollout starts with a list instead of a surprise.

FAQ

Is GPT faster than MBR on an SSD?

No. The partition style is a table at the start of the disk, read at boot and when a volume mounts. Read and write speed comes from the drive and the interface, not from the table. Pick GPT on an SSD because of the partition count, the size limit and UEFI boot, not for speed.

Can I convert MBR to GPT without losing data?

On a Windows boot disk, yes: MBR2GPT converts in place and Microsoft documents it as not modifying or deleting data, as long as the disk passes validation. On a data disk, Microsoft's tools need the disk emptied first, so the safe path is back up, convert, restore. Third-party partition managers convert data disks in place, with the same backup-first rule.

Does Windows 11 require GPT?

Windows 11 requires UEFI firmware with Secure Boot capability, and Windows boots in UEFI mode only from a GPT disk. So the boot disk has to be GPT. Extra data disks can stay MBR if they're under 2 TB.

Why does MBR2GPT say the disk layout validation failed?

Usually one of four reasons: the disk already has four primary partitions, it has an extended partition, there's no active system partition, or the BCD store has no default OS entry. BitLocker that isn't suspended fails separately with return code 6. The detail is in setupact.log and setuperr.log under %windir%.

Can a UEFI PC read an MBR drive?

Yes, for data. UEFI systems read and write MBR data disks without any change. What they can't do is boot Windows from one. Only the boot disk has to be GPT; everything else can be either style.