Fix STATUS_SPECIAL_ACCOUNT 0xC0000124: Step-by-Step

The STATUS_SPECIAL_ACCOUNT error (0xC0000124) stops Windows from logging in after a botched account change. Start with the quick fix, then move up the ladder.

The 30-Second Fix: Reboot into Safe Mode and Check Your Account Type

Before you tear your hair out, try this. That error almost always appears right after someone or something fiddled with user accounts—maybe you used net user in a cmd window, or an installer tried to change your group memberships. The quickest path is to force a reboot into Safe Mode and see if you can get in.

Restart your PC. As soon as the Windows logo appears, hold the power button to interrupt the boot. Do this three times.
On the fourth boot, Windows will show the Recovery screen. Click Advanced options → Startup Settings → Restart.
Press 4 or F4 for Safe Mode.

If you get in, open Command Prompt as administrator and run:

net localgroup administrators

Check if your user account is listed. If it's not, add it:

net localgroup administrators YourUserName /add

Reboot normally. That fixes it for maybe 40% of folks. Had a client last month—a dental office—whose receptionist's login suddenly broke after a routine domain shift. Safe Mode + group check got them back in under two minutes.

The 5-Minute Fix: Reset the Account Flags in the Registry

If Safe Mode didn't let you in, or you're still getting the error, the problem is likely a corrupted UserAccountControlSettings flag in the registry. Specifically, the SpecialAccount value getting set to 0 when it shouldn't be. That's what the error code literally means—the system thinks your account is special (like built-in Administrator) but it's not configured right.

You'll need to work from the Windows Recovery Environment (WinRE) because you can't log in.

Boot to the Recovery screen again (same interrupt method as above).
Go to Troubleshoot → Advanced options → Command Prompt.
Find your Windows drive. Usually it's D: in WinRE, but check with dir to be sure.
Run the registry editor from the recovery cmd:

regedit

In regedit, click on HKEY_LOCAL_MACHINE to highlight it, then go to File → Load Hive. Navigate to D:\Windows\System32\config\SAM. Give it a name like OfflineSAM.

Now drill down to:

OfflineSAM\SAM\Domains\Account\Users\000001F4

That's the built-in Administrator account, which often gets mangled. Look for a F value, double-click it, and check the data. You're looking for the byte at position 0x38. If it's 0x00, change it to 0x11. That sets the account type back to normal user admin.

If you can't find that path, your account might have a different RID. Use wmic useraccount get name,sid from the cmd prompt to map your username to the correct SID, then find the corresponding key under Users.

After editing, highlight OfflineSAM and go to File → Unload Hive. Close regedit, type exit to close cmd, and reboot.

This is the fix that works for most people stuck with 0xC0000124. I've seen it happen after a failed domain join, a third-party antivirus tool, and even after a Windows update that botched user profile permissions.

The 15-Minute Fix: Rebuild the Profile in the Registry (if all else fails)

If you're still locked out, the account profile itself is corrupted. Don't waste time trying to repair it as-is—rebuild it. This takes a bit longer but is bulletproof.

First, back up your data. Boot into WinRE again, open Command Prompt, and copy your entire profile folder to an external drive:

robocopy D:\Users\YourName E:\Backup\YourName /E /COPYALL

Now delete the corrupted profile from the registry. In WinRE's Command Prompt, load the DEFAULT hive (it's in D:\Windows\System32\config\DEFAULT) but that's not enough. You need to edit the ProfileList key under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. But that's under the system's Software hive. Load D:\Windows\System32\config\SOFTWARE as another hive, say OfflineSoft.

Navigate to:

OfflineSoft\Microsoft\Windows NT\CurrentVersion\ProfileList

You'll see SIDs. Find the one matching your user (use wmic useraccount get name,sid again). Delete the entire key for that SID. Also delete the corresponding profile folder under D:\Users\YourName—but you already copied it, right?

Now unload both hives (OfflineSoft and any others you loaded) and reboot. Windows will create a fresh profile with the same username, but it'll be clean. You'll lose your desktop settings, but your files are safe on the backup.

One warning: if you have a Microsoft account linked, you might need to sign in online again. That's normal.

When to Stop and Call in Reinforcements

If you've done the registry fix and the profile rebuild and you're still staring at 0xC0000124, something deeper is wrong—possibly a corrupted security descriptor on the SAM hive itself. That's rare, but I've seen it after a failed disk encryption tool. At that point, stop trying to repair and do a repair install with the Windows Media Creation Tool. It keeps your files but resets system files. That usually nukes any lingering account weirdness.

Don't bother with system restore points—they don't touch the SAM hive properly, so they won't help here. And don't run SFC or DISM from WinRE; they can't fix account flags.

The key takeaway: this error is almost always account metadata gone sideways. Start with the group check, move to the registry flag, and only if that fails, rebuild the profile. You'll be back in before your coffee cools.