Convert a Disk from MBR to GPT Without Data Loss

If msinfo32 shows "BIOS Mode: Legacy", enabling Secure Boot is pointless: the system is booting in compatibility mode, and that is incompatible with secure boot by definition. The cause is almost always the same — the system disk uses the old MBR scheme, while UEFI requires GPT.

The good news: Windows ships with mbr2gpt, a tool that converts the disk without deleting data. It takes a couple of minutes. The bad news: this is an operation on the partition table, and a backup here is not a formality.

AK-47 | RedlineAWP | AsiimovM4A4 | AsiimovUSP-S | Kill ConfirmedAK-47 | Slate

First check whether you need it

Win + R → msinfo32 → the BIOS Mode line:

• UEFI — the disk is already GPT, no conversion needed, the problem is elsewhere;
• Legacy — read on.

To see the layout itself: Win + X → Disk Management → right-click the disk name on the left (where it says "Disk 0") → Properties → the Volumes tab → the Partition style line.

mbr2gpt limits

The tool will refuse to run unless every condition is met:

The third item is the most common reason for a refusal: factory laptops often ship with four partitions including the vendor's recovery volume.

Step 1. Make a backup

Do not skip it. The conversion rewrites the partition table: a power failure at that moment leaves the disk without a bootloader. Copying what matters to external storage is enough — a full system image is not required.

Step 2. Validate

Open the command prompt as administrator: Start → type cmd → right-click → "Run as administrator". Then run:

mbr2gpt /validate /allowFullOS

The answer Validation completed successfully means the disk is ready for conversion.

The /allowFullOS switch is needed because the tool is designed for the recovery environment and will otherwise refuse to run inside a normal Windows session.

If validation fails, the output names the reason — most often "Disk layout validation failed" because of extra partitions.

Step 3. Convert

mbr2gpt /convert /allowFullOS

It takes ten to twenty seconds. The final line is Conversion completed successfully. Do not reboot normally: until you switch the firmware to UEFI the system will not start, because the old bootloader is gone.

Step 4. Switch the firmware to UEFI

Reboot straight into UEFI (Del or F2 at startup — the route through Windows is no longer available) and change:

1. Boot mode: Boot Mode → UEFI (instead of Legacy or UEFI+Legacy).
2. CSM (Compatibility Support Module) → Disabled.
3. Check the boot order: an entry like Windows Boot Manager should appear — put it first.
4. Save (F10).

Windows will boot as usual. Confirm it: msinfo32 → "BIOS Mode: UEFI".

Step 5. Now Secure Boot

Only now can secure boot be enabled — it becomes available in the menu where it used to be grayed out. The steps are here: enable Secure Boot.

If the system does not boot

Do not panic, the data is intact — this is about the bootloader.

1. Confirm that CSM is off in UEFI and that the boot mode is UEFI.
2. In the boot device list, pick Windows Boot Manager rather than the disk itself.
3. If the entry is missing, boot from a Windows installation USB → Repair your computer → Troubleshoot → Startup Repair.

Why this is worth doing anyway

The conversion is not a FACEIT whim. GPT removes the MBR limit on disks larger than 2 TB, keeps a backup copy of the partition table (recoverable if the primary is damaged), and is a hard requirement for Secure Boot — and therefore for the anti-cheat requirements. Windows 11 will not install without GPT at all.

Why converting beats reinstalling

The most common advice online for an MBR question is "reinstall Windows and lay the disk out again". It works, but it is needlessly expensive: you lose installed programs, settings and time, while the built-in mbr2gpt utility solves the task in minutes without touching your data.

A reinstall is justified in two cases: the system already runs badly and you were going to refresh it anyway, or mbr2gpt refused to convert the disk and the reason could not be removed. In every other situation conversion is the smaller intervention.

It helps to understand what actually changes. Conversion rewrites the partition table structure and adds a service EFI partition; the files and data partitions themselves stay where they are. This is not formatting, but it is an operation on the disk structure — which is why a backup is mandatory even when everything goes to plan.

If mbr2gpt refuses

The utility is fairly strict and declines for understandable reasons. The most frequent ones:

• Too many primary partitions. Conversion needs room for a service partition; extra partitions have to be merged or removed.
• No free space at the start or end of the disk. The service partition has nowhere to go.
• BitLocker is on. Encryption must be suspended before converting.
• The disk is not the system disk, or the OS does not match. mbr2gpt targets the system disk of the current Windows installation.

The utility writes the error text into its own log, and that log is what you read rather than the general exit code: it names the specific reason for the refusal, which tells you what to fix.

Is my data definitely safe? The built-in conversion does not touch files, but it is an operation on the disk structure, and no such operation is entirely risk-free. A backup of what matters is made beforehand — that is a rule, not paranoia.

Can I go back to MBR? Not with built-in tools without losing data. The reverse path means repartitioning the disk, which destroys its contents. So the decision is made once and deliberately.

Do I need to change anything in BIOS after converting? Yes, necessarily. A GPT disk boots only in UEFI mode, so after conversion you switch the boot mode in firmware and turn CSM off. Skip that and the system simply will not find the bootloader.

How do I check which layout the disk uses now? Disk Management shows the partition style — MBR or GPT — in the disk properties. Check the disk itself rather than a volume: one computer can hold disks laid out differently.