Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0xC0000234

0xC0000234 account locked out and other logon states that block shares

10 min read Updated October 5, 2026 Networking, Sharing & Printing

Fix it now

0xC0000234 and the status values around it are the directory refusing you, not the network. Windows deliberately shows the same vague message for all of them, so the only way to tell a lockout from an expired password or a disabled account is to read the status value in the event that recorded the attempt.

Run these from a machine with the Active Directory tools installed

Search-ADAccount -LockedOut
Unlock-ADAccount -Identity jsmith
Get-ADUser jsmith -Properties LockedOut, Enabled, PasswordExpired, AccountExpirationDate
  1. On a domain controller, open Event Viewer, Windows Logs, Security, and find event 4776 for the account. Its Error Code field carries the value you need, and Microsoft publishes a table of what each one means.
  2. On the machine that refused the connection, event 4625 carries Status and Sub Status for the same attempt. Logon Type 3 is a network logon such as a share; Logon Type 10 is Remote Desktop.
  3. Match the value against the table below, and act on that rather than on the message the user saw.
  4. For a lockout, find where the bad passwords came from before you unlock: read the lockout events on the domain controller holding the PDC emulator role and note the caller computer name.
  5. Clear the source on that machine: stored entries in Credential Manager, mapped drives, scheduled tasks and services running as the user, and mail profiles on phones.
  6. Have the user try again, and watch whether the account relocks within a few minutes.

Unlock only after you know what is submitting the old password. Unlocking first means you get to do it again in four minutes, and you will have lost the evidence of where it came from.

If the user can open the share and the account stays unlocked, you are done. If it relocks, the next section is about finding what is holding the old credential.

Why it happens

These values come from the authentication package rather than from the file sharing layer, and they are wrapped up by whatever component asked for the logon. That is why the same underlying refusal appears as a network error in Explorer, a credential prompt in an application and a rejected sign-in at the logon screen. The component reporting it does not know why the directory said no. The event log does, and Microsoft publishes what each value means.

The distinction that matters most is between a state you can clear and a state somebody chose. A lockout is a threshold being crossed and is meant to be cleared. A disabled account is usually a deliberate act by whoever manages leavers, and enabling it without asking simply undoes somebody’s decision. An expired password is policy working as intended. An account with an expiry date is a contractor arrangement reaching its end.

Network logons make one of these harder than it needs to be. When a password has expired, an interactive sign-in offers a change prompt and the user fixes it themselves in seconds. A network logon to a share has nowhere to show that prompt, so it simply fails and the user reports that the share is broken. The same is true of an account flagged to change its password at next sign-in, which Microsoft publishes as the meaning of 0xC0000224 – it is a directory flag, not a general statement that the password is unusable.

A stale credential somewhere is locking the account

You have this one if 0xC0000234, and the account relocks within minutes of every unlock.

  1. On the PDC emulator, read the lockout events and note the caller computer name, which tells you where the bad attempts originate.
  2. On that machine, clear stored credentials in Credential Manager, check net use for mappings under the old password, and look at scheduled tasks and services running as the user.
  3. Do not forget mobile devices and any application that stores the password separately, since those retry silently and endlessly.

If the caller computer name is blank or names an internet-facing service, treat it as a possible password guessing attempt rather than a stale credential, and escalate rather than unlocking on a loop.

The password has expired or must be changed

You have this one if 0xC0000071 or 0xC0000224. The same credentials work at a console sign-in, where the change prompt appears, and fail everywhere else.

  1. Have the user change the password at a console or Remote Desktop session, or through whatever self-service reset tool you run.
  2. Once changed, clear the old value from Credential Manager on every device that had it stored.
  3. Confirm the new state with Get-ADUser <name> -Properties PasswordLastSet, PasswordExpired before testing again.

The account is disabled

You have this one if 0xC0000072. The object exists and the password is unchanged, but every logon type fails identically.

  1. Confirm with Get-ADUser <name> -Properties Enabled.
  2. Find out who disabled it and why before doing anything. A leaver process and a security response look identical from here.
  3. Where it is a genuine mistake, Enable-ADAccount -Identity <name> puts it back.

The account has expired

You have this one if 0xC0000193, typically on a contractor or temporary account that worked yesterday.

  1. Check the expiry with Get-ADUser <name> -Properties AccountExpirationDate.
  2. Extend it with Set-ADAccountExpiration, or clear it with Clear-ADAccountExpiration where the arrangement is now permanent.
  3. Confirm with whoever owns the account that the extension is authorised before you make it.

The lockout is real and repeated

You have this one if Lockout events arrive from several machines, or from external-facing services, faster than any stale credential would produce them.

  1. Identify which service is receiving the attempts and whether it is reachable from the internet.
  2. Check the lockout policy: threshold, duration and reset counter, and confirm the threshold is not so low that ordinary mistakes trigger it.
  3. Where credentials are exposed to the internet, put multi-factor authentication in front of the service rather than relying on lockout as the defence.

Full reference

The status values, as Microsoft publishes them

These are the descriptions from the error code table for Security event 4776, which is the event a domain controller writes when it validates credentials for an account.

Value Published meaning What to do
0xC0000234 Account logon with account locked Find the source of the bad attempts, then unlock
0xC0000071 Account logon with expired password The user changes it at a console or through self-service
0xC0000072 Account logon to account disabled by administrator Find out why before enabling it
0xC0000193 Account logon with expired account Extend or clear the expiry date if the account is still needed
0xC0000224 Account logon with “Change Password at Next Logon” flagged A network logon cannot satisfy this. The user must sign in interactively

Which event, on which machine

Event Where it is written What it gives you
4776 The domain controller that validated the credentials An Error Code field carrying the values above
4625 The machine where the logon was attempted Status and Sub Status, the submitted account name, the logon type and the source address

You frequently need both. The controller tells you what the directory decided; the member machine tells you what was submitted and from where. Reading only one of them is why account problems take longer than they should.

Logon types worth recognising in event 4625

Type Meaning
3 Network. A user or computer logged on to this computer from the network – a share, for example
10 RemoteInteractive. A user logged on remotely using Terminal Services or Remote Desktop

That distinction settles a common confusion. Type 3 has nowhere to show a password change prompt, which is why an expired password looks like a broken share. Type 10 does, which is why telling the user to connect by Remote Desktop and change it there is often the fastest route out.

Finding what is locking an account

  1. Start on the domain controller holding the PDC emulator role. Bad password attempts across the domain are forwarded to it, so it sees what individual controllers do not.
  2. Read the caller computer name in the lockout event. That is where to go next.
  3. On that machine, work through the places a password is stored without anyone thinking about it: Credential Manager, mapped drives, scheduled tasks, services running as the user, and any application with its own credential store.
  4. Check the user’s phone. A mail profile with an old password will lock an account every few minutes, indefinitely, and nobody thinks of it because the phone shows no error.
  5. Only then unlock, and watch for a repeat over the following ten minutes.

Setting a lockout threshold very low makes accounts trivially easy to lock deliberately, and setting it to zero removes a real defence. Neither extreme is a good answer. If lockouts are frequent because of stale credentials, fix the credentials rather than the threshold.

Every code this article covers

Code What it points at Source
0xC0000234 Account logon with account locked. The account will not authenticate until it is unlocked or the lockout duration expires Microsoft Learn
0xC0000071 Account logon with expired password Microsoft Learn
0xC0000072 Account logon to account disabled by administrator Microsoft Learn
0xC0000193 Account logon with expired account Microsoft Learn
0xC0000224 Account logon with “Change Password at Next Logon” flagged, which a network logon cannot satisfy Microsoft Learn

Confirm the fix worked

  1. Get-ADUser <name> -Properties LockedOut, Enabled, PasswordExpired, AccountExpirationDate returns the values you expect.
  2. The user opens the share that failed and writes a test file.
  3. Watch the lockout events on the PDC emulator for the next hour and confirm nothing relocks the account.
  4. Confirm the machine that generated the bad attempts no longer holds the old credential.
  5. Check the user’s phone and any application with its own credential store, since those are the ones that come back later.

Questions people ask about this

Does any of this need a purchase?

No. The Active Directory tools, the event logs and the PowerShell cmdlets used here all come with Windows and the free administration tools. Nothing in this article is solved by a licence.

Why does the same account work on one machine and not another?

Usually because the working machine has a cached ticket or a saved credential from before the state changed. That is also why a reboot sometimes makes the failure appear on a machine that seemed fine.

Where are lockouts actually recorded?

Bad password attempts across the domain are forwarded to the controller holding the PDC emulator role, so that is where to look for the pattern. The attempt itself is recorded on the machine where it was made, as event 4625, and the credential validation on a controller as event 4776. You often need both.

Can I stop expired passwords breaking mapped drives?

Partly. Notify users before expiry and encourage them to change the password from a console session rather than waiting for a failure. Setting passwords never to expire is a poor trade for the convenience it buys.

What is the difference between 0xC0000071 and 0xC0000224?

Microsoft publishes the first as an expired password and the second as an account flagged for Change Password at Next Logon. Both stop a network logon for the same practical reason – there is nowhere to show the change prompt – but the second is a flag somebody set rather than an age limit being reached.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Duplicate name on the network 0x80070034 and a broken Winsock TCP stack Free Fix Error 0x0000007C: printer driver or print processor not supported by Windows License Error VPN error 809 and 800: IKE traffic blocked before the tunnel can open Free Fix Error 0x8009030C: logon denied when NTLM is blocked or restricted
โ† Back to Knowledge Base