You need to enable JavaScript to run this app.
Elastic Compute Service

Elastic Compute Service

Copy page
Download PDF
Windows operating system issue
What do I do if the "As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts." error message is displayed?
Copy page
Download PDF
What do I do if the "As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts." error message is displayed?
Issue description​
When I am using an ECS instance running the Windows operating system, the "As a security precaution, the user account has been locked because there were too many login attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support" error message is displayed.​
Causes​
The security mechanism of the system is triggered when an incorrect password is entered too many times during a Remote Desktop login to the instance.​
Solutions​
In this example provided in this topic, the Windows Server 2022 Datacenter Edition 64 bit operating system is used.​
  1. Use VNC to log in to the instance. For more information, see Using the console to log in to a Windows instance.​
If you are unable to use VNC to log in to the instance, reset the login password and then try again.​
  1. Right-click the "Start" icon, and then click the "Run" button to open the "Run" dialog box.​
  1. Enter the following command in the dialog box, and click the "OK" button.​
  • ​
    gpedit.msc​
    ​
  1. In the "Local Group Policy Editor" window, select "Computer Configuration > Windows Settings > Security Settings > Account Policies > Account Lockout Policy".​
  • ​​​
  1. Double-click "Account lockout threshold" to open the account lockout threshold window.​
  1. Modify the number of consecutive incorrect login password attempts required to lock the account based on your needs, and then click the "OK" button to complete the modification.​
If 0 is specified, there is no limit on the number of consecutive incorrect password attempts.​
  • ​​​
  1. Use Remote Desktop to connect to the instance again and check whether you can log in to the instance as expected.​
Last updated: 2026.04.13 16:50:02