Fix 0X00000A3D: Profile name in use error

What triggers 0X00000A3D?

You'll see this error when Windows can't create or load your user profile because the profile name (the folder under C:\Users) is already tied to a different account. It's common after a domain migration, a failed Windows update, or when you delete an old user account but the profile folder lingers.

Here's the real issue: Windows checks the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. If two SIDs reference the same profile image path, or one SID has a stray lock, you get code 0X00000A3D.

Let's fix it. Stop at the first fix that works.

Fix 1: Reboot and try again (30 seconds)

I know this sounds basic, but half the time Windows just needs a clean slate. Restart your machine completely — not a shutdown with fast startup enabled. Do a full restart.

Then log in with the affected account. If the error's gone, you're done. If not, move on.

Fix 2: Release the lock on the profile folder (5 minutes)

Sometimes a background process holds a handle on the profile folder. Here's how to break it:

Press Win + R, type compmgmt.msc, hit Enter.
Go to System Tools > Shared Folders > Open Files.
Look for any file from C:\Users\[your profile name]. Right-click it and select Close Open File.
If you see multiple files, close them all. Then try logging on again.

If that list is empty, run this command in an admin PowerShell:

Get-SmbOpenFile | Where-Object { $_.Path -like "*Users*" } | Close-SmbOpenFile -Force

This clears any SMB locks that might be lingering from network shares or remote desktop sessions. Try logging in again.

Fix 3: Rename the profile folder and registry entry (10 minutes)

This is the money fix. The profile name is in use because Windows sees the folder path in the registry. We'll rename both.

Step 1: Backup your profile folder

Log in with a different admin account. If you don't have one, boot in Safe Mode with networking (press F8 or Shift + Restart).

Navigate to C:\Users. Find the folder with the profile name that's causing the error. Right-click it, rename it to something like OldProfileName. Don't delete it — you might need files later.

Step 2: Edit the registry

Press Win + R, type regedit, hit Enter. Go to:

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

Look for a key (a long GUID) that has a ProfileImagePath value pointing to the old folder path. You'll see something like C:\Users\[YourProfileName].

Double-click ProfileImagePath and change it to match the new folder name you just gave. In my example, that would be C:\Users\OldProfileName.

Also check for any key under ProfileList that has a State value of 0 (meaning it's a temporary profile). If you see one, delete that key entirely — but only if you're 100% sure it's not the active account you're using right now.

Step 3: Reboot and log in

Restart and log in with the affected account. Windows should now load your profile from the renamed folder.

Fix 4: Delete the orphaned profile entry (advanced, 15+ minutes)

If none of the above worked, the profile SID is corrupted beyond repair. You need to nuke it and start fresh.

Warning: This will delete the user profile — all settings, files on the desktop, documents, and bookmarks. Back up any critical data first from C:\Users\[OldProfileName] while logged in as another admin.

Step 1: Identify the SID

Open Command Prompt as admin and run:

wmic useraccount get name,sid

Find the SID for the problematic user. It looks like S-1-5-21-....

Step 2: Delete the profile from registry

In regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Find the key matching that SID. Right-click it and delete.

Step 3: Delete the profile folder

Go to C:\Users and delete the folder (again, only if you've backed up your data).

Step 4: Recreate the user

Open Settings > Accounts > Family & other users, remove the account, then add it back. Or use this PowerShell command as admin:

Remove-LocalUser -Name "YourUserName"

Then add the user again via:

New-LocalUser -Name "YourUserName" -Password (Read-Host -AsSecureString "Enter password")

When to throw in the towel

If you're still seeing 0X00000A3D after all this, the issue might be in your domain controller or a group policy that maps profile paths. Check with your IT admin if you're on a domain — they might need to clean up the profile list in Active Directory.

On a standalone machine, this has never failed me. The registry rename in Fix 3 handles 9 out of 10 cases. Good luck — you've got this.