Can’t Connect via RDP with Your Microsoft Account? Here’s Why—and How to Fix It (Windows 10)

Have you tried to use Remote Desktop (RDP) to connect from your desktop to your laptop, only to be greeted with the frustrating message:

“Your credentials did not work.”

Even though you’re sure your Microsoft account password is correct?

You’re not alone. Some users say RDP only accepts an old password; others can’t log in at all even though the same account works elsewhere. This guide explains why it happens on Windows 10/11 and shows clear, beginner-friendly fixes to get RDP working again.

❗ Common Error Message

“Your credentials did not work”

This appears when RDP can’t authenticate your username or password. With Microsoft accounts, there are a few extra quirks (sync timing, username format, cached credentials) that often cause this.

Before You Start: Requirements Checklist

• Remote PC edition: Windows Pro/Enterprise/Education (Home cannot act as an RDP host; it can only connect as a client).
• Remote Desktop enabled: Settings → System → Remote Desktop → On, note the PC name.
• A real password exists: RDP does not accept PIN/Windows Hello—use your account password.

Main Causes and How to Fix Them

1. ⚠️ The remote PC is still using your old Microsoft password

If you changed your Microsoft account password, the remote machine may not have synced yet (e.g., it was offline/asleep). RDP then rejects the new password.

• Wake the remote PC, connect it to the Internet, and sign in locally once with the new password to force sync.
• Then try RDP again.

2. Username format is wrong (Microsoft account vs. local)

For Microsoft accounts, using just the email sometimes fails. Try these formats:

Entra ID (Azure AD) devices specifically accept user@domain.com or AzureAD\user@domain.com.

3. Cached credentials need a refresh (restart helps)

Windows can keep using cached tokens until a reboot.

• Restart the remote PC, ensure it’s online, then retry RDP.
• If you changed your password, restart after signing in locally once.

4. Create a dedicated local account for reliable RDP

Using a simple, dedicated local account avoids most Microsoft-account quirks (sync, aliases, Hello-only sign-in, etc.).

👣 Create a Local Account (Windows 10/11)

1. Settings → Accounts
2. Family & other users → Add someone else to this PC
3. I don’t have this person’s sign-in information → Add a user without a Microsoft account
4. Set a username/password → (optional) add to Remote Desktop Users group.

Use COMPUTERNAME\LocalUser + that password in RDP.

RDP Login Field Examples

Tip: If you’re unsure of the local username format, run whoami on the remote PC to see COMPUTERNAME\Username.

How to Check Your PC Name

1. Settings → System → About
2. See Device name (use this in RDP or in Credential Manager entries).

Enable Remote Desktop Access

1. Settings → System → Remote Desktop
2. Turn Remote Desktop On → Confirm
3. Note the PC name and ensure the firewall rule is enabled (Windows does this automatically).

Extra Tips & Tricks

Trick #1: Use the “internal” username if email fails

Some setups map a Microsoft account to a local profile name. Trying COMPUTERNAME\ThatProfileName with your current Microsoft password can succeed when MicrosoftAccount\email fails. (Use whoami to discover it.)

Trick #2: Save credentials in Credential Manager

1. Control Panel → User Accounts → Credential Manager
2. Windows Credentials → Add a Windows credential
3. Enter the remote PC name, your username (MicrosoftAccount\email or COMPUTERNAME\LocalUser), and password.

This reduces typos and helps avoid auth prompts.

⚠️ Reminder: PIN/Windows Hello won’t work over RDP

Always use the full account password for RDP sign-in.

About Microsoft’s “Windows” App vs. Classic RDP

Microsoft is shifting cloud connections (Windows 365, Azure Virtual Desktop, etc.) from the Store “Remote Desktop” app to the newer Windows app. The classic Remote Desktop Connection (mstsc.exe) remains available for PC-to-PC RDP and continues to work.

Final Thoughts

• Check the username format (MicrosoftAccount\email / COMPUTERNAME\LocalUser / AzureAD\user@domain.com).
• Sign in locally once after password changes and restart the remote PC.
• Use Credential Manager to store credentials cleanly.
• For maximum reliability, set up a local account dedicated to RDP.
• Confirm the remote edition supports hosting and that Remote Desktop is enabled.

With these steps, you’ll avoid the common pitfalls of Microsoft-account sign-ins and connect smoothly between devices.

You might also find these useful:
▶︎ [Solved] 5 Practical Ways to Open Large CSV Files Faster in Excel (Without Crashes)
▶︎ [With Pro Tips] 7 Ways to Speed Up Opening Large Files on Windows
▶︎ Windows Laptops Failing to Boot After June 2025 Update: A Deep Dive into System Failures

← Back to English Article List

タグ: RDP login issue, Local account RDP, Windows 10 remote access, Microsoft account not working, Fix RDP authentication, Remote Desktop Windows 10, RDP credential error