Fix 0X00000A3C: Profile record not found on login

When the error strikes

You’re at a domain-joined Windows 10 or 11 machine. User types their password, hits enter, and instead of the desktop they get a dialog: “Profile record was not found” with error code 0X00000A3C. Sometimes it’s a plain text box with the hex code. The system logs them in with a temp profile, or worse — it bounces them back to the login screen. This usually happens after a profile corruption, a botched system restore, or a forced domain policy update that left the registry in a broken state.

What actually causes it

Windows stores every local user profile’s info in the registry under HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList. Each profile gets a key named after its SID. Inside that key, there’s a value called ProfileImagePath pointing to the folder under C:\Users. When that key is missing, has wrong data, or the folder itself is gone — boom, error 0X00000A3C. The OS can’t find the record it needs to load the profile.

The culprit here is almost always a corrupt registry entry. Either the SID key is present but empty, or the ProfileImagePath points to a folder that was deleted manually. Another common trigger: a domain admin renamed the user folder thinking it’d fix something else — it never ends well.

How to fix it — step by step

Step 1: Boot to an admin account

You need a local admin account that isn’t affected. If you don’t have one, boot into Safe Mode with Networking and use the built-in Administrator account. Activate it with net user administrator /active:yes from an elevated command prompt if you have to.

Step 2: Find the broken profile

Open Registry Editor (regedit). Go to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Look for a SID key (starts with S-1-5-21...) that either:

Has no ProfileImagePath value
Has a ProfileImagePath pointing to a folder that doesn’t exist under C:\Users
Has a State value set to 0 or missing entirely

A healthy profile key has State = 1 (temporary) or 2 (persistent). If you see 0 or 4, it’s corrupt.

Step 3: Back up and delete the bad key

Right-click the offending SID key, choose Export, and save it somewhere safe. Then delete that key entirely. Don’t worry — you’re not deleting the user folder, just the registry record.

Step 4: Rebuild the profile

Have the affected user log off and then log back in. Windows creates a fresh registry entry automatically. The system will build a new profile folder under C:\Users\[username].DOMAIN or C:\Users\[username].000 if the original folder still exists.

Step 5: Migrate old data (if needed)

If the original user folder is still there (like C:\Users\john.doe), copy the contents — Desktop, Documents, Downloads, AppData — into the new profile folder. Do NOT copy the entire NTUSER.DAT file; that’ll bring the corruption back. Stick to user data files.

What if the fix doesn’t work?

If the user still gets the same error after deleting the registry key, check for a domain policy that forces a specific profile path. Group Policy can override local settings. Run gpresult /h gp.html and look for “Folder Redirection” or “Profile path” settings. If a policy is forcing a network path that doesn’t exist, that’s your real problem.

Another edge case: a corrupt NTUSER.DAT in the user’s original folder. If the folder exists but the registry key keeps reappearing with the same problem, rename the user folder to C:\Users\old_username, delete the registry key again, and let Windows build a completely fresh profile. Don’t bother with chkdsk or sfc — they never fix this.