System Disk GPT to MBR Conversion and the Boot Problem
Converting the Windows system disk from GPT to MBR changes how the PC boots. The CSM or Legacy switch, the boot file repair, and the safe order that avoids a dead PC.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute read
🎥 Watch the full video — the BIOS change from UEFI to CSM right after the conversion is shown live
A converted data disk just works. A converted system disk very often greets you with "no bootable device" — and that is not data loss, it is a boot conversation between firmware and disk that you have only half finished. This page completes it: why UEFI Windows will not boot from an MBR disk until you change the firmware mode, what else may need repair, and the order professionals use.
After converting the Windows disk — first boot (what many users see)
⛔ No bootable device found — or the PC loops back into BIOS setup
Firmware boot modeStill set to UEFI
Disk partition style nowMBR
ResultFirmware is looking for a UEFI boot that no longer exists
The classic post-conversion screen. The Windows files are usually still on the disk — the firmware is simply knocking on the wrong door. Panel recreated from the typical firmware message.
1
Why the System Disk Is a Different Animal
UEFI firmware boots a GPT disk by loading a boot program from a special EFI System Partition. MBR disks boot the old way: the firmware (in Legacy/CSM mode) runs boot code from the start of the disk, which hands over to an active system partition holding the Windows boot files. Convert the disk's partition table and you have changed which of these handshakes must happen — while Windows itself, sitting on the disk, still expects the old one.
A data disk has no handshake at all, which is why data disks convert in minutes inside Windows and system disks demand this whole page.
2
Step One — Switch the Firmware to CSM or Legacy
This is exactly the step the video performs right after the conversion:
Restart and enter BIOS/UEFI setup (Del or F2 on most boards)
Find the boot mode setting and change UEFI to CSM (Compatibility Support Module) or Legacy — wording varies by manufacturer
Make sure the converted disk is the first boot device
Save and exit
One honest warning: some modern laptops and boards have no CSM/Legacy mode at all — they are UEFI-only. On such a machine, an MBR system disk can never boot internally, whatever you do. Check that your firmware offers CSM before converting, not after.
3
Step Two — If It Still Will Not Boot, Repair the Boot Files
Changing the partition table does not automatically give the disk a working legacy boot path. When the mode is right but Windows still refuses to start, the boot files need rebuilding:
Boot from a Windows installation USB
Choose Repair your computer → Troubleshoot → Startup Repair and let it run
If Startup Repair cannot fix it, the same recovery environment's Command Prompt can rebuild the boot configuration — the typical command is bcdboot C:\Windows /s C: /f BIOS adjusted to your drive letters, which writes BIOS-mode boot files for the converted disk
Restart and test again with the disk as first boot device
Expect this step rather than fearing it: many technicians treat boot repair as a planned part of a system-disk conversion, not a sign of failure.
4
The Supporting Details Nobody Mentions
Legacy booting needs a partition marked active — conversion and repair tools normally handle this, but a disk that "has Windows yet never starts" is often missing exactly this flag
Features tied to UEFI stop applying — Secure Boot has no role in Legacy mode, and Windows 11 treats the whole arrangement as unsupported
BitLocker-encrypted system drives must be suspended or fully decrypted before conversion, or the first boot becomes a recovery-key exercise
5
The Safe Order for a System Disk Conversion
Full disk image backup, verified
Confirm the firmware actually offers CSM/Legacy mode
Suspend or decrypt BitLocker if present
Convert with the partition tool (it restarts into pre-boot mode for the system disk)
Switch firmware to CSM/Legacy, disk first in boot order
Boot; if Windows does not start, run Startup Repair from installation media
Verify in Disk Management that the style reads MBR and all files open
🔴 Never convert a system disk on a machine you cannot afford to have down. Between the firmware switch and possible boot repair, a system-disk conversion is a planned maintenance job with a backup and install media on the desk — not a two-minute tweak between other tasks.
🎥 Watch the Complete Conversion in the Video
Every click of the conversion — checking the partition style, converting with AOMEI Partition Assistant, changing the BIOS mode and verifying the result — is shown live in the full video.
Why does Windows not boot after I converted its disk to MBR?
Because the two halves of the boot process no longer match. UEFI firmware looks for an EFI System Partition that the conversion removed from play, and the disk now needs Legacy/CSM booting plus BIOS-style boot files. Switch the firmware to CSM/Legacy first; if Windows still does not start, rebuild the boot files from Windows installation media using Startup Repair.
My laptop BIOS has no Legacy or CSM option. Can I still use an MBR system disk?
No — a UEFI-only machine cannot boot an MBR system disk internally, and no conversion tool changes the firmware's abilities. On such hardware the Windows disk must stay GPT; use MBR only on separate data disks for other purposes.
Is converting only the data disks and leaving the Windows disk on GPT allowed?
Yes, and it is the arrangement most people actually want. Partition style is per-disk: your Windows SSD can stay GPT and UEFI while a second disk is converted to MBR for a legacy machine or tool. Nothing forces all disks in one PC to share a style.
This guide is based on the Technical Anshu GPT to MBR conversion video • Stuck on a step? Ask in the video comments — you will get a reply 🙏