Remote Desktop Credentials Didn’t Work in Win 10: Fixes

If you’re seeing “Your credentials did not work” when connecting to Windows 10 via Remote Desktop, the fix usually involves checking the username format, verifying the account password, or adjusting a Group Policy setting. Below are the most common causes and the exact steps to resolve them.

Why Windows 10 Rejects Valid Remote Desktop Credentials

Windows 10 Remote Desktop (RDP) stores credentials separately from your local sign-in. Even if you log into the PC normally, the RDP service may require a different authentication method. The most frequent reasons for the “credentials did not work” error are:

• You typed the username in the wrong format (e.g., PCNAME\User vs. User).
• The account has no password set, or the password was changed after the last RDP session.
• Network Level Authentication (NLA) requires the password to be entered before the session starts, and the cached credential is stale.
• The account is a Microsoft account, not a local account, and you used the wrong domain prefix.
• Group Policy or Registry settings restrict which users can log in via RDP.

Step 1: Use the Correct Username Format

For a local account, the username is usually COMPUTERNAME\Username. For a Microsoft account, it is the full email address. Many users type just the username without the computer name, which fails when the PC is not on a domain. To find the exact computer name, open Settings > System > About and look at “Device name”. Then in the RDP client, enter DEVICE-NAME\YourUserName (replace with your actual device name and username). If you use a Microsoft account, enter the full email address (e.g., user@outlook.com).

Step 2: Verify the Account Has a Password

Windows 10 does not allow RDP logins with a blank password by default. If your local account has no password, set one via Settings > Accounts > Sign-in options > Password. After setting it, try connecting again. If you use a PIN to sign in locally, note that RDP does not accept the PIN – you must use the account password. For a Microsoft account, the password is the one you use for the Microsoft account, not the PIN.

Step 3: Disable Network Level Authentication (NLA) Temporarily

NLA prompts for credentials before the remote desktop session starts. If the NLA handshake fails, you may see the credentials error even though the password is correct. To disable NLA on the target PC:

1. Open System Properties (Win + R, type sysdm.cpl, Enter).
2. Go to the Remote tab.
3. Uncheck “Allow connections only from computers running Remote Desktop with Network Level Authentication”.
4. Click OK and try connecting again.

If that fixes it, re-enable NLA later after you confirm the credentials work, because NLA is a security feature that reduces brute-force attacks.

Step 4: Check Group Policy / Local Security Policy

Windows 10 Pro and Enterprise have a policy that restricts who can log in via RDP. To check:

1. Press Win + R, type secpol.msc, Enter.
2. Go to Local Policies > User Rights Assignment.
3. Find “Allow log on through Remote Desktop Services”.
4. Ensure your username (or the group “Remote Desktop Users”) is listed. If not, add it.

If you are on Windows 10 Home, the Local Security Policy editor is not available. Instead, you can add your user to the Remote Desktop Users group via lusrmgr.msc (Local Users and Groups).

Step 5: Clear Stored RDP Credentials

Windows stores credentials in the Credential Manager. A stale entry can override what you type. To clear them:

1. Open Control Panel > User Accounts > Credential Manager.
2. Click “Windows Credentials”.
3. Look for any entry under “Remote Desktop Credentials” (often starts with TERMSRV/).
4. Remove those entries, then try connecting again.

Also, in the RDP client (mstsc.exe), go to the Advanced tab and clear the “Allow me to save credentials” checkbox if you don’t want them saved.

Step 6: When All Else Fails – Restart the Remote Desktop Service

Sometimes the Remote Desktop Services service gets stuck. On the target PC, open an elevated Command Prompt and run:

net stop TermService && net start TermService

Then try connecting again. If the service fails to start, check that the Remote Desktop Services service is set to Automatic and is running (services.msc).

Frequently Asked Questions

Why does RDP say my password is incorrect when I know it’s right?

This often happens when you use a PIN instead of the password, or when the account is a Microsoft account and you typed the local username. Also, if you recently changed the password, the RDP service may have cached the old one. Restart the target PC or restart the TermService service.

Can I use a Microsoft account to connect via RDP?

Yes, but you must enter the full email address as the username. If you see “The user name or password is incorrect”, try entering MicrosoftAccount\email@example.com (replace with your actual email).

Does Windows 10 Home support Remote Desktop?

Windows 10 Home can act as an RDP client, but it cannot be the host (the PC you connect to). If you are trying to connect to a Home edition, you need Pro or Enterprise, or use a third-party tool like TeamViewer or AnyDesk.

How do I enable Remote Desktop on Windows 10?

Go to Settings > System > Remote Desktop and toggle “Enable Remote Desktop” on. Confirm the prompt. Then ensure your user is in the Remote Desktop Users group.

What is the difference between NLA and standard RDP authentication?

NLA requires the user to authenticate before the remote session is created, which reduces the risk of denial-of-service and brute-force attacks. Standard RDP creates the session first and then prompts for credentials. Disabling NLA can help troubleshoot, but it lowers security.

Why does RDP work on the local network but not over the internet?

This is usually a router or firewall issue. You need to forward port 3389 to the target PC and have a public IP. However, exposing RDP to the internet is risky; consider using a VPN instead.

Related

• How to Fix Common WordPress Import Errors
• Wrestling Belt Relic Not Spawning in BO7: Fixes
• Gorilla vs Humans Codes?