Fix 0X000008AD: User name not found error

This error means Windows can't find the user account you're trying to connect to. The fix is usually checking the username or checking the account on the domain controller.

You're trying to connect to a shared folder, a remote desktop session, or a network printer, and instead of getting in, you get error 0X000008AD — the user name could not be found. Frustrating, right? Let's get this sorted.

First thing: check the username

This error, also known as NERR_UserNotFound, means Windows looked for the account you typed and couldn't find it anywhere — not on the local machine, not on the domain, not in Active Directory. So start with the obvious.

Make sure you typed the username correctly. This includes uppercase vs. lowercase — Windows is case-insensitive for usernames, but domain prefixes are case-sensitive. If the domain is Contoso, type CONTOSO\username, not contoso.


  If you're using a Microsoft account (like for Windows 10/11), the username is your full email address — you@outlook.com, not just you.
  For local accounts, the format is MachineName\Username or just .\Username (the dot stands for the local machine).



After you type the correct username and click OK, you should see a password prompt if the account exists. If you still get the error, move to step 2.

Check if the user account actually exists

If you're on a domain, open Active Directory Users and Computers on the domain controller. Look for the account. Is it there? Is it disabled? Expired? Locked out?


  Right-click the account, go to Properties, and check the Account tab. The account should be enabled and not expired.
  If the account is missing, you need to create it again or restore it from a backup. That's a domain admin task.
  If the account exists but the error still happens, verify the user can log on to the domain from a different PC. If they can, the problem is on the target machine.


Pro tip: This error often happens when you've recently migrated user accounts from one domain to another, or when you've renamed the account. The cached credentials on the client machine still point to the old name. Clear those out — we'll cover that next.

Clear cached credentials (the real fix 9 times out of 10)

Windows stores old passwords and usernames in a place called Credential Manager. If the stored info doesn't match the actual account, you get this error.


  Press Windows + R, type control, hit Enter.
  Click User Accounts, then click Credential Manager (on Windows 11 it's under User Accounts > Credential Manager).
  Choose Windows Credentials.
  Look for any entry related to the server or domain you're trying to connect to. You'll see things like TERMSRV/<server name> for Remote Desktop, or MicrosoftAccount:user= for Microsoft accounts.
  Click the arrow to expand that entry, then click Remove.
  Confirm removal. Repeat for any other entries that look stale.
  Close Credential Manager and try your connection again.


After clearing, you'll be prompted for the username and password fresh. Type the correct credentials and you should get through.

When the error shows up on a Remote Desktop connection

If you're using Remote Desktop (RDP) and you see 0X000008AD, it's almost always a credential mismatch. But there's another cause: the remote machine's local account policy.

The remote computer might have Network access: Do not allow storage of passwords and credentials for network authentication enabled. That setting is in the Local Security Policy (secpol.msc) under Security Settings > Local Policies > Security Options. If it's enabled, RDP won't save cached credentials, and if the typed credentials don't match exactly, you get this error. Disable that policy and try again.

Rare cause: DNS or NetBIOS name resolution problems

Sometimes the error is not about the username at all — it's about the computer name. Windows can't find the target machine on the network, so it can't check the user account there. This is more common in workgroups or small offices without a proper DNS server.


  Try connecting using the IP address instead of the computer name. For example, \\192.168.1.100\sharedfolder.
  If that works, you have a name resolution issue. Check that both PCs are on the same subnet, and that NetBIOS over TCP/IP is enabled on both (you can check in the network adapter's IPv4 properties, under Advanced > WINS).
  Also check the hosts file at C:\Windows\System32\drivers\etc\hosts for any incorrect entries.


Prevention tips


  Use consistent naming: always type the full DOMAIN\username format.
  When you rename a user account in Active Directory, immediately update any mapped drives or scheduled tasks that reference the old name.
  Set a reminder to clear cached credentials after a domain migration or password reset.
  If you manage multiple machines, push a Group Policy that restricts cached credentials to only the most recent logon — it reduces stale entries.


Start with the username check and credential cleanup. That fixes the vast majority of these errors. If you're still stuck, check the target machine's local security policy and the DNS setup. You'll get in.