Technical Anshu
Tutorials Blog
💽 MBR Table Error

Selected Disk Has an MBR Partition Table Error on UEFI Systems

This is the mirror image of the famous GPT error: Setup booted correctly in modern UEFI mode, but the disk it found is still formatted in the old MBR style — usually an older drive, a disk from a previous PC, or one initialised on a Legacy machine. Windows on an EFI system installs to GPT disks only, so Setup stops. Two fixes exist, and on a modern PC one of them is almost always the right one.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute read
🎥 Watch the full fix in the video — the error on screen, the DiskPart commands and the boot mode change, step by step

The full message reads: Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disks. Translate it and it says: you arrived the modern way (UEFI), the disk is dressed the old way (MBR). Reaching a match means either dressing the PC down — booting Legacy so MBR is accepted — or dressing the disk up — converting MBR to GPT. On any PC new enough to have UEFI, and for every Windows 11 install, the disk should move, not the PC. Here is why, and how.

Windows Setup
⚠️ Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disks.
Drive 0 Partition 2 — 476.9 GB (example size)Selected
The MBR table error in full — note it names EFI systems and GPT in the same breath. Sizes shown are example values.
1

Where an MBR Disk Comes From in a Modern PC

MBR is not a fault; it is history. This disk is MBR because:

  1. It came from an older, Legacy-era PC or laptop
  2. It was initialised in an external enclosure or by an older tool that defaulted to MBR
  3. It is a smaller, older HDD or SSD that has simply never been converted
  4. Someone previously converted it to MBR to satisfy an old machine

None of these mean the drive is failing. It only means its partition style belongs to the previous generation of booting.

2

Fix A — Convert MBR to GPT at Setup (the Right Answer on Modern PCs)

Warning first, as always: conversion at Setup requires clean, which erases the entire disk — every partition and file, permanently. Proceed only if the disk is empty, new to you, or backed up.

  1. At the disk screen, press Shift + F10
  2. Type diskpart, then list disk — the empty Gpt column (no star) confirms this disk is MBR
  3. Type select disk 0 — verify the number against the disk's size
  4. Type clean — the erase step
  5. Type convert gpt, then exit, close Command Prompt, click Refresh, and press Next on the empty disk

Converting UP to GPT also removes MBR's limits for good: disks larger than 2 TB become fully usable, and you can have far more than four partitions.

3

Fix B — Boot in Legacy Mode Instead (Rarely the Right Answer)

The other way to a match is to restart, open the boot menu, and pick the plain (non-UEFI) entry for your USB — or enable CSM/Legacy boot in firmware. Setup then runs in Legacy mode and accepts the MBR disk unchanged, data intact.

Understand what you are accepting with this route: no Secure Boot, an MBR 2 TB ceiling, and for Windows 11, an unsupported installation — Windows 11 requires UEFI. This route exists for one honest situation: installing Windows 10 on a genuinely old disk setup you do not want to disturb. On a current PC it is a step backwards taken to avoid a five-minute conversion of an empty disk — a bad trade.

4

Already Have Windows on This MBR Disk and Want to Keep It?

A different situation deserves a different ending. If this MBR disk already contains a working Windows 10 installation with your files and programs, erasing it just to satisfy Setup is wasteful — and if you have not even installed yet, stop and think about whether a reinstall is needed at all.

If the real goal is moving that existing Windows to modern UEFI/GPT, the planned route is Microsoft's mbr2gpt tool, run from inside the working Windows (validate first: mbr2gpt /validate /disk:0 /allowFullOS), followed by switching the firmware to UEFI boot. That is a migration project with a backup made first — not something to improvise from an install screen.

🔴 Data loss warning: the quick conversion in Fix A begins with clean, which erases the entire disk — all partitions, all files, with no undo. If this MBR disk came out of another PC and holds anything you need, do not convert it at Setup. Retrieve the data first, or boot Legacy for a Windows 10 install that leaves the disk untouched.

🎥 Watch the Complete Video Guide

Watch the error and both directions of the fix on video — including the moment the MBR disk becomes GPT and Setup finally says yes.

▶️ Watch Full Video
❓ Frequently Asked Questions

Why does Windows insist on GPT for EFI systems?

UEFI firmware boots from a GPT disk's EFI System Partition, and the GPT layout is part of the UEFI specification itself. The old MBR boot process belongs to Legacy BIOS. Microsoft simply enforces the pairing the firmware standards already define: UEFI with GPT, Legacy with MBR.

My disk is 3 TB and shows only about 2 TB. Is this error related?

Yes, same root cause. MBR cannot address more than 2 TB of a disk, so the remainder is invisible and unusable. Converting the disk to GPT (after backing up, since conversion at Setup erases it) makes the full capacity available.

Can I convert MBR to GPT without erasing, from the Setup screen?

No. Inside Setup, conversion always requires an empty disk. The data-preserving MBR to GPT conversion (mbr2gpt) exists only within a running Windows and only for the system disk. At the Setup screen your data-safe option is to change the boot mode, not the disk.

This guide is based on the Technical Anshu Windows install disk error video • Stuck on any point? Ask in the video comments — you will get a reply there 🙏