GPT Disk Partition Type Error: Fix & Meaning

The error “selected gpt formatted disk contains partition not of type” appears in Windows disk management tools when you try to install Windows or use a partitioning utility on a GPT disk that has a partition type the tool doesn’t recognize. The fix is usually to delete or convert the offending partition, but the exact steps depend on which tool you’re using and whether you need the data on that partition.

What GPT and Partition Types Are

GPT (GUID Partition Table) is a modern disk layout standard that replaces the older MBR (Master Boot Record). Every partition on a GPT disk has a globally unique identifier (GUID) that tells the operating system what the partition is for—for example, an EFI System Partition, a Microsoft Reserved Partition, or a basic data partition. Windows tools like DiskPart and the Windows Setup installer check these GUIDs to decide whether they can safely use a partition.

When you see the “partition not of type” error, it means the partition’s GUID doesn’t match any of the types the tool expects. This commonly happens with:

• Partitions created by Linux (e.g., Linux filesystem, Linux swap)
• Partitions from a Mac (Apple APFS or HFS+)
• Partitions created by third-party partitioning software that uses non-standard GUIDs
• OEM recovery or diagnostic partitions with custom GUIDs

Why the Error Occurs in Windows Setup

Windows Setup’s disk selection screen is strict: it only allows installing to a partition that it recognizes as a valid Windows partition type. If you select a GPT disk that contains any partition with an unrecognized GUID, Setup may refuse to proceed and show the error. This is a safety measure—it prevents you from accidentally overwriting data on a partition that Windows doesn’t understand.

The most common scenario is trying to install Windows on a disk that previously held Linux or was used as a secondary storage drive on a Mac. The Linux swap partition or the Apple HFS+ partition has a GUID that Windows Setup doesn’t recognize, so it blocks the entire disk.

How to Fix the Error

The safest way to fix the error depends on whether you want to keep the data on the disk. If you don’t need any data on the disk, the quickest fix is to delete all partitions and let Windows create fresh ones. If you need the data, you’ll have to back it up first or use a tool that can convert the partition type without erasing it.

Fix 1: Delete All Partitions (Data Loss)

1. Boot from the Windows installation media (USB or DVD).
2. When you reach the disk selection screen, press Shift+F10 to open Command Prompt.
3. Type diskpart and press Enter.
4. Type list disk to see all disks. Note the disk number of the problematic disk (e.g., Disk 1).
5. Type select disk 1 (replace 1 with your disk number).
6. Type clean to remove all partition information. This erases all data on the disk.
7. Close Command Prompt and refresh the disk selection screen. The disk will now show as unallocated space, and you can proceed with the installation.

Fix 2: Delete Only the Problem Partition

If you want to keep other partitions on the disk, you can delete just the unrecognized partition. In DiskPart:

1. Follow steps 1-4 above.
2. Type list partition to see partitions on the selected disk.
3. Identify the partition that is not of type (usually the one with a different file system or size).
4. Type select partition N (replace N with the partition number).
5. Type delete partition override to force deletion.
6. Exit DiskPart and refresh the screen. Windows should now allow installation on the remaining space.

Fix 3: Convert the Partition Type (No Data Loss)

If you need to keep the data on the partition, you can change its GUID to a Windows-recognized type using third-party tools like GParted or MiniTool Partition Wizard (free versions available). These tools let you change the partition type GUID without formatting. However, this is risky and may not always work if the file system itself is not NTFS or FAT32—Windows can only install to NTFS (or FAT32 for UEFI boot). If the partition is ext4 or APFS, you’ll need to back up the data and reformat.

Why the Error Appears in DiskPart or Disk Management

DiskPart’s clean command and Disk Management’s “Delete Volume” action can also trigger this error when you try to delete a partition that Windows doesn’t recognize. This is more common on disks that were partitioned by non-Windows tools. In DiskPart, you may need to use delete partition override to force deletion. In Disk Management, the option to delete may be greyed out; in that case, use DiskPart.

Common Misconceptions

One common misconception is that the error means the disk is corrupt or failing. It doesn’t—it only means the partition type GUID is not in Windows’ list. The disk itself may be perfectly healthy. Another misconception is that converting a GPT disk to MBR will fix the error. That’s not true—converting to MBR will likely erase the partition table and may not help if the underlying partition types are still unrecognized. The real issue is the partition type, not the partition table format.

How to Avoid This Error in the Future

• When dual-booting Linux and Windows, always create the Windows partitions with Windows tools, then install Linux afterwards.
• If you’re reusing a disk from a Mac, wipe it completely with a tool like DiskPart’s clean before installing Windows.
• If you’re using a third-party partitioning tool, stick to standard partition type GUIDs (e.g., for basic data, use the Microsoft basic data GUID).

Frequently Asked Questions

Will this error damage my files?

No, the error itself doesn’t damage files. It only prevents Windows from using the disk. However, if you run the clean command, it will erase all data on the disk. Always back up important data before attempting any fix.

Can I install Windows on a disk that has Linux partitions?

Yes, but you must delete the Linux partitions first (or at least the one that is causing the error). Windows Setup will not install alongside Linux partitions on the same disk without manual partitioning, and it may overwrite the boot loader. It’s safer to use separate disks for each OS.

Why does DiskPart say “The specified disk is not convertible”?

This is a different error that occurs when you try to convert a GPT disk to MBR. It usually means the disk has more than 4 partitions or contains a partition that cannot be converted. You may need to delete some partitions before converting.

Does this error appear on MBR disks?

No, MBR disks use a different partition type system (partition IDs, not GUIDs). The error specifically mentions GPT, so it only occurs on GPT disks.

Can I fix this error without losing data?

Sometimes. If the partition’s file system is NTFS or FAT32, you can change its type GUID using third-party tools without losing data. If it’s a Linux or Mac file system, you’ll need to back up the data and reformat the partition to NTFS.

Related

• Smart Failure Predicted? How AI Forecasts Breakdowns
• Choosing API Gateway Functionality for Kubernetes
• How to Reset or Wipe an ARK Survival Evolved Server