Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can convert an eligible Windows system disk from MBR to GPT without reinstalling Windows by using Microsoft’s built-in MBR2GPT.exe. It is designed to convert the disk without deleting its data, but the conversion is not a substitute for a backup: the disk must meet specific layout requirements, the computer must support UEFI, and you must switch the firmware to UEFI boot mode afterward.
What does converting MBR to GPT change?
MBR and GPT are partition-table formats. They describe how a disk is divided into partitions, where those partitions begin and end, and how the operating system identifies them. The conversion changes that disk-level map and the boot arrangement; it is not the same as formatting a volume or reinstalling Windows.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
AOMEI Partition Assistant PRO - Hard Drive Management - Migrating the Operating System for 2 PCs -... | $34.99 | Buy on Amazon |
Microsoft’s MBR2GPT.exe is built into supported Windows 10 and Windows 11 installations. It is intended for an attached Windows system disk and is designed to convert that disk without modifying or deleting its data. That statement describes the supported operation, not a guarantee against every unrelated hardware fault, power interruption, existing boot problem, or mistake in selecting a disk. Keep a current backup or recovery image before changing the partition table.
The conversion also changes the boot model. An MBR installation normally starts through Legacy BIOS or Compatibility Support Module (CSM) firmware. A GPT installation is intended to start through UEFI, using an EFI System Partition (ESP) and Windows Boot Manager. Converting the partition table but leaving the firmware in the old mode can leave Windows unable to start.
#1 Best Overall
- Simple and secure partition manager, disk converter, and PC optimizer
- Maximize your disk performance
- Split, extend, and merge partitions — reallocate free space, move partitions, or resize them
- Restores your system after a system crash
- License for 2 PCs, lifetime validity — no subscription
Why GPT may be needed
Microsoft Azure Support states in 2026 that MBR uses 32-bit logical block addressing, limiting the maximum addressable disk size to 2 TiB (2,199,023,255,552 bytes). GPT uses 64-bit addressing and supports disks up to 18 exabytes. Those are partition-table addressing limits, not promises about the capacity a particular computer can use. Firmware, Windows edition and version, storage controller, sector format, and the disk itself can impose lower limits.
GPT is also the partition style used with a UEFI boot path. That is why converting an existing Windows installation can be useful when preparing a computer for a UEFI-only configuration or a Windows 11 deployment. Conversion changes the partition and boot configuration; it does not itself upgrade Windows, add UEFI support to old hardware, or remove other Windows 11 requirements.
Can I convert without reinstalling Windows?
Yes, if the target is an eligible Windows system disk. MBR2GPT validates the disk, changes its partition style, creates or reuses an EFI System Partition, installs UEFI boot files, and updates the boot configuration. You do not need to erase the disk and reinstall Windows as part of this supported path.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe qualification matters. MBR2GPT cannot convert a non-system data disk. The disk must contain the Windows installation being prepared for UEFI boot and must satisfy the tool’s layout checks. If you are unsure which disk contains the running installation, stop and identify it before running a command. A wrong disk number can turn a normally safe procedure into an avoidable recovery problem.
What should I check before converting?
Check the target disk, firmware, encryption status, backup, and partition layout before you run the conversion. Validation performs many of these checks, but doing your own inventory first makes it easier to recognize the correct disk and understand a failure.
- Back up first. Make a current file backup and, preferably, a recovery image or other restorable copy of the Windows installation. Confirm that the backup can actually be accessed. Microsoft’s Azure conversion procedure takes an OS-disk snapshot before conversion. A backup is also protection against an unrelated disk, firmware, or power problem that happens during the same maintenance window.
- Confirm UEFI support. Check the computer or motherboard documentation and firmware setup. The machine must support UEFI, because the converted installation is expected to boot through UEFI. If firmware offers only Legacy BIOS, converting the disk does not create a usable modern boot path.
- Identify the correct disk and its style. In PowerShell, run
Get-Disk | ft -Auto. Record the disk number and confirm that its partition style is MBR and that it is the disk containing Windows. Do not assume that Disk 0 is always the operating-system disk, especially on systems with multiple drives. - Check BitLocker. If BitLocker is enabled, suspend protection before converting. Microsoft says a BitLocker volume can be converted while protection is suspended. Suspending is different from decrypting: it avoids leaving the volume unprotected permanently while allowing the conversion. To resume protection afterward, delete and recreate the existing protectors as Microsoft directs, then verify that protection is active.
- Review the partition layout. MBR2GPT requires no more than three primary partitions, no extended or logical partition, an active system partition, a valid default operating-system entry in the BCD store, recognized partition types, and enough room for GPT metadata. Count every partition, including recovery or vendor partitions, rather than counting only the volumes that appear in File Explorer.
- Ensure space for metadata and the ESP. The tool requires 16 KB plus 2 sectors at the front of the disk and 16 KB plus 1 sector at the end for GPT metadata. It must also be able to create or reuse an EFI System Partition. If the existing system partition is unsuitable, the tool may need to shrink the Windows partition to make room.
These checks are prerequisites, not suggestions to delete partitions pre-emptively. Do not remove a recovery, vendor, or system partition merely to make the count look lower unless you have a separately verified recovery plan and understand the consequences. Let validation identify the actual issue.
How do I run MBR2GPT?
Use an elevated Command Prompt and validate before converting. Microsoft documents offline execution from Windows PE or the Windows Recovery Environment (WinRE) as the normal route. Offline means the installed Windows system partition is not actively running the command environment, reducing the number of files and partitions in use.
- Start Windows PE or WinRE. Boot from appropriate Windows recovery or deployment media, or use the computer’s recovery environment. Open an elevated Command Prompt. If you use a recovery environment, drive letters may differ from those seen in normal Windows; the disk number is the important value for the MBR2GPT command.
- Identify the disk again. Use
Get-Disk | ft -Autowhere PowerShell is available, or use DiskPart’s read-only inventory tools, and match the disk number to the Windows installation you recorded earlier. - Validate eligibility:
mbr2gpt /validate /disk:0
Replace0with the intended system-disk number. Validation checks whether the disk meets the tool’s requirements and does not convert it. Treat a failed validation as a stop signal. - Convert only after validation succeeds:
mbr2gpt /convert /disk:0
The conversion command validates again, then performs the partition and boot changes. Leave the machine powered and undisturbed until the command reports its result. - Record the result. Note the return code and any messages. If the code is not a clean success, do not immediately repeat the command. Save the logs and resolve the reported condition first.
The documented syntax also supports /logs:<directory> to choose a log directory and /map:<source>=<destination> to map a source partition type to a destination type. The mapping option is for a particular partition-type compatibility situation; it is not a routine switch to append to every conversion. A log path is useful when you need to preserve files for troubleshooting.
Can I run it from full Windows?
Yes, Microsoft documents an option for running MBR2GPT while the full Windows installation is running. Add /allowFullOS to both validation and conversion:
mbr2gpt /validate /disk:0 /allowFullOS
mbr2gpt /convert /disk:0 /allowFullOSIn the full operating system, the existing MBR system partition is in use. MBR2GPT therefore creates a new EFI System Partition by shrinking the Windows OS partition. That is a different layout operation from the usual offline path. Use the offline route when it is available; choose /allowFullOS only when you have a reason to keep Windows running and have checked the backup and free-space situation carefully.
What does MBR2GPT do during conversion?
Microsoft describes six phases:
- Validate the disk and its partition layout.
- Create an EFI System Partition if an appropriate existing system partition cannot be reused.
- Install the UEFI boot files.
- Apply GPT metadata and the new partition layout.
- Update the BCD store so Windows Boot Manager points to the installation.
- Restore drive-letter assignments.
If the existing system partition is suitable, it may be reused. Otherwise, Microsoft creates a 100 MB EFI System Partition, or 260 MB on disks with 4K sectors, by shrinking the OS partition. The size is created by the tool; do not manually create a replacement ESP before running it unless a documented troubleshooting plan specifically calls for that.
Because this is both a partition-table and boot-configuration change, a successful conversion does not mean the computer can continue booting with its old Legacy BIOS or CSM setting. The firmware change is a required part of completing the operation.
What should I do immediately after conversion?
When MBR2GPT reports success, restart promptly, enter the firmware setup, and change the boot mode from Legacy BIOS/CSM to UEFI. Microsoft explicitly requires this reconfiguration after GPT conversion. Firmware menus differ by manufacturer, so the labels may be Boot Mode, UEFI/Legacy Boot, CSM, or a similar term.
- Restart and enter firmware setup using the key or menu specified by the computer maker.
- Change the boot mode from Legacy BIOS or CSM to UEFI. If there is a separate CSM setting, disable or turn it off as required for UEFI-only boot.
- Save the firmware change and restart.
- Choose the Windows Boot Manager entry associated with the converted disk if the firmware presents several boot choices.
- Once Windows starts, verify that the expected disk is present and that BitLocker protection has been restored if you suspended it.
If the machine does not boot, return to firmware and verify that UEFI mode is selected and that Windows Boot Manager on the converted disk is first or explicitly selected. Do not switch randomly among unrelated firmware options. Review the MBR2GPT logs before attempting another partition or boot change.
What does “MBR2GPT validation failed” mean?
It means the disk did not pass one or more eligibility checks. Validation itself does not convert the disk, so the correct response is to investigate rather than run /convert anyway.
Start with Microsoft’s stated requirements:
- The selected disk must actually be MBR and must be the Windows system disk.
- There can be no more than three primary partitions.
- There can be no extended or logical partition.
- An active system partition must exist.
- The BCD store must contain a valid default operating-system entry.
- Partition types must be recognized.
- There must be room for GPT metadata at both ends of the disk and room to create or reuse an ESP.
A validation failure can therefore reflect a partition count, an unsupported partition type, a boot-configuration problem, insufficient placement space, encryption state, or simply the wrong disk number. The exact message and log entry matter. Do not “fix” a count failure by deleting a partition until you have confirmed that the data and recovery function are backed up.
Where are the logs?
MBR2GPT writes diagerr.xml, diagwrn.xml, setupact.log, and setuperr.log. Microsoft identifies setupact.log and setuperr.log as the most detailed files for disk-layout and conversion errors. Use /logs:<directory> if you need to place the files in a known location for review or copying to another machine.
Read the logs in sequence: identify the disk and phase being processed, note the first error rather than only the final summary, and check whether the tool was validating, creating the ESP, installing boot files, applying GPT metadata, or updating BCD. This distinction prevents treating a boot-file issue as a partition-layout issue.
How should I interpret the result code?
A return code of 0 means conversion completed successfully. Code 100 means conversion succeeded but some boot-configuration entries could not be restored. Treat code 100 as a boot-repair task: inspect the logs, verify the Windows Boot Manager entry in firmware, and make sure the expected Windows installation is selected.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Other return codes identify categories such as cancellation, invalid parameters, layout failure, encryption, EFI-partition creation failure, boot-file installation failure, or GPT-application failure. The number alone is not a repair recipe. Use the detailed log files to determine which phase failed, then correct that condition before trying again.
Can I convert a data disk with MBR2GPT?
No. MBR2GPT is for a Windows system disk and cannot convert a non-system data disk. Do not apply the OS-disk commands to an external, secondary, or removable disk containing files you want to keep.
Microsoft’s Azure procedure for a data disk is destructive: back up the contents, use DiskPart clean and convert gpt, recreate and format a partition, and restore the data. In outline, the workflow is to verify the backup, select the correct disk, erase its existing partition information, convert the now-empty disk to GPT, create and format a new volume, assign access as needed, and copy the data back. Because clean erases the disk’s partition information, this is a backup-and-recreate process, not an in-place conversion.
That distinction also answers the external-drive question. A USB drive or secondary storage disk should not be treated as a supported MBR2GPT target merely because it is attached to Windows. Use a destructive data-disk workflow only after you have a verified copy and have positively identified the disk; otherwise leave its partition style unchanged.
Which conversion approach fits my disk?
The first decision is whether the disk is the attached Windows system disk. The second is whether you can work offline. The third is whether encryption and the partition layout meet the requirements.
| Situation | Approach | Important condition |
|---|---|---|
| Attached Windows system disk | Run MBR2GPT validation, then conversion | Requires an eligible MBR layout and UEFI-capable firmware; switch firmware to UEFI afterward. |
| System disk with an offline environment available | Run from Windows PE or WinRE | This is Microsoft’s normal documented execution path and avoids the in-use MBR system partition. |
| System disk while full Windows must remain running | Add /allowFullOS to both commands |
The tool creates the ESP by shrinking the OS partition because the existing system partition is in use. |
| BitLocker-protected system disk | Suspend protection, convert, then restore protection | Microsoft permits conversion while protection is suspended; recreate the existing protectors when resuming. |
| Non-system data disk | Back up, erase and recreate as GPT, then restore | MBR2GPT cannot convert it; DiskPart clean makes this destructive. |
Common mistakes to avoid
- Skipping validation. The conversion command validates again, but running it as a first experiment makes a preventable failure harder to diagnose.
- Using the wrong disk number. Disk numbers can differ between normal Windows and WinRE. Recheck the inventory in the environment where you will run the command.
- Changing firmware too early. Switch to UEFI after a successful conversion and restart, not before the MBR2GPT operation has completed.
- Leaving BitLocker protection active. Suspend it first and plan how you will recreate protectors and verify protection afterward.
- Assuming every partition counts as a simple primary volume. Extended, logical, recovery, and vendor partitions affect eligibility. Read the layout instead of relying on File Explorer.
- Trying to convert a data disk in place. MBR2GPT is not a general-purpose data-disk converter. The supported data-disk process erases and restores.
- Repeating a failed conversion without reading logs. A failure may concern BCD, encryption, ESP creation, boot-file installation, or GPT application. The remedy depends on the phase.
Frequently asked questions
Frequently Asked Questions
Does converting to GPT make a hard drive faster?
No performance improvement is promised. The conversion changes the partition-table format and boot arrangement. Choose GPT for UEFI booting or partition-size needs, not as a speed upgrade.
Can I switch from Legacy BIOS to UEFI without reinstalling Windows?
For an eligible Windows system disk, yes. Run MBR2GPT, restart after it succeeds, and change the firmware from Legacy BIOS or CSM to UEFI. The disk layout and boot files must meet the tool’s requirements.
How do I convert an MBR disk for Windows 11?
On a supported Windows 10 or Windows 11 installation, use the same MBR2GPT validation and conversion procedure for the system disk, then boot it in UEFI mode. Conversion does not itself install Windows 11 or satisfy other hardware and software requirements.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesWill converting MBR to GPT erase my files?
Microsoft describes MBR2GPT as converting the system disk without modifying or deleting its data. Nevertheless, it changes partition and boot configuration, so make and verify a current backup or recovery image before starting.
Can I use MBR2GPT on an external USB drive?
The documented procedure is for an attached Windows system disk, and MBR2GPT cannot convert a non-system data disk. Do not treat a removable or secondary USB drive as a supported target for these commands.
What does return code 100 mean?
Conversion completed, but some boot-configuration entries could not be restored. Inspect setupact.log and setuperr.log, verify the Windows Boot Manager entry in UEFI firmware, and treat the remaining work as boot-configuration repair.
What if my disk has four primary partitions?
The documented eligibility limit is no more than three primary partitions, with no extended or logical partition. Validation can fail until the layout meets that requirement. Do not delete a partition without a verified backup and a clear recovery plan.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →How much space does the EFI System Partition need?
If MBR2GPT cannot reuse a suitable system partition, Microsoft says it creates a 100 MB ESP, or 260 MB on a 4K-sector disk, usually by shrinking the OS partition in the full-OS path.
Where can I find MBR2GPT error details?
The tool writes diagerr.xml, diagwrn.xml, setupact.log, and setuperr.log. The setup and error logs are the most detailed; use /logs:<directory> to choose where they are stored.
What should I do if Windows will not boot after conversion?
Enter firmware setup, confirm UEFI mode is enabled, and select the Windows Boot Manager entry on the converted disk. Then review the MBR2GPT logs before making another change. Do not return to Legacy mode as a substitute for diagnosing the converted boot path.
Can GPT hold a disk larger than 2 TiB?
GPT’s 64-bit addressing supports disks up to 18 exabytes, while Microsoft Azure Support gives MBR’s 32-bit LBA limit as 2 TiB (2,199,023,255,552 bytes). Actual usable capacity still depends on the computer, firmware, operating system, controller, and disk.
Recommended Free Tools
Do I need to decrypt BitLocker first?
Microsoft says a BitLocker volume can be converted while protection is suspended, so full decryption is not the stated requirement. Suspend protection before conversion, then delete and recreate the existing protectors to resume it afterward.
The Bottom Line
For an eligible Windows system disk, Microsoft’s MBR2GPT can change MBR to GPT without reinstalling Windows or intentionally deleting the disk’s data. Back up first, confirm UEFI support and the disk layout, suspend BitLocker, validate before converting, and use the logs for any failure. After a successful conversion, restart and explicitly switch firmware from Legacy BIOS/CSM to UEFI. For a non-system data disk, do not use MBR2GPT: back up the files, erase and recreate the disk as GPT, then restore the data.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
