STATUS_SAM_INIT_FAILURE (0XC00002E3) – Fix It Fast

What You're Looking At

You're staring at a blue screen or black screen with STATUS_SAM_INIT_FAILURE (0XC00002E3). The Security Account Manager (SAM) registry hive is jacked up. Windows can't read the database that stores user accounts and passwords. This means no login, no desktop, nothing.

The culprit here is almost always a corrupted SAM hive file. Common triggers: a hard shutdown while Windows was writing to the registry, a failing hard drive, or a botched Windows update. I've also seen this after someone ran a registry cleaner tool. Don't run those.

Let's get you booting again. Work through these steps in order. Stop when the machine comes back.

The 30-Second Fix: Last Known Good Configuration

This is the easiest shot. It restores the last set of registry hives that actually worked. Doesn't always help, but it's fast.

1. Reboot the machine.
2. As soon as the motherboard logo appears, start tapping F8 repeatedly until you see the Advanced Boot Options menu. (On Windows 10/11 with UEFI, you might need to interrupt boot three times to trigger Automatic Repair, then go to Troubleshoot > Advanced Options > Startup Settings.)
3. Use the arrow keys to select Last Known Good Configuration (advanced) and press Enter.

If the system boots, you're done. Go update your drivers and run chkdsk C: /f from an admin command prompt later to rule out disk issues. If you get the same error, move on.

The 5-Minute Fix: Boot from Recovery Media and Run System File Checker

If Last Known Good didn't work, you need to boot from Windows installation media (USB or DVD). Don't have any? Create one on another PC using Microsoft's Media Creation Tool. You need at least a 8GB USB drive.

1. Insert the Windows installation media and boot from it.
2. On the first screen, click Next, then click Repair your computer at the bottom-left.
3. Go to Troubleshoot > Advanced Options > Command Prompt.

Once you have a command prompt, run these commands one at a time:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

This scans and repairs protected system files. If your Windows drive is D: or something else, change the paths accordingly. To find your drive letters, type diskpart, then list volume, then exit.

After SFC finishes, run DISM to fix the system image itself:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth

This downloads fresh files from Windows Update. Takes 5-10 minutes. If it succeeds, reboot and see if the error clears. If not, the SAM hive is likely beyond SFC's reach.

The 15+ Minute Fix: Manual SAM Hive Repair or Replacement

This is the real fix for most cases. The SAM hive is at C:\Windows\System32\config\SAM. You're going to replace it with a backup copy that Windows keeps.

1. Boot from your installation media and open Command Prompt as before.
2. Navigate to the config folder:

cd /d C:\Windows\System32\config

Now rename the corrupted SAM file and copy the backup:

ren SAM SAM.corrupt
copy C:\Windows\System32\config\RegBack\SAM C:\Windows\System32\config\

Important: On Windows 10 version 1803 and later, Microsoft stopped backing up SAM to the RegBack folder by default. So that copy command might fail with "The system cannot find the file specified." If it does, you need to try the next approach.

If RegBack is empty, your best bet is to restore from a Volume Shadow Copy. Still in the command prompt:

vssadmin list shadows /for=C:

This lists any shadow copies (restore points). If one exists, note its Shadow Copy Volume path — something like \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1. Then copy the SAM from there:

copy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Windows\System32\config\SAM C:\Windows\System32\config\

Replace the path with your actual shadow copy volume. If that works, type exit and reboot.

No shadow copies either? You can try a registry recovery tool like chntpw (offline registry editor) from a Linux live USB. Boot from a Ubuntu USB, install chntpw with sudo apt install chntpw, then mount the Windows drive and run:

sudo chntpw -e /mnt/Windows/System32/config/SAM

This lets you blank or edit user passwords. Sometimes simply opening and rewriting the hive can fix minor corruption. Real talk: I've only had this work about 50% of the time. If it fails, you're looking at a full reinstall.

When You're Out of Options: Backup and Reinstall

If none of the above works, the SAM hive is toast. Before giving up, pull the drive, connect it to another PC as a secondary drive, and copy off any critical files from C:\Users\[YourUsername]. Then reinstall Windows from scratch. It sucks, but it's faster than spending another two hours chasing dead ends.

This error has been around since Windows NT. It's not going away. Keep a USB recovery drive handy — it saves you every time.