0XC00000A9 Boot Error: Fix Bad MBR in 2 Minutes

You're staring at 0XC00000A9 and your machine won't boot. Yeah, it sucks. Let's fix it.

The culprit here is almost always a busted master boot record (MBR) or a jacked-up partition table. Windows can't find the boot code it needs. The error message says "token object inappropriate" which is Microsoft's way of saying "the disk's boot structure doesn't match what we expect."

The Fix: Rebuild the MBR with bootrec

You'll need Windows installation media — a USB stick or DVD. Boot from it. On the first screen, click Repair your computer (bottom-left corner), then Troubleshoot → Advanced options → Command Prompt.

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

Run these three commands in that order. The first rewrites the MBR code. The second fixes the boot sector on the system partition. The third scans for Windows installations and rebuilds the Boot Configuration Database (BCD).

After /rebuildbcd, it'll ask if you want to add the installation to the boot list. Type Y and press Enter. Then reboot.

This works on Windows 7, 8, 8.1, 10, and 11. I've done it on hundreds of machines — Dell Optiplex, HP ProDesk, custom builds. Same fix.

Why This Works

The MBR is the first 512 bytes of your disk. It contains code the BIOS uses to load Windows. If that code gets corrupted — from a failed update, power loss during boot, or a dual-boot gone wrong — you get the error. bootrec /fixmbr writes fresh, clean boot code. /fixboot repairs the boot sector on the active partition. /rebuildbcd fixes the boot menu that Windows reads. Together, they cover all the common failure points.

When the Standard Fix Doesn't Cut It

Sometimes the standard bootrec commands fail. Here's what to try next.

Check Disk for Bad Sectors

Physical damage to the drive can nuke the MBR. Run this from the same Command Prompt:

chkdsk c: /f /r

Replace c: with your system drive letter — it might not be C: in recovery mode. Run diskpart, then list volume to find it. If chkdsk finds bad sectors, the drive is dying. Replace it.

Active Partition is Wrong

If you have multiple drives or partitions, the active partition might point to the wrong one. In diskpart:

diskpart
list disk
select disk 0
list partition
select partition 1
active
exit

Make sure the partition marked as active is the System Reserved partition (usually 100-500 MB) or the boot drive that contains the Windows boot files. Setting the wrong partition as active causes this exact error.

UEFI vs Legacy BIOS Confusion

If your PC uses UEFI but the disk is MBR (or vice versa), you'll hit this. Check your BIOS boot mode. If it's set to UEFI, the disk must be GPT. If it's Legacy/CSM, it should be MBR. I've seen this on prebuilt machines where someone reset the BIOS. Change the boot mode in BIOS to match your disk format.

Corrupt BCD Store

If /rebuildbcd fails with "The requested system device cannot be found," nuke the BCD file and rebuild it manually:

bcdedit /export C:\BCD_Backup
c:
cd boot
attrib bcd -s -h -r
ren bcd bcd.old
bootrec /rebuildbcd

This deletes the corrupt BCD and lets bootrec create a fresh one.

Prevention: Stop It from Happening Again

Most MBR corruption comes from three things. Avoid these.

Don't hard-shutdown your PC. Pulling the plug while Windows is writing boot data is the #1 cause. Let the system shut down properly. Even if it hangs for a minute, wait.
Keep your boot drive healthy. Run chkdsk c: /f every few months. If SMART data (check with CrystalDiskInfo) shows reallocated sectors, replace the drive before it fails.
Be careful with dual-boot setups. Installing a second OS can overwrite the boot sector. Use a dedicated boot manager like rEFInd for Linux/Windows dual-boot — it's less likely to corrupt the MBR.
Disable Fast Startup. Fast Startup in Windows 10/11 doesn't fully shut down the OS. It can cause boot data corruption over time. Turn it off in Power Options → Choose what the power buttons do → Uncheck "Turn on fast startup."

If you've followed these steps and still get the error, the drive is toast. Replace it, install Windows fresh, and restore your data from backup. You do have a backup, right?