How to Fix “The User Account Has Been Locked Because There Were Too Many Logon Attempts” RDP Error on Windows

Remote Desktop Protocol (RDP) is one of the most widely used methods for remotely accessing Windows computers and servers. Whether you’re managing a personal PC, connecting to a work computer, or administering a Windows Server, RDP provides a secure and convenient way to work remotely. However, you may sometimes encounter the error “The user account has been locked because there were too many logon attempts.” When this occurs, you’re unable to sign in using Remote Desktop until the account is unlocked or the lockout period expires.

This error usually appears after multiple failed login attempts with an incorrect password, but it can also be triggered by saved credentials, outdated Remote Desktop sessions, automated scripts, mapped drives using old passwords, scheduled tasks, or brute-force login attempts. In domain environments, account lockout policies configured through Active Directory can also cause the account to become temporarily locked.

Fortunately, you can resolve this issue by waiting for the lockout duration to expire, unlocking the account, updating saved credentials, and identifying the source of repeated failed login attempts. In this guide, we’ll walk you through the most effective methods to fix the “The user account has been locked because there were too many logon attempts” RDP error on Windows 10, Windows 11, and Windows Server.

How to Fix “The User Account Has Been Locked Because There Were Too Many Logon Attempts” RDP Error

Before you begin, make sure you know the correct password for the account you’re trying to use. If you recently changed your password, update it everywhere the account is used before attempting another sign-in.

1. Wait for the Account Lockout Period to Expire

Many Windows systems automatically unlock user accounts after a configured lockout duration.

1. Wait for the configured account lockout period.
2. Avoid making additional login attempts during this time.
3. Try signing in again using the correct password.

On many systems, the lockout period ranges from 15 to 30 minutes, although administrators can configure different values.

2. Verify That You’re Using the Correct Password

Repeatedly entering an incorrect password will continue triggering account lockouts.

1. Confirm your current password.
2. If necessary, reset your password.
3. Sign in locally first, if possible.
4. Retry the Remote Desktop connection.

Verifying your credentials prevents additional failed logon attempts.

3. Clear Saved Remote Desktop Credentials

Windows may automatically retry outdated saved credentials.

1. Open Control Panel.
2. Go to Credential Manager.
3. Select Windows Credentials.
4. Locate saved Remote Desktop credentials.
5. Remove the stored credentials.
6. Reconnect using the correct username and password.

Removing outdated credentials prevents automatic failed logins.

4. Unlock the User Account

If you have administrative access, unlock the account immediately instead of waiting.

For Local Accounts

1. Open Computer Management.
2. Navigate to Local Users and Groups > Users.
3. Open the affected user account.
4. Clear the Account is locked out option (if available).
5. Apply the changes.

For Active Directory Accounts

1. Open Active Directory Users and Computers.
2. Locate the affected user.
3. Open Properties.
4. Go to the Account tab.
5. Unlock the account.
6. Apply the changes.

This immediately restores access if you have sufficient permissions.

5. Check for Background Services Using Old Credentials

Windows services configured with outdated passwords may continuously trigger failed logons.

1. Open Services.
2. Review services running under user accounts.
3. Update the stored password where necessary.
4. Restart the affected services.

Incorrect service credentials are a common cause of repeated account lockouts.

6. Update Scheduled Tasks

Scheduled tasks may still use an old password.

1. Open Task Scheduler.
2. Review tasks configured to run under the affected account.
3. Update the stored credentials.
4. Save the changes.

Incorrect task credentials can repeatedly lock the account.

7. Disconnect Stale Remote Desktop Sessions

Old sessions may continue attempting authentication.

1. Open Task Manager or Remote Desktop Services Manager (Windows Server).
2. Review active user sessions.
3. Sign out disconnected or stale sessions.
4. Reconnect using the correct credentials.

Removing old sessions prevents repeated authentication failures.

8. Review Security Event Logs

The Windows Security log can help identify the source of failed logon attempts.

1. Open Event Viewer.
2. Navigate to Windows Logs > Security.
3. Look for failed logon events such as Event ID 4625.
4. Identify the source computer or process generating failed logins.

This helps determine whether the lockout is caused by another device, application, or user.

9. Scan for Unauthorized Login Attempts

If the account locks unexpectedly, it may be the target of repeated login attempts.

1. Run a full Windows Security scan.
2. Review firewall logs if available.
3. Check Remote Desktop exposure to the internet.
4. Consider enabling account monitoring.

Unauthorized login attempts should be investigated promptly, especially on internet-facing systems.

10. Reset the Account Password

If you’re unsure whether the password is correct, reset it.

1. Open Computer Management or Active Directory Users and Computers.
2. Reset the user’s password.
3. Update the password on all devices, services, and scheduled tasks.
4. Sign in again.

Updating every stored credential prevents future lockouts.

11. Review Account Lockout Policy

Administrators can modify account lockout settings if appropriate.

1. Open Local Security Policy or Group Policy Management.
2. Navigate to:

Computer Configuration > Windows Settings > Security Settings > Account Policies > Account Lockout Policy

3. Review:
   • Account lockout threshold
   • Lockout duration
   • Reset account lockout counter

Adjust these settings only if they align with your organization’s security requirements.

12. Restart the Remote Desktop Services

If authentication issues persist, restarting the service may help.

1. Open Services.
2. Locate Remote Desktop Services.
3. Restart the service if possible.
4. Reconnect to the remote computer.

Restarting the service refreshes active RDP sessions and authentication processes.

Conclusion

The “The user account has been locked because there were too many logon attempts” error typically occurs after repeated failed authentication attempts through Remote Desktop, Windows services, scheduled tasks, or other applications using outdated credentials. In most cases, waiting for the lockout period to expire, clearing saved credentials, updating stored passwords, and unlocking the account will resolve the issue.

If the problem continues, investigate Windows Security logs, review account lockout policies, and identify any background processes or devices repeatedly attempting to sign in with incorrect credentials. By keeping passwords synchronized across all services and monitoring failed logon events, you can prevent future RDP account lockouts and maintain secure remote access to your Windows systems.