Last Updated: September 2026
Seeing “The referenced account is currently locked out and may not be logged on to” can be frustrating, especially when you believe you are entering the correct Windows password.
In many cases, the message appears because Windows has locked an account after too many unsuccessful authentication attempts. The account may become available after the configured lockout period expires, or an authorized administrator may need to unlock it.
However, a Windows account lockout is not always the same as a Microsoft account being locked online. Local accounts, Microsoft accounts, work or school accounts, and Active Directory accounts can require different recovery methods.
This guide explains what the error means, why it happens, how long a Windows account may stay locked, how to fix it, and what to investigate when the account keeps locking again.
Quick Answer
If “The referenced account is currently locked” appears, Windows or a connected authentication system is refusing the sign-in because the account is currently in a locked state. Stop repeated attempts, identify the account type, wait for the applicable lockout period if one exists, and use the correct recovery path. If the problem returns after access is restored, investigate stale credentials, services, tasks, and other devices.
Key Takeaways
- Too many failed sign-in attempts can trigger an account lockout.
- Entering the correct password does not automatically work while the account remains locked.
- Windows does not have one universal lockout duration for every device.
- Microsoft accounts, local accounts, and domain accounts require different recovery methods.
- Repeated lockouts can be caused by old passwords stored on another device, service, task, or network resource.
- Event ID 4740 and Event ID 4625 can help administrators investigate recurring domain authentication problems.
What Does “The referenced account is currently locked” Mean?
The full Windows message commonly appears as:
“The referenced account is currently locked out and may not be logged on to.”
It means the account Windows is attempting to authenticate is currently in a locked state.
When “The referenced account is currently locked” appears, the important point is that the account state not just the password you are typing may be blocking access.
Windows account-lockout policies can control how many unsuccessful attempts are allowed, how long the account stays locked, and when the failed-attempt counter resets.
A simplified process looks like this:
Failed sign-in attempts → lockout threshold reached → account locked → lockout expires or administrator unlocks account
For example, if a system is configured to lock an account after 10 unsuccessful attempts, reaching that threshold can prevent additional authentication until the applicable lockout condition is cleared.
What Is the “Referenced Account”?
The phrase referenced account generally means the account involved in the authentication request.
On a personal PC, this may simply be the Windows account you are trying to use.
In network environments, however, authentication may involve another computer, server, shared folder, domain, application, or remote resource.
Therefore, the message does not automatically mean that your Windows profile is damaged.
Does the Error Mean Your Password Is Wrong?
Not necessarily.
Your password can be correct while the account itself remains locked.
That is why “The referenced account is currently locked” can continue to appear even after you enter the correct password.
If Windows has already placed the account into a locked state, repeatedly entering the correct password may still fail until the lockout expires or an authorized administrator clears it.
Why Does the Referenced Account Become Locked?
Several situations can trigger or contribute to the error.
The exact reason “The referenced account is currently locked” appears depends on which account is being authenticated and where the failed attempts originate.
Too Many Incorrect Password Attempts
Repeated unsuccessful sign-in attempts are one of the most common causes.
For many personal PCs, “The referenced account is currently locked” follows a series of failed password attempts that reached the configured threshold.
This may happen because:
- You forgot the password.
- You mistyped it several times.
- Caps Lock was enabled.
- Num Lock affected your input.
- The keyboard language changed.
- The keyboard layout changed.
- Someone else attempted to sign in.
- You entered an old password after changing it.
Account-lockout policies are designed partly to restrict repeated authentication attempts.
Another Device Is Using an Old Password
This is especially important when the account becomes locked repeatedly.
Suppose you change your account password on your main computer, but another device still has the old password saved.
That device may continue trying to authenticate automatically.
The result can be:
Password changed → old credential remains stored → repeated failed authentication → account locked again
Possible sources include:
- Another desktop PC
- Laptop
- Phone
- Tablet
- Remote workstation
- Network application
- Backup software
- Mapped network drive
- Shared folder connection
If your account becomes locked again shortly after you regain access, stale credentials should be investigated.
A recurring “The referenced account is currently locked” message often points to an old password still being used somewhere else.
A Service or Scheduled Task Uses Old Credentials
Background processes can authenticate without you manually entering a password.
Examples include:
- Windows services
- Scheduled tasks
- Scripts
- Backup jobs
- Database services
- Monitoring applications
- Network applications
A service configured with an old password may repeatedly fail authentication and contribute to recurring lockouts.
In that situation, “The referenced account is currently locked” may appear even though the user is no longer entering the wrong password manually.
A Domain Account Is Locked
On a company or school computer, the affected account may be managed through Active Directory or another organizational identity system.
In that situation, local Windows settings may not control the lockout.
An authorized administrator may need to unlock the account centrally and investigate the source of the failed authentication attempts.
On a domain-managed PC, “The referenced account is currently locked” is therefore often an IT administration issue rather than a local Windows setting problem.
The Account Is Disabled Rather Than Locked
A disabled account and a locked account are different conditions.
A locked account is commonly associated with failed authentication attempts.
A disabled account has usually been administratively disabled.
The troubleshooting method therefore depends on the actual account state.
Do not assume “The referenced account is currently locked” means the account was disabled, because those are different conditions.
The Problem Appears After Sleep or Resume
Sometimes the lockout message appears immediately after waking a laptop or desktop computer.
That does not necessarily mean sleep caused the problem.
Instead, the timing may indicate that a device, service, application, saved credential, or network connection attempted authentication while the computer was sleeping or reconnecting.
Windows Account Lockout vs. Microsoft Account Lock
These situations should not be treated as identical.
Before fixing “The referenced account is currently locked”, confirm whether the affected identity is a local, Microsoft, work or school, or Active Directory account.
| Situation | What Is Locked? | Typical Recovery Path |
|---|---|---|
| Windows local-account lockout | Local Windows account | Wait, use account recovery, or use an authorized administrator |
| Active Directory lockout | Domain account | Administrator unlocks and investigates |
| Microsoft account locked online | Microsoft online account | Microsoft account recovery |
| Account disabled | Administratively disabled account | Authorized administrator re-enables it |
| Forgot Windows Hello PIN | Device sign-in credential | PIN recovery |
| Forgot password | Account credential | Password reset or recovery |
Microsoft provides different recovery procedures depending on whether the problem involves a local Windows password, Windows Hello PIN, Microsoft account, or organization-managed account.
How to Tell Which Type of Account You Are Using
Identifying the account type should come before changing security settings.
Local Windows Account
A local account exists on that specific computer and is managed locally.
Microsoft Account
A Microsoft account is normally associated with an email address and Microsoft’s online services.
Work or School Account
A work or school account may be managed by an organization’s identity and device-management systems.
Active Directory Domain Account
A domain account is centrally managed through an organization’s domain environment.
The distinction matters because the same-looking sign-in problem can require completely different recovery steps.
Correctly identifying the account type makes “The referenced account is currently locked” much easier to troubleshoot without changing unrelated settings.
How Long Does a Windows Account Stay Locked?
There is no universal lockout period for every Windows computer.
So when “The referenced account is currently locked” appears, waiting a fixed 30 minutes is not guaranteed to solve the problem.
The configured Account lockout duration determines how long an account remains locked before automatically becoming available again.
Microsoft documents configurable lockout behavior, and a duration of zero can mean that administrator intervention is required before the affected account becomes available again.
Is 30 Minutes the Windows Default?
You should not assume that every Windows account unlocks after 30 minutes.
Microsoft’s Windows 11 security guidance describes secure-by-default settings for newly installed Windows 11 devices that include:
- 10 failed sign-in attempts
- 10-minute account lockout duration
- 10-minute reset counter
- Administrator account lockout enabled by default
However, actual settings can differ depending on local policy, organizational configuration, security baselines, domain policies, and device-management rules.
Windows Account Lockout Settings Explained
Three settings are particularly important.
| Setting | What It Controls |
|---|---|
| Account lockout threshold | Number of unsuccessful attempts allowed before lockout |
| Account lockout duration | How long the account remains locked |
| Reset account lockout counter after | How long before the failed-attempt counter resets |
For example:
Configuration A
- Threshold: 10 attempts
- Duration: 10 minutes
- Reset counter: 10 minutes
Configuration B
- Threshold: 5 attempts
- Duration: 30 minutes
- Reset counter: 15 minutes
These configurations behave differently, which is why the threshold alone does not tell you everything about an account lockout.
Understanding all three settings helps explain why “The referenced account is currently locked” may clear quickly on one PC but remain active much longer on another.
How to Fix “The referenced account is currently locked”
Start with the least disruptive solutions before changing policies or considering major recovery options.
The safest way to handle “The referenced account is currently locked” is to begin with simple checks and move to administrative troubleshooting only when necessary.
Fix 1: Stop Repeatedly Trying the Password
Once Windows displays the account-lockout message:
- Stop guessing passwords.
- Verify which account you are trying to use.
- Check whether another sign-in method is available.
- Wait for the configured lockout period if automatic unlocking is enabled.
- Use the appropriate recovery method if necessary.
Repeated attempts can make troubleshooting more difficult.
If “The referenced account is currently locked” is already displayed, repeatedly testing passwords is usually less useful than confirming the account type and lockout policy.
Fix 2: Check Caps Lock, Num Lock, and Keyboard Layout
Before assuming that Windows is rejecting a valid password, verify the input.
Check:
- Caps Lock
- Num Lock
- Keyboard language
- Keyboard layout
- Special characters
- Username
- Domain name
- Whether you are entering a password or PIN
Keyboard-layout changes are particularly important when a password contains symbols.
Fix 3: Restart Windows
Restarting can resolve temporary Windows sign-in problems.
From the lock screen:
- Select the Power icon.
- Choose Restart.
- Allow Windows to start normally.
- Try the correct sign-in method once.
A restart does not guarantee that a policy-based account lockout will be removed.
In other words, “The referenced account is currently locked” can remain after a reboot when the underlying lockout state is still active.
If the account is genuinely locked by policy, the configured duration or administrator action still applies.
Fix 4: Try Another Sign-In Option
Select Sign-in options on the Windows sign-in screen when available.
Depending on your computer, you may see:
- Password
- Windows Hello PIN
- Fingerprint
- Facial recognition
- Security key
A Windows Hello PIN is not the same thing as your Microsoft account password.
If the PIN is the problem, use PIN recovery rather than assuming the Microsoft account password must be reset.
Fix 5: Check Your Internet Connection
If you use a Microsoft account or an online authentication method, verify that the computer has Internet access.
From the lock screen:
- Select the network icon.
- Connect to Wi-Fi or Ethernet.
- Wait for connectivity to become active.
- Try the appropriate recovery or sign-in option.
Fix 6: Reset a Local Windows Account Password
For a local Windows account, supported password-recovery options may be available.
Depending on the account configuration:
- Select the password sign-in option.
- Choose Reset password when available.
- Answer the configured security questions.
- Create a new password.
- Try signing in again.
If another administrator account already exists on the PC, that administrator may also be able to manage the affected local user’s password.
Remember that resetting a password and clearing a lockout are not necessarily the same action.
A password reset may be appropriate in some cases, but “The referenced account is currently locked” can still require the lockout itself to expire or be cleared.
Fix 7: Reset a Microsoft Account Password
If Windows sign-in uses a Microsoft account and you have forgotten the password, use Microsoft’s official recovery options.
Possible routes include:
- I forgot my password from the Windows sign-in screen
- Available web sign-in options
- Microsoft’s online password-reset process
Avoid unofficial third-party password-reset tools when supported account-recovery options are available.
Fix 8: Unlock a Microsoft Account That Is Locked Online
A Microsoft account that is locked online is different from a local Windows account being locked by a PC security policy.
Microsoft’s recovery process may ask you to verify your identity using a security code or complete additional account-recovery steps.
Changing local Windows lockout settings will not necessarily resolve an online Microsoft account restriction.
If “The referenced account is currently locked” is actually tied to an online Microsoft account restriction, use Microsoft’s account recovery process instead of changing local policy.
Fix 9: Use Another Authorized Administrator Account
If another administrator account can already sign in to the PC, it may be used to investigate the affected local account.
An authorized administrator may be able to:
- Reset a local user’s password
- Review account status
- Inspect local users
- Check security settings
- Investigate Windows events
Only use administrator access that you are authorized to control.
Fix 10: Use net user to Inspect a Local Account
Windows includes the net user command for managing and displaying user-account information.
To list users:
net user
To inspect a specific account:
net user username
Replace username with the actual Windows account name.
Do not assume that every net user command clears an account lockout.
For example:
net user username /active:yes
controls whether a local account is active. Account activation and account lockout are not the same condition.
Fix 11: Check Local Account Lockout Policy
On supported Windows editions, open Local Security Policy using:
secpol.msc
Then go to:
Account Policies → Account Lockout Policy
Review:
- Account lockout threshold
- Account lockout duration
- Reset account lockout counter after
Do not change these settings blindly.
Changing security policy just to remove “The referenced account is currently locked” can create new security risks without solving the reason failed authentication is occurring.
What If secpol.msc Is Not Available?
The tool is not available in the same way on every Windows edition.
Microsoft’s documented AccountLockoutPolicy support includes Windows 11 Pro, Enterprise, Education, and IoT Enterprise.
Windows 11 Home users should focus on supported account-recovery methods, existing administrator access, and diagnosing the actual source of repeated authentication failures rather than trying to force unsupported administrative tools onto the system.
Fix 12: Review Lockout Policy Carefully
Some tutorials recommend setting the account-lockout threshold to zero.
Although a threshold of zero can disable lockout under the applicable policy, doing so also removes protection against repeated password-guessing attempts.
Before changing account-lockout policy, consider:
- Who owns and controls the device
- Whether it is domain joined
- Whether organizational management controls the setting
- Why the account is becoming locked
- What security trade-offs the change creates
Fix 13: Contact IT for a Work or School Account
If the computer belongs to an organization:
- Stop repeatedly trying the password.
- Wait for automatic unlock if that is normal for your organization.
- Contact IT if access is not restored.
- Mention any recent password changes.
- Tell IT if the account becomes locked again after being unlocked.
Do not modify enterprise security policies unless you are authorized to administer them.
Fix 14: Unlock an Active Directory Account
An authorized Active Directory administrator can use Microsoft’s Unlock-ADAccount PowerShell cmdlet.
Example:
Unlock-ADAccount -Identity username
Unlocking the account may restore access, but it does not necessarily explain why the account became locked.
If the problem returns, administrators should investigate the source of the failed authentication attempts.
When “The referenced account is currently locked” returns soon after an Active Directory unlock, the next step should be finding the system that is still sending bad credentials.
Why Does the Account Keep Locking After You Unlock It?
Repeated lockouts usually deserve more investigation than a simple password reset.
Imagine this situation:
- 9:00 AM: Administrator unlocks the account.
- 9:03 AM: User signs in successfully.
- 9:10 AM: Account becomes locked again.
That pattern suggests another process may still be attempting authentication.
Possible sources include:
- Another computer
- Phone or tablet
- Stored credentials
- Scheduled task
- Windows service
- Mapped network drive
- Backup software
- Remote workstation
- Application
- Script
- Network share
- Database service
- Monitoring software
If a lockout repeatedly returns shortly after access is restored, finding the source of those authentication attempts is usually more useful than repeatedly unlocking the account.
This is especially true when “The referenced account is currently locked” appears multiple times in the same day.
How to Find What Is Causing the Account Lockout
Recurring account lockouts often require investigating authentication logs and stored credentials.
For recurring “The referenced account is currently locked” problems, Windows security events can provide much better clues than guessing at settings.
Check Event ID 4740
Microsoft documents Windows Security Event ID 4740 as:
“A user account was locked out.”
In a domain environment, administrators can inspect:
Event Viewer → Windows Logs → Security
Then search for:
Event ID 4740
Useful information may include:
- Account that was locked
- Caller Computer Name
- Time of the event
The caller computer information can provide an important clue about the device associated with the authentication attempt.
That makes Event ID 4740 particularly useful when “The referenced account is currently locked” keeps appearing in an Active Directory environment.
Check Event ID 4625
Windows Security Event ID 4625 represents a failed logon.
It may contain information such as:
- Account name
- Logon type
- Workstation name
- Source network address
- Process name
- Failure status
Common logon types include:
| Logon Type | Meaning |
|---|---|
| 2 | Interactive sign-in |
| 3 | Network logon |
| 4 | Batch process |
| 5 | Service |
| 7 | Workstation unlock |
| 10 | Remote interactive or RDP |
| 11 | Cached interactive |
These details can help determine whether the failed authentication originated from a user, service, scheduled task, network connection, or remote session.
Event ID 4625 is also valuable when “The referenced account is currently locked” needs to be traced back to repeated failed logons.
Check Stored Credentials With cmdkey
Windows provides the cmdkey command for viewing and managing stored credentials.
To list stored entries:
cmdkey /list
If a legitimate resource contains an outdated password, the relevant saved credential may need to be updated or removed.
Do not delete every saved credential indiscriminately.
Removing credentials can interrupt access to applications, servers, or network resources that depend on them.
Check Scheduled Tasks
Open Task Scheduler and inspect tasks configured to run using the affected account.
If the account password changed recently, an old password stored in a task configuration may generate recurring authentication failures.
Check Windows Services
Review Windows services configured to run under the affected user account.
A service that still stores the previous password can continue attempting authentication even when the user is entering the new password correctly.
This explains why “The referenced account is currently locked” can seem random when the real cause is a background process.
Special Account Lockout Scenarios
Some occurrences of the message require slightly different troubleshooting.
Error When Accessing a Shared Folder
The error does not always occur on the Windows desktop sign-in screen.
It can appear when connecting to another computer or shared network resource.
Check:
- Which computer hosts the resource
- Which username is being used
- Whether stored credentials exist
- Whether the remote computer uses a local account
- Whether the account is domain managed
- Whether the password recently changed
The referenced account may belong to the authentication context used for the remote resource rather than the account currently displayed on your desktop.
When “The referenced account is currently locked” appears while opening a shared folder, check the credentials being sent to that remote resource.
Error After Sleep or Closing the Laptop Lid
If the error appears immediately after waking the computer, use that timing as a troubleshooting clue.
Ask:
- Did another device attempt authentication?
- Did a network connection reconnect?
- Is a background application running?
- Was the account password recently changed?
- Are failed authentication events recorded around the same time?
- Does the problem happen after a full shutdown and restart?
Sleep itself may not be the root cause.
Can Safe Mode Fix the Lockout?
Safe Mode can help diagnose certain Windows problems, including issues involving startup applications, drivers, or services.
However, it is not a universal account-lockout bypass.
If an account is genuinely locked through local or domain policy, entering Safe Mode does not automatically clear that security state.
Safe Mode can help with diagnosis, but “The referenced account is currently locked” should not be treated as a problem that Safe Mode automatically bypasses.
Windows 11 Home Users
Windows 11 Home users may encounter tutorials that instruct them to open secpol.msc.
That tool may not be available on their edition.
Instead, prioritize:
- Official account recovery
- Local-account password recovery
- Another authorized administrator account
- Waiting for automatic lockout expiration
- Investigating stored credentials and other devices if the problem returns
Avoid downloading unofficial utilities simply to imitate enterprise administration tools.
What About Windows 10?
The general troubleshooting principles are similar, but Windows 10 should no longer be treated as Microsoft’s standard current desktop platform.
Microsoft ended standard Windows 10 support on October 14, 2025, although extended-security arrangements may apply in some environments.
Should You Disable Account Lockout?
Disabling account lockout is sometimes presented as an easy fix, but it changes the device’s security posture.
Account lockout helps reduce repeated password-guessing attempts.
Compare the main options:
| Approach | Possible Benefit | Main Trade-Off |
|---|---|---|
| Keep lockout enabled | Helps protect against repeated guessing | Accidental lockouts can occur |
| Increase threshold | Allows more failed attempts | More password attempts are permitted |
| Adjust duration | Changes recovery time | Alters security and usability balance |
| Disable lockout | Prevents policy-based lockouts | Removes an important protection |
For company or school devices, organizational security policies should be followed.
Is Setting the Threshold to 0 a Good Permanent Fix?
Setting the threshold to zero addresses only one narrow issue: lockouts caused by that particular policy.
It does not fix:
- Forgotten passwords
- Old credentials stored elsewhere
- Compromised passwords
- Misconfigured services
- Domain authentication problems
- Microsoft account restrictions
- Repeated attempts from other systems
Finding the source of repeated failed authentication is usually a more meaningful long-term solution.
Account Locked vs. Account Disabled vs. Wrong Password
These conditions are easy to confuse.
| Condition | Meaning | Typical Response |
|---|---|---|
| Account locked | Lockout policy has been triggered | Wait or unlock |
| Account disabled | Administrator disabled the account | Authorized administrator re-enables it |
| Wrong password | Credential does not match | Verify or reset password |
| Forgot PIN | Windows Hello PIN issue | Use PIN recovery |
| Microsoft account locked | Online Microsoft account restriction | Use Microsoft account recovery |
A password reset can solve a forgotten password without necessarily being the action that clears an existing lockout.
Password vs. PIN vs. Account Lockout
A Windows PIN and password are not interchangeable concepts.
| Credential or State | What It Is | Typical Recovery |
|---|---|---|
| Windows password | Account credential | Password change or recovery |
| Windows Hello PIN | Device sign-in credential | PIN reset or recovery |
| Fingerprint | Windows Hello biometric method | Use another sign-in option |
| Facial recognition | Windows Hello biometric method | Use another sign-in option |
| Account lockout | Account security state | Wait or have the account unlocked |
Identify which problem you actually have before resetting credentials.
Do You Need to Reset Windows?
Usually, no.
A normal account lockout alone is not a good reason to reinstall or reset Windows.
In most cases, “The referenced account is currently locked” can be handled without resetting the entire PC.
Try less destructive recovery options first, including:
- Waiting for the configured lockout period
- Official account recovery
- Another administrator account
- Domain administrator assistance
- Investigating repeated authentication failures
Resetting Windows is significantly more disruptive.
Before using Windows Reset, make sure you understand:
- Which files are backed up
- Which applications need to be reinstalled
- Whether BitLocker recovery information is available
- Which Microsoft or work accounts will be required afterward
Resetting the PC should generally be a last resort.
Real-World Account Lockout Examples
Example 1: Personal Windows 11 PC
Imagine you accidentally enter the wrong password several times.
Windows reaches the configured lockout threshold and displays:
“The referenced account is currently locked out and may not be logged on to.”
A sensible troubleshooting order is:
- Stop entering passwords.
- Check Caps Lock and keyboard layout.
- Wait for the applicable lockout period.
- Restart if appropriate.
- Use local-account recovery if you forgot the password.
- Use another authorized administrator account if one is available.
Reinstalling Windows should not be your first response.
Example 2: Work or Domain Laptop
Suppose an employee recently changed a domain password.
The user can sign in successfully, but the account becomes locked again.
An old password may still be stored in:
- A scheduled task
- Windows service
- Another workstation
- Network connection
- Saved credential
The administrator should identify and update the stale credential rather than repeatedly unlocking the account.
Example 3: Microsoft Account
Suppose a Windows PC uses a Microsoft account and Microsoft’s online service reports that the account itself is locked.
Changing a local Windows account-lockout policy would not necessarily resolve that restriction.
Use Microsoft’s account-recovery process instead.
Common Fixes That May Not Work
Several common suggestions are often presented as universal solutions even though they do not work in every situation.
- “Just wait 30 minutes.” The actual lockout duration depends on policy.
- “Reset your password.” Changing a password does not necessarily clear every lockout state.
- “Boot into Safe Mode.” Safe Mode is not a universal security-policy bypass.
- “Set the threshold to 0.” This changes security policy rather than identifying the underlying problem.
- “Delete the Windows profile.” A normal lockout does not mean the user profile is damaged.
- “Change the system clock.” Altering system time does not reliably resolve the underlying account state.
- “Use a third-party password bypass.” Official account-recovery options are preferable when available.
How to Prevent the Account From Locking Again
Once you regain access, focus on preventing the same problem from returning.
Use a Strong, Unique Password
Avoid weak or reused passwords.
A unique password reduces the risk that a credential exposed elsewhere will affect your Windows or Microsoft account.
Consider Windows Hello
On supported hardware, Windows Hello can provide alternative sign-in options such as:
- PIN
- Fingerprint
- Facial recognition
Update Old Credentials After Changing Your Password
Whenever an account password changes, update legitimate applications and services that may have stored the previous credential.
Check:
- Other computers
- Network drives
- Scheduled tasks
- Windows services
- Backup tools
- Remote applications
Review Saved Credentials
Use Credential Manager or appropriate Windows credential-management tools to identify outdated saved credentials.
The cmdkey /list command can also help display stored entries.
Investigate Unexpected Lockouts
If an account starts locking without an obvious reason, treat the problem as a diagnostic warning.
Do not simply increase the threshold without identifying where the failed authentication attempts originate.
Preventing “The referenced account is currently locked” from returning is mainly about fixing stale credentials and repeated failed authentication at the source.
Troubleshooting Checklist
If you see “The referenced account is currently locked”, work through these steps:
- Stop repeatedly entering the password.
- Check Caps Lock and Num Lock.
- Verify the keyboard language and layout.
- Confirm the correct username and account.
- Determine whether you are using a password or PIN.
- Identify whether the account is local, Microsoft, work/school, or domain managed.
- Wait for the configured lockout duration where appropriate.
- Restart Windows if a temporary sign-in issue is possible.
- Use official password or PIN recovery when needed.
- Contact IT for organization-managed accounts.
- Check Event ID 4740 and Event ID 4625 for recurring domain lockouts.
- Review stored credentials, scheduled tasks, services, and other devices if the lockout returns.
Frequently Asked Questions
1. Why Does Windows Say “The referenced account is currently locked”?
Windows usually displays the message when the account has entered a locked state after reaching the applicable failed-authentication threshold. Access may return automatically after the configured duration or require administrator intervention.
2. How Long Does the Referenced Account Stay Locked?
There is no universal duration. The lockout period depends on the device or organization’s configured account-lockout policy.
3. Is 30 Minutes the Windows Default?
No universal 30-minute value should be assumed. Microsoft’s current Windows 11 security guidance describes a secure-by-default configuration for new Windows 11 devices that includes a 10-minute lockout period, but actual configurations can vary.
4. Why Is My Account Locked Even Though My Password Is Correct?
The account may already have been locked before you entered the correct password. Another device, service, application, scheduled task, or stored credential may also be submitting an outdated password.
5. Can Restarting Windows Unlock the Account?
Restarting may resolve temporary sign-in problems, but it does not guarantee that a policy-based account lockout will be removed.
6. Why Does My Account Keep Locking Again?
Recurring lockouts can occur when another computer, service, application, scheduled task, network resource, or stored credential continues using an old or incorrect password.
7. What Is Event ID 4740?
Event ID 4740 is a Windows Security event associated with an account being locked out. In domain environments, it can help administrators identify the affected account and sometimes the computer associated with the authentication attempt.
8. How Do I Permanently Fix “The referenced account is currently locked”?
The long-term solution depends on the cause. If the problem keeps returning, identify the device, service, task, application, network resource, or saved credential generating unsuccessful authentication attempts rather than simply unlocking the account repeatedly.
A lasting fix for “The referenced account is currently locked” comes from removing the source of the bad authentication attempts, not just clearing each lockout after it occurs.
Final Thoughts
The referenced account is currently locked message usually means Windows or an organization-managed authentication system has placed an account into a locked state after unsuccessful authentication attempts.
For a personal Windows PC, start with simple troubleshooting. Stop repeated sign-in attempts, verify the keyboard and credentials, identify the account type, wait for the applicable lockout duration, and use Microsoft’s supported recovery options when necessary.
For a work or school computer, an authorized administrator may need to unlock the account and investigate the authentication source.
Most importantly, if the account keeps locking after access is restored, do not treat the lockout itself as the root problem. Investigate what continues to generate the failed authentication attempts.
Stored credentials, services, scheduled tasks, other devices, network resources, and authentication events such as Event ID 4740 and Event ID 4625 can provide valuable clues.
Avoid risky registry modifications, unofficial password-bypass utilities, and blanket recommendations to disable account lockout. The safer approach is to identify the account type, understand the applicable security policy, and use the supported recovery process for that environment.
