How to Fix The Selected Disk is not a Fixed MBR Disk?

The error message “The Selected Disk is not a Fixed MBR Disk” indicates that the commands you’re trying to use are suitable only for MBR disks, and you’re dealing with a GPT disk. The “Active” command you are trying to use is not applicable to a GPT disk.

This error usually appears in several circumstances. It often shows up when trying to set a primary partition to active on a GPT disk—a concept not recognized by GPT (GUID Partition Table). Additionally, if the boot manager or BCD (Boot Configuration Data) store has problems, this error message is likely to appear.

With the causes explained, let’s explore solutions.

1. Fix the BCD store

The computer’s firmware uses the BCD store at startup to locate Windows for booting. If the BCD store is corrupted or missing, you might encounter related error messages.Using BCD commands can help repair a damaged BCD store by copying boot files from the Windows system drive and rebuilding the lost BCD store, which may resolve the issue.

  1. Insert a Windows bootable USB. Use this guide if needed.
  2. Go to boot options by pressing Delete and select the USB drive.
  3. Boot from USB, select your language, and click Next.
  4. Choose Repair your PC.
  5. Select Troubleshoot then Command Prompt.
  6. Determine the system drive and partition using:
    diskpart
    list disk
    select disk 0
    list volume

    Note: Replace “0” with your specific OS disk number.

  7. Assign a letter to the FAT32 volume:
    assign letter=z
  8. Exit diskpart using exit.
  9. Run the BCD command replacing <source> and <volume-letter> with your OS drive and assigned letter:
    bcdboot <source>/I <locale>/s <volume-letter>/f <firmware type>

    For example: bcdboot D:/Windows/I en-us/s Z:/f All

  10. Check if the error is resolved.

2. Convert the GPT disk to MBR

Converting a GPT disk to MBR can fix the “selected disk is not a fixed MBR disk” error, but it will erase all data on the disk. Back up important files first. Non-OS drives are easy to convert using command prompt or disk management tools. If the GPT disk has your operating system, you’ll need to reinstall Windows and switch to BIOS legacy mode, as MBR supports BIOS booting, while GPT is for UEFI.

  1. Type these commands.
    diskpart
    list disk
    select disk <disk number causing the error> (e.g., select disk 0)
    convert MBR

  2. Now, MBR commands will work without error messages.

3. Fix the Boot Manager

If the Boot Manager isn’t working, it can cause this error. The Boot Manager is important for starting your computer, as it controls the boot process and directs the system to the right partition. Running commands to rebuild the Boot Configuration Data (BCD), fix the Master Boot Record (MBR), and restore boot functions can make the boot process more reliable and fix potential boot errors.

  1. Open the command prompt as an administrator.
  2. Type cd /d C:\Windows\system32 and press Enter.
  3. Enter the following commands to repair the bootloader:
    bootrec /RebuildBcd
    bootrec /fixMbr
    bootrec /fixboot

  4. Check if the problem is resolved.

If these methods haven’t worked, you can switch the bios mode from UEFI to legacy following this guide. You’ll need to convert your GPT OS disk to MBR first using the second method and then you can reinstall Windows on the MBR disk, resolving the error.

ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Comments

6
    BK
    Bhuvanesh S K May 23, 2020

    Hello
    Isn’t MBR related to legacy boot and GPT to uefi secure boot ?
    In secure boot it took long time to boot when MBR drive was corrupted but in legacy boot it never booted .
    Disabling secure boot will actually make matter worse.

      SW
      Shane Warren Author May 27, 2020

      Did you try the first 2 solutions?

    WP
    Wake Up People Jun 6, 2020

    Just a heads up, on a condition I stumbled into, on an HP ENVY m7, when changing from secure to legacy. Make sure that you make one change, at a time. I started with enabling legacy first, rebooted, went back in and switched the secure boot off. With the first time around, I did both changes (same order) then did one reboot. I was still having erratic boots and a locked drive. Re-doing these with separate REBOOTS may help avoid these issues. Maybe even in other systems. (REM: Legacy disabled to enabled, and secure boot from enabled to disabled, or the equivalent of the settings)

    CW
    Chris Wilson May 6, 2021

    Hey heads up? That “clean” command will completely delete everything that is on that partition. If you want to try this “fix” make sure you have any important data backed up because this will just clobber your system

    TH
    Timothy Hordern Sep 12, 2023

    Hey guys. I got to “bootrec /fixboot” but it told me access was denied. It appears my ssd on my Dell Latitude 7370 is encrypted, when I never encrypted it in the first place. Also tried installing Ubuntu, but it told me I had to disable Bitlocker from Windows, which I don’t remember enabling. Can anyone help me please? Thanks in advance.

      MZ
      Muhammad Zubyan Author Sep 14, 2023
Need Help? From $35
Still stuck? Get expert help