“The selected disk is not a fixed MBR disk” usually appears after a DiskPart command such as active is aimed at a GPT disk, removable media, or the wrong selected object. It does not mean you should erase the drive and convert it to MBR. First identify the exact disk and partition, read their current style, and protect any files you cannot replace. The safe fix depends on whether Windows was installed for UEFI/GPT or for legacy BIOS/MBR booting.
Understand why DiskPart rejected the command
The active flag belongs to a legacy boot arrangement. In Microsoft’s DiskPart active command documentation, the operation marks a selected partition as capable of holding startup files. DiskPart does not verify that the files are actually there. Marking the wrong partition active can therefore make a PC unbootable. On a modern UEFI installation using GPT, the usual boot path is different; forcing an MBR-style instruction onto it does not create the missing boot files.
A second possibility is simply that DiskPart is focused on another disk or partition than the one you intended. Numbers can change when you boot from a USB recovery drive or connect extra storage. “Disk 0” is not a permanent synonym for your Windows SSD. Always identify the device by model, size, connection, and layout before issuing commands that write to it.
The error can also occur when the selected medium is removable. A bootable USB installer may be visible alongside the internal system drive. Trying to mark a partition on that USB stick active while diagnosing the internal disk will not repair Windows. The message is a clue about the command-target mismatch, not proof that the main drive’s partition table is corrupt.
Make a record of the current disk layout
Stop before clean, convert, format, or delete partition. Those are source-modifying operations. If the disk contains the only copy of important files, recover or verify a backup first. A wrong command can remove partition references or overwrite structures that might otherwise help locate data.
From an appropriate Windows Command Prompt, diskpart followed by list disk displays detected disks and their sizes. The GPT column helps identify a GPT-style disk. list volume and list partition display different levels of the layout. These listing commands are for observation. Note that drive letters in a recovery environment may differ from those in your usual Windows session. Do not paste a full sequence containing someone else’s disk number.
Write down the Windows disk’s approximate capacity, whether the GPT indicator appears, whether an EFI System Partition is shown, and the exact command that produced the error. A screenshot or photo of the layout is useful. If the expected disk is missing, appears with the wrong capacity, or disconnects during inspection, stop software repairs and assess hardware or connection stability. A command-line tutorial cannot make an absent device readable.
Choose the route that matches the actual installation
The Windows disk uses GPT and UEFI
Do not convert it to MBR just so active will run. The GPT/UEFI arrangement uses an EFI System Partition and firmware boot entry rather than the legacy active-partition approach. If Windows Boot Manager is missing or damaged, use an appropriate Windows recovery environment to diagnose that boot path. You may need a BitLocker recovery key to access the volume. The dedicated article on Windows Boot Manager missing handles that narrower repair after data is protected.
Check whether the firmware itself still detects the disk and whether a Windows Boot Manager entry exists. Changing UEFI to Legacy mode as an experiment can hide a valid installation. Record current firmware settings before changing a boot priority. Rebuilding the EFI partition or boot files is a deliberate write-based operation, not a default response to this DiskPart message.
The selected disk is removable or not the Windows disk
Exit DiskPart without changing anything. Identify the internal system drive by capacity and model in firmware or Disk Management. Remove nonessential USB storage before the next diagnostic boot if you can do so safely. When a drive number changes after removing the USB installer, that confirms why copying a fixed command sequence from another computer is risky.
If the intended internal disk is not detected, do not keep selecting other disks until one accepts active. The problem may be a connection, controller, or failing drive. A disk that clicks, repeatedly disappears, or reports inconsistent capacity needs hardware-oriented assessment and possibly a professional image.
A genuine BIOS/MBR system needs a legacy boot repair
Only if you have verified that the Windows installation really uses BIOS/MBR should an active-partition decision be considered. Even then, the target must be the correct system partition containing or intended to contain boot files, not simply the largest partition. DiskPart does not make that judgment for you. If you are unsure, use manufacturer or Windows recovery diagnostics and seek technical help rather than guessing. An incorrect active flag can prevent startup.
The broader GPT-or-MBR explanation compares the two partition styles. This error is narrower: it tells you that the selected object does not fit the legacy command you attempted. It is not a recommendation to change your entire disk style.
Preserve data before boot or partition changes
Check whether you have a recent external backup, cloud copy, or image of the files you need. Open representative files from that backup on a working device. If the system disk is recognized and stable but Windows does not boot, use a suitable recovery environment or attach the source drive safely to another Windows PC. Do not allow the receiving computer to initialize, format, or repair it automatically. Unlock BitLocker only with the authorized recovery key.
Drecov is Windows data-recovery software for files on stable, recognized storage. Its Quick Scan, Deep Scan, filters, and preview help find candidate documents and photos before saving them to a separate healthy disk. If a partition has gone missing but the physical disk remains visible, its Lost Partition Recovery mode is relevant. These functions search for data; they do not convert GPT to MBR, rebuild a boot entry, or repair failing hardware. Drecov cannot guarantee recovery of overwritten content.
Prepare another healthy drive with enough space, and install the software away from the source. If the affected disk is physically unstable, stop repeated scans; a professional image may be safer. Because the original Windows drive may not boot, the source must first be accessible through a functioning Windows environment. Do not install a new Windows copy onto that source merely to run a recovery app.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Step 1: Open Drecov and select the original stable disk
Choose the disk or partition that held the missing files, checking model and capacity. If the partition entry is gone, select Lost Partition Recovery for the recognized physical disk. The healthy output device must not be used as the scan source.
Step 2: Run Quick Scan for known user folders
Look for Documents, Desktop, Pictures, and project paths. If the partition map is damaged, original names may be incomplete. Check a few distinctive filenames or file types. Stop if the source begins disconnecting or showing severe read errors.
Step 3: Use Deep Scan only if a stable source needs it
When Quick Scan does not show essential files and the disk continues to read normally, try Deep Scan. It can reveal additional candidates. It does not repair the partition table in place or make a physically failing device safe to keep scanning.
Step 4: Filter, preview, and select coherent sets
Filter by former path, filename, or type. Preview supported files and include related assets when recovering a project. A visible preview of one file does not verify an entire directory. Select a representative sample for export before committing to a large batch.
Step 5: Save to another drive and verify
Recover files to the prepared healthy device, never back onto the original disk. If they are not in the chosen folder, inspect the Drecov Folder or Recovery Folder on the destination. Open several files in their normal applications and confirm they contain the expected work. Only then return to any boot repair or partition-style decision.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
What not to infer from a successful command
If you later find an MBR partition that accepts active, that only shows the command was allowed. It does not prove that the partition has the right boot files. Check whether Windows actually starts and whether the same drive remains stable after a full shutdown. If startup still fails, avoid marking additional partitions active one by one. Each change can make diagnosis harder.
If a conversion tool reports success, that also does not confirm every personal file is intact. Test the backup or recovered files separately. For a GPT system, a working UEFI boot entry and an accessible Windows volume are different checkpoints. Keep a record of which one failed. The absence of a boot entry does not automatically mean the document partition has been erased.
If you discover that a previous command already deleted or reformatted a partition, stop additional writes to that disk. A lost-partition or file-recovery path may still be possible on stable media, but each new allocation can overwrite evidence. This is another reason not to treat clean as a harmless reset of DiskPart.
The selected disk is not a fixed mbr disk FAQs
Does the error mean my disk is broken?
No. It often means the selected disk or partition does not fit the legacy MBR operation. Check style and identity first. Physical warning signs such as disconnections or wrong capacity require separate attention.
Can I convert GPT to MBR to make the active command work?
That is not a safe generic fix. It changes the disk layout and may break a UEFI Windows installation. Preserve data and identify the actual boot configuration before considering any conversion.
Why does DiskPart list a different disk number in recovery media?
Device enumeration can change when a USB installer or other storage is connected. Match the disk by size, model, and layout rather than relying on a number copied from another session.
Is Lost Partition Recovery the same as repairing GPT?
No. It is a way to search for files associated with a missing partition on a suitable stable disk. Save found files elsewhere; rebuilding boot or partition structures is a separate decision.
Should I run clean and start over?
Not when the disk contains needed files. Clean removes partition information and can make later recovery harder. Back up or recover the data first, then decide whether a fresh installation is actually required.
Conclusion
“The selected disk is not a fixed MBR disk” is a mismatch between the command and the selected storage, not an instruction to erase it. Verify the disk, its GPT or MBR style, and the firmware boot mode. Protect unique files before boot repairs or conversions. On a stable recognized drive, Drecov can search missing files or a lost partition and save recoverable results to another healthy device; it does not turn a GPT disk into a bootable MBR disk.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
