0X00000A47 Boot Block Record Not Found Fix

Corrupted Boot Sector (The Most Common Cause)

Nine times out of ten, this error means the boot block record on your system drive is corrupt. I've seen it happen after a sudden power loss—last month a client's office lost power during a storm, and three machines came back with this exact error. The boot sector is like a map for your PC to find Windows. When it's scrambled, the PC throws up 0X00000A47 and stops.

The quickest fix is using the Windows Recovery Environment (WinRE) to run bootrec commands. Here's how:

1. Boot from a Windows installation USB or recovery drive. You can create one on another PC using the Media Creation Tool.
2. On the first screen, click 'Repair your computer' in the bottom-left corner.
3. Go to Troubleshoot > Advanced Options > Command Prompt.
4. Type these commands one by one, pressing Enter after each:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

After the last command, you'll be asked if you want to add the installation to the boot list. Press Y and Enter. Then restart your PC.

Most of the time this fixes it. But if bootrec /fixboot gives you 'Element not found' or 'Access is denied', skip to the next method.

Corrupted Boot Configuration Data (BCD)

If the boot sector fix didn't work, the BCD store itself might be corrupt. This is the file that holds the actual list of operating systems and their locations. I had a client whose Windows update borked the BCD—took longer to diagnose than to fix.

Back in the Command Prompt, run these:

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

This backs up the old BCD, renames it, and builds a fresh one from scratch. When it finds your Windows installation, type Y and hit Enter. Restart and see if the error's gone.

If you're on a newer PC with UEFI (most PCs built after 2012), the BCD path might be on the EFI system partition. In that case, you'll need to assign a drive letter to it. First, type diskpart, then list disk, select disk 0, list partition. Look for the partition labeled 'System' (usually around 100MB to 500MB). Select it with select partition X (replace X with the right number), then assign letter=S. Type exit to leave diskpart. Now run:

bcdedit /store S:\EFI\Microsoft\Boot\BCD /export S:\EFI\Microsoft\Boot\BCD.bak
attrib S:\EFI\Microsoft\Boot\BCD -h -r -s
ren S:\EFI\Microsoft\Boot\BCD BCD.old
bootrec /rebuildbcd

That's the UEFI version of the same fix. Works like a charm.

Dying Hard Drive or SSD

Sometimes it's not software—it's hardware. If the boot sector keeps getting corrupt even after you fix it, your drive might be on its way out. I've seen this with older mechanical hard drives after 5+ years of use, and with budget SSDs that hit their write limit early.

Before you panic, run CHKDSK to check the drive health. From the Command Prompt, type:

chkdsk C: /f /r

This scans the drive for bad sectors and attempts to recover data from them. It'll take a while—could be an hour on a large drive. If CHKDSK reports a ton of bad sectors or just hangs, your drive's probably failing.

You can also check the SMART status of the drive. In the same Command Prompt, type wmic diskdrive get status. If it says 'Pred Fail', replace the drive immediately. I had a client ignore that warning, and three days later their drive died completely—lost everything they hadn't backed up.

If the drive is failing, clone it to a new one using a tool like Clonezilla or Macrium Reflect Free. Then install the new drive and boot from it. The error won't come back if the new drive is healthy.

Quick-Reference Summary

Start with the first fix. If that doesn't work, move to the second. If you're still stuck, it's almost certainly a failing drive. Don't wait—back up your data now if you haven't already.