Technical Anshu
Tutorials Blog
🔁 Final Step

After MBR2GPT Conversion Switch Firmware to UEFI or Windows Will Not Boot

The most common ending to an MBR2GPT story: conversion succeeds, the PC reboots into Legacy mode out of habit, and a GPT disk flatly refuses to boot that way. One firmware setting fixes it.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 5 minute read
🎥 Watch the full video — the firmware screen and the exact setting that changes are shown at the end

MBR2GPT ends its run with a warning that is easy to click past: after conversion, you must configure the firmware to boot in UEFI mode. This is not fine print. A GPT system disk can only be booted by UEFI firmware — the old Legacy/CSM path looks for boot code in the MBR, and your disk does not have a working one of those any more. This page is the switch itself, what the failure looks like if you skip it, and the verification that closes the job.

What you see if the firmware is still set to Legacy (typical messages)
No Bootable Device or: Reboot and Select proper Boot device or: a black screen with a blinking cursor

👆 These messages mean the firmware cannot find a Legacy boot path — on a freshly converted disk, that is expected until you switch modes

1

Why the PC Cannot Boot Until You Do This

Legacy booting and UEFI booting are two different handshakes. Legacy firmware reads the master boot record and chain-loads from an active partition — the world your disk just left. UEFI firmware instead reads the EFI System Partition that MBR2GPT created and starts the Windows Boot Manager from a file on it. Until the firmware is told to use the second handshake, it will keep attempting the first one and reporting, accurately, that there is nothing for it to boot.

Nothing about your data is involved in this failure. The disk is converted, Windows is intact — the doorbell is simply wired to the old door.

2

The Switch, Step by Step

  1. Restart the PC and enter firmware setup — typically Del or F2 tapped during start-up (some brands use F1, F10 or Esc). From inside Windows you can also go Settings → Recovery → Advanced startup → Restart now → Troubleshoot → UEFI Firmware Settings.
  2. Find the boot mode control. Depending on the brand it is labelled Boot Mode, UEFI/Legacy Boot, or a CSM (Compatibility Support Module) switch.
  3. Set it to UEFI (equivalently: disable CSM / Legacy support).
  4. Check the boot order shows Windows Boot Manager as an entry — that is the EFI-side name for your Windows.
  5. Save and exit — usually F10.
3

About Secure Boot

With the machine now in UEFI mode, Secure Boot can be enabled — and if this conversion was preparation for Windows 11, you will want it, since Windows 11 requires UEFI firmware with Secure Boot capability. Enable it after Windows has booted successfully once in plain UEFI mode, so that if anything complains you know which change caused it. One change at a time, even at the finish line.

4

Verify, Then Call It Done

  1. In Windows, run msinfo32. The BIOS Mode line should read UEFI.
  2. Open Disk Management, right-click the disk label → Properties → Volumes. Partition style: GUID Partition Table (GPT).
  3. Resume BitLocker if you suspended it for the conversion.

Both lines changed means the job is genuinely complete — disk converted and firmware converted.

5

If Your Firmware Has No UEFI Option at All

Then the hardware has told you the truth Microsoft's documentation starts with: the device must support UEFI before you convert. On a Legacy-only board, a GPT system disk will never boot, and the recovery route is your backup — restore the disk image you made before converting, returning the machine to its working MBR state. This is the one scenario where the backup graduates from precaution to rescue, and it is exactly why the check belongs at the start of the main guide, not in this page's hindsight.

🔴 The one-sentence version: conversion changes the disk, the firmware switch changes the PC — the job is only finished when both have happened.

🎥 Watch the Complete Conversion in the Video

The closing minutes of the video are this exact firmware screen — watch them before your reboot, not after the black screen.

▶️ Watch Full Video
❓ Frequently Asked Questions

The conversion succeeded but the PC says No Bootable Device. Is the SSD ruined?

No — this message almost always means the firmware is still in Legacy/CSM mode. Enter setup, switch the boot mode to UEFI, save, and the same disk will boot Windows normally.

Where is Windows Boot Manager in my boot order?

It appears as an entry once the firmware is in UEFI mode and can see the EFI System Partition MBR2GPT created. If the mode is UEFI but the entry is missing, re-check that the conversion truly completed successfully, and that you are looking at the disk you converted.

Should I turn on Secure Boot at the same time as the mode switch?

Do it as a separate, second step. Boot once in UEFI mode first and confirm Windows starts; then enable Secure Boot. If a problem appears, you will know which of the two changes caused it.

This guide is based on the Technical Anshu MBR to GPT conversion video • Stuck on a step? Ask in the video comments — you will get a reply 🙏