GPT partition error: causes, MBR differences and solutions

When you're installing Windows and the message "Windows cannot be installed on this disk. The selected disk has a GPT partition style" appears, it's normal to panic a little: the wizard won't let you continue, you can see your disks and partitions, but it won't allow you to proceed with the installation. The good news is that this is a very common problem and there are several clear solutions.

This message appears because your computer's boot mode and disk partitioning type are incompatible . For years, Windows has supported two partitioning styles (MBR and GPT) and two boot modes (Legacy BIOS and UEFI). Errors such as "The selected disk has a GPT partition style" or "The selected disk has an MBR partition table" occur when these two systems are not aligned.

What does the error “the selected disk has the GPT partition style” mean?

The message indicates that you are trying to install Windows on a disk configured as GPT while your computer has booted into Legacy BIOS mode . The installer detects that the disk and boot method are incompatible and, for security reasons, blocks the installation.

GPT (GUID Partition Table) is a modern partitioning scheme linked to the UEFI standard . It's the norm in current computers: motherboards with UEFI firmware designed to boot from GPT disks, especially those with large storage capacity.

In contrast to GPT is MBR (Master Boot Record), a classic partitioning format, older and with several technical limitations : it only supports disks up to 2 TB and a maximum of four primary partitions, unless an extended partition with logical drives is used.

When you see the message “Windows cannot be installed on this disk. The selected disk has a GPT partition style” during installation, it means that Windows is launching the installer in BIOS/Legacy mode but is encountering a disk configured for UEFI . The reverse is also true: if you boot in UEFI and the disk is MBR, you will see the message “The selected disk has an MBR partition table. On EFI systems, Windows can only be installed on GPT disks.”

Furthermore, a more complex scenario can occur: attempting to restore a backup made on a GPT disk to a disk that previously had an MBR partition table . In this situation, the GPT table can overwrite the previous information and cause errors when creating or extending partitions, leaving confusing messages in Disk Management and blocking operations.

Key differences between MBR and GPT and their relationship to UEFI/BIOS

To understand why this error occurs, it's essential to understand how partition styles (MBR/GPT) and firmware boot modes (BIOS/UEFI) work . Both elements must be coordinated, or the system won't boot and the Windows installer will complain.

On an MBR disk, the boot information and partition table are stored in the disk's starting sector (Master Boot Record) . This design dates back decades and was intended for small disks. Out of the box, it only allows four primary partitions; if you want more, you have to create an extended partition and, within it, logical partitions. Furthermore, it cannot handle more than 2 TB : any space above that limit is wasted.

GPT, on the other hand, is part of the UEFI standard and was designed precisely to overcome the limitations of MBR and offer greater robustness against errors . It allows for a very high theoretical number of partitions (Windows supports up to 128 without needing an extended partition) and manages very large disks, of several terabytes, without problems. It also replicates the partition table at the beginning and end of the disk and stores backups and checksums, which greatly increases the possibility of recovering the disk if there is corruption in the table.

The other piece of the puzzle is the motherboard firmware. This is where UEFI and the older Legacy BIOS come into play . In practical terms:

• BIOS/Legacy + MBR: classic combination; older equipment only supports this pairing.
• UEFI + GPT: modern pair; it is the one they recommend for Windows 8, 8.1, 10 and 11 on current hardware.
• UEFI with Compatibility Module (CSM): allows booting MBR disks on UEFI motherboards by activating "Legacy", "CSM" or similar options.

If you boot the Windows installer in BIOS mode and the disk is GPT, you'll get a message that the selected disk has the GPT partition style . If you boot it in pure UEFI mode and the disk is MBR, you'll see the opposite message about the MBR partition table. The logic is always the same: the boot mode and partition type must match.

General options for fixing the error

When you encounter this warning during Windows installation, you actually have two possible paths to unlock the situation , depending on whether you want to keep the current partitions or are willing to reformat the disk.

The first option, and the most recommended for most modern computers, is to adapt the installation medium (the bootable USB drive) to UEFI/GPT mode . In practice, this means creating an installation USB drive configured as GPT and booting the PC in UEFI mode to respect the current disk partitioning scheme.

The second option involves changing the disk partitioning style, switching from GPT to MBR or vice versa (see Converting an MBR disk to GPT ). This can be done in several ways: using the Diskpart command-line tool from the Windows installer itself, using third-party programs that allow lossless conversions, or completely formatting the drive and recreating the partition table.

If you decide to reformat with Diskpart, you must be very clear that all partitions will be erased and all data lost . Therefore, when there is important information, software like EaseUS Partition Master or AOMEI Partition Assistant comes into play, allowing you to convert between GPT and MBR while trying to preserve the disk's contents.

Create a bootable USB drive in GPT format using Rufus (recommended solution)

On modern computers, the most sensible approach is to keep the disk formatted as GPT and properly prepare the installation USB drive to boot in UEFI mode . This way, you take full advantage of GPT and avoid the hassle of modifying the disk's partition table.

For this purpose, one of the most convenient tools is Rufus. Unlike the official Windows Media Creation Tool, which doesn't always allow you to properly control the USB partition scheme , Rufus lets you explicitly choose whether you want a USB drive prepared for GPT/UEFI or MBR/BIOS.

The usual process is this: first you get a Windows ISO image (for example, by downloading it with the Media Creation Tool itself by choosing the "create installation media" option and saving a Windows 10 or 11 ISO file, preferably 64-bit), and then you use Rufus to convert that ISO into a bootable USB drive with the appropriate format.

Once you have the ISO, connect a USB drive to your PC and run Rufus. It's preferable to use the installable version of the program because it's usually less troublesome than the portable version . Within Rufus, the key setting is choosing the correct partition scheme and target system.

• Select your USB drive in the device section.
• Click on "To select" to specify the Windows ISO image you downloaded.
• In “Partition scheme” you choose GPT.
• In “Target System” you choose UEFI (not CSM).
• Leave the rest of the options at their default settings, unless you have specific needs, and click on “Start”.

When Rufus finishes, you'll have a USB drive ready to boot in UEFI mode. Now you need to tell your motherboard to prioritize booting from that USB drive . On many computers, you can display a quick boot menu at startup by pressing keys like F8, F12, ESC, or a specific F key, depending on the manufacturer.

If you prefer to leave it permanently set, you can enter the UEFI settings (usually by pressing Delete, F2, or another key at startup) and set the USB drive as the first boot device. Either way, the goal is for the system to boot from the USB drive in UEFI mode , so the installer recognizes the GPT disk and allows you to continue without displaying the error.

Convert a GPT disk to MBR using Diskpart during installation

If for any reason you're not interested in or can't create a GPT/UEFI USB drive, there's the alternative of converting the disk from GPT to MBR directly from the Windows installer . It's a drastic method, but also very effective when you want to maintain a legacy/MBR environment.

The major drawback is obvious: Diskpart conversion involves completely wiping the disk . All partitions and all content will be deleted, so it's advisable to have previously backed up anything you don't want to lose (either to another internal drive, an external HDD/SSD, or the cloud).

To use Diskpart from within Windows installation, when you're on the initial wizard screen, you can open the command prompt by pressing Shift + F10 . If that combination doesn't work, you can always go back in the wizard to the initial window, click on "Repair your computer ," go to "Troubleshoot," and choose "Command Prompt . "

With the command window open, the typical procedure for converting a GPT disk to MBR by full reformatting is as follows:

1. Type diskpart and press Enter to launch the tool.

2. Run `list disk` to see all connected disks. You'll see which drive is GPT because an asterisk appears in the corresponding column. It's very important to make sure you select the correct disk number to avoid accidentally removing another drive.

3. Select the disk to convert with select disk X , replacing X with the actual disk number where you want to install Windows.

4. Clean the entire partition structure with the clean command . This step erases everything on that disk, with no way back.

5. Next, run convert mbr to make the drive adopt the MBR style.

When you're finished, type `exit` to quit Diskpart and close the console. Back in the installation wizard, you can refresh the list of disks and partitions: the disk will appear as a single unallocated space. Select that space and continue with the installation as usual , letting the installer create the necessary partitions.

If you opened the command prompt from the recovery options instead of from the installation wizard itself, you may need to restart your computer and restart the installer for it to detect the changes correctly.

BIOS/UEFI settings to use MBR or GPT disks

When you choose to work with MBR on a modern computer, simply converting the disk isn't enough: you must ensure that the BIOS/UEFI is configured to boot in a mode compatible with that partition type. Otherwise, the system will install, but then it won't boot.

Motherboards with UEFI firmware typically have sections like "Boot," "Startup," or "Startup." Within these, you'll find boot mode options , where you can select between pure UEFI, Legacy/CSM, or a combination of both. Each manufacturer uses its own terminology: "Compatibility Support Module (CSM)," "Boot MBR Legacy," "Legacy Only," "UEFI and Legacy," and similar terms.

If your disk is MBR and you want to be able to boot from it, you'll need to enable Legacy or mixed (UEFI + Legacy) compatibility mode . If, on the other hand, you choose to keep the disk GPT, it's best to use pure UEFI or, at least, ensure that UEFI is enabled.

The key to enter the BIOS/UEFI also varies depending on the brand: on many desktop computers it's Delete or F2, while on laptops it might be F1, F10, Esc, or others. If you're unsure which key to use or where to find the option , it's best to consult your motherboard manual or search for the exact model on the manufacturer's website.

Using third-party software to convert GPT↔MBR without losing data

It's not always advisable to format the disk when you see a message indicating that the selected disk has a GPT partition style . If you have a lot of important data and want to minimize risks, there are specialized partition management programs that allow you to convert between GPT and MBR while attempting to preserve all your data.

One example is EaseUS Partition Master, which includes a built-in disk converter . The general workflow involves opening the program, going to the "Disk Converter" section, and choosing "Convert GPT to MBR." Then, you select the disk to convert, click "Convert," and the software takes care of modifying the partition table.

The main advantage is that, according to the manufacturer, all data should remain intact during the process . Even so, it is highly recommended to make a backup beforehand because any conversion of this type involves some risk, especially if the disk already had bad sectors or had suffered errors previously.

Another widely used program is AOMEI Partition Assistant Professional. This tool also allows you to convert from GPT to MBR and from MBR to GPT without erasing the disk's contents , and offers additional features such as drive cloning, partition resizing, and bootable media creation.

When the computer doesn't have Windows installed and you can't run the program from within the system itself, AOMEI offers the option of creating a bootable USB drive with its environment . This USB drive is prepared on another working computer, the problematic computer is booted from the USB drive, and once AOMEI has loaded, the disk is selected and the "Convert to MBR disk" or "Convert to GPT disk" option is chosen, depending on the need.

After applying the changes and restarting, the disk will have changed its partition style and you can try installing Windows again, always remembering to adjust the boot mode (UEFI or Legacy) in the BIOS/UEFI to be consistent with the type of disk chosen.

“GPT protective partition” and data recovery with TestDisk

Another GPT-related scenario that often catches many users off guard is the "GPT protective partition" message in Windows Disk Management. In these cases, the system recognizes the disk, but doesn't allow assigning a drive letter or accessing the data, and sometimes even displays an incorrect capacity (for example, marking a 512 GB disk as if it were 2 TB).

This behavior usually indicates that the GPT partition table is damaged or inconsistent . The disk may have suffered a mechanical failure, a sudden shutdown during access, a controller problem, or some type of logical corruption, and Windows, instead of mounting the partitions, displays this "protective partition" status.

If the problem is purely mechanical (for example, stuck read/write heads or mild overheating), tricks like gently cooling the disk for a few minutes (not freezing it) have sometimes been suggested to try and get it working enough to read it one last time. However, these kinds of maneuvers are delicate and offer no guarantees; whenever important data is involved, the best course of action is to use a professional repair service.

When the damage is primarily logical, a very useful tool is TestDisk. It's a free program that runs on Windows and Linux, specifically designed to analyze and repair partition tables . A common way to use it with problematic GPT disks is to boot a Linux system in live mode (for example, Ubuntu from a USB drive), download TestDisk, run it, and let it perform a deep disk analysis.

In the case of GPT, within TestDisk you typically select the affected disk, indicate that the partition type is EFI-GPT, and run a scan. After a quick scan, the program displays all detected partitions, both active and deleted . Those marked with the letter "D" appear as deleted and in gray, while active primary partitions are shown in green.

The interesting thing is that you can navigate with the arrow keys and change the status of the partitions: from "D" deleted to "P" primary, making them valid again. It's common to have several small entries corresponding to recovery or system partitions; the one that really matters is usually the one that occupies most of the disk and contains your data.

Before writing anything to the disk, TestDisk lets you press the "P" key to list the files on the selected partition. If you see your folders and documents, you have several options: you can either copy those files directly to another drive (the program allows this, although on a live USB you need to carefully check the destination path), or you can trust that the overall structure is correct and proceed to write the new partition table using the "Write" option.

Upon confirmation, TestDisk rewrites the GPT table consistent with the partitions you've marked in green. After restarting, the disk should be accessible again from the file explorer of a system like Ubuntu live or even Windows, provided there's no serious physical damage. Keep in mind that after this type of repair, Windows might not boot correctly from that disk, but the important thing is to be able to recover your data first.

Reverse cases: error “the selected disk has an MBR partition table”

The opposite problem to the one we're discussing occurs when the computer boots the installer in UEFI mode and the disk is partitioned as MBR . In that situation, the typical message is "Windows cannot be installed on this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed on GPT disks."

Again, the root cause is the same: the boot mode doesn't match the partition type . Here too you have two options: either change the boot mode to Legacy/CSM in the BIOS/UEFI so the installer can work with MBR, or convert the disk to GPT to adapt it to the current UEFI environment.

If you want to stick with MBR because your hardware is old or for compatibility with other systems, you can create a bootable USB drive in MBR format. Tools like the Windows Media Creation Tool allow you to directly mount an installation USB drive; you can also use Rufus by selecting "MBR" as the partition scheme within the program.

The other scenario is that you might prefer to convert the disk to GPT and take full advantage of modern UEFI booting . Diskpart also allows you to perform this conversion from within the Windows installation environment itself, following a very similar sequence to the one explained earlier, but using the `convert gpt` command instead of `convert mbr`. Again, using `clean` will erase all partitions, so a backup is essential if you don't want to risk losing your data.

On relatively new machines, where the UEFI firmware doesn't offer a pure Legacy mode or BIOS support is very limited, the only realistic solution is usually to convert the disk to GPT and abandon the MBR scheme. This is precisely why Windows 11 requires a UEFI environment with Secure Boot and a GPT disk for standard installation.

Whichever path you choose in each case, the pattern always repeats: first, choose which boot mode you want to use (UEFI or Legacy) and adjust the disk type (GPT or MBR) to match . Once both elements are aligned, the "Windows cannot be installed on this disk" messages disappear, and the installation proceeds normally.

With all that said, it is clear that understanding how GPT, MBR, UEFI and BIOS are related, along with the available tools (Rufus, Diskpart, TestDisk and third-party partition managers), allows you to confidently deal with any warning that the selected disk has the GPT or MBR partition style , whether to install Windows without problems or to recover a disk that seemed lost.