What the Status and Sub Status codes in Windows Event ID 4625 mean (0xC000006A, 0xC0000064, 0xC000006D, 0xC0000234, 0xC0000072 and more), how to read the logon type and source address, and the matching 4776 and 4771 codes.
Home › Guides › 4625 status codes
Last updated 18 November 2026
Event ID 4625 (An account failed to log on) is logged on the computer where the logon attempt was made. Status is the reason the logon failed and Sub Status adds detail. Both are NTSTATUS values. The ones you will see most:
0xC000006A: right user name, wrong password.0xC0000064: the user name doesn't exist.0xC000006D: generic logon failure (bad user name or authentication information); read Sub Status for the specific reason.0xC0000234: the account is locked out. Find the source with the Event ID 4740 lockout guide.0xC0000072: the account is disabled. 0xC0000193: the account has expired. 0xC0000071: the password has expired.Search any event ID in the Windows Event ID Lookup.
The names and descriptions are from Microsoft's NTSTATUS reference ([MS-ERREF] 2.3.1). The last column says where Microsoft's audit documentation lists the code: the 4625 monitoring table, or the 4776 NTLM error code table (the same values appear in 4625 Status and Sub Status).
| Code | NTSTATUS name | Meaning | Listed for |
|---|---|---|---|
0xC000005E | STATUS_NO_LOGON_SERVERS | No logon servers are currently available to service the logon request. | 4625 |
0xC0000064 | STATUS_NO_SUCH_USER | The specified account does not exist. | 4625, 4776 |
0xC000006A | STATUS_WRONG_PASSWORD | Misspelled or bad password. | 4625, 4776 |
0xC000006D | STATUS_LOGON_FAILURE | The attempted logon is invalid, due to a bad username or authentication information. For 4776 Microsoft also lists a LAN Manager Authentication Level mismatch between source and target as a cause. | 4625, 4776 |
0xC000006F | STATUS_INVALID_LOGON_HOURS | Logon outside the account's authorized hours. | 4625, 4776 |
0xC0000070 | STATUS_INVALID_WORKSTATION | Logon from a workstation the account isn't allowed to use. | 4625, 4776 |
0xC0000071 | STATUS_PASSWORD_EXPIRED | The user account password has expired. | 4776 |
0xC0000072 | STATUS_ACCOUNT_DISABLED | The account is disabled. | 4625, 4776 |
0xC000015B | STATUS_LOGON_TYPE_NOT_GRANTED | The user hasn't been granted the requested logon type (logon right) on this machine. | 4625 |
0xC0000192 | STATUS_NETLOGON_NOT_STARTED | An attempt was made to log on, but the Netlogon service was not started. | 4625 |
0xC0000193 | STATUS_ACCOUNT_EXPIRED | The user account has expired. | 4625, 4776 |
0xC0000224 | STATUS_PASSWORD_MUST_CHANGE | The password must be changed before logging on (Change Password at Next Logon is set). | 4776 |
0xC0000234 | STATUS_ACCOUNT_LOCKED_OUT | The account has been automatically locked because of too many invalid logon or password change attempts. | 4625, 4776 |
0xC0000371 | STATUS_NO_SECRETS | The local account store does not contain secret material for the specified account. | 4776 |
0xC0000413 | STATUS_AUTHENTICATION_FIREWALL_FAILED | The machine is protected by an authentication firewall and the account is not allowed to authenticate to it. | 4625 |
Microsoft's sample 4625 event shows Status 0xC0000234 with Failure Reason Account locked out and Sub Status 0x0. For any code not in this table, look it up in the NTSTATUS Values list that the 4625 page refers to.
From Microsoft's monitoring recommendations for 4625 and 4776:
0xC0000064 events in a row can be a sign of a user enumeration attack.0xC000006A or 0xC000006D against critical or service accounts can indicate a brute-force password attack.0xC000005E (no logon servers) and 0xC0000192 (Netlogon not started) are typically not security issues but can be infrastructure or availability issues.| Field (XML name) | What it means |
|---|---|
Account For Which Logon Failed (TargetUserName, TargetDomainName) | The account specified in the logon attempt. |
Logon Type (LogonType) | 2 interactive, 3 network, 4 batch, 5 service, 7 unlock, 8 network cleartext, 9 new credentials, 10 remote interactive (Remote Desktop), 11 cached interactive. |
Caller Process Name (ProcessName) | Full path of the executable that attempted the logon, for example C:\Windows\System32\winlogon.exe in Microsoft's sample. |
Workstation Name (WorkstationName) | Machine name the attempt was performed from. |
Source Network Address (IpAddress) | IP address the attempt came from: IPv6 or ::ffff: plus an IPv4 address. ::1 or 127.0.0.1 means localhost. |
Source Port (IpPort) | 0 for interactive logons. |
| Authentication Package / Package Name | Negotiate picks Kerberos unless it can't be used, then NTLM. Package Name (NTLM V1, NTLM V2 or LM) is filled in only for NTLM. |
Microsoft suggests comparing Source Network Address with the list of addresses an account is allowed to use. Check whether an address is inside a range with the IPv4 Subnet Calculator or IPv6 Subnet Calculator, and see who owns a public address with the ASN IP Lookup or Cloud IP Lookup.
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4625; StartTime=(Get-Date).AddHours(-24)} |
ForEach-Object {
$d = @{}
([xml]$_.ToXml()).Event.EventData.Data | ForEach-Object { $d[$_.Name] = $_.'#text' }
[pscustomobject]@{ User=$d.TargetUserName; Status=$d.Status; SubStatus=$d.SubStatus
LogonType=$d.LogonType; Source=$d.IpAddress; Process=$d.ProcessName }
} |
Group-Object User, Status, SubStatus, Source |
Sort-Object Count -Descending |
Format-Table Count, Name -AutoSize
The field names match Microsoft's sample event XML (Status, SubStatus, LogonType, IpAddress, ProcessName). Add -ComputerName to query another machine (one at a time; the event log service must be reachable through its firewall). The values come back as hex strings such as 0xc000006a, so compare them case-insensitively. To pull out unusual lines from an exported log, try patterns in the Regex Tester, and keep the query in the PowerShell Cheat Sheet.
When Kerberos is used, a bad password on a domain account shows on the domain controller as 4771 (Kerberos pre-authentication failed), which is generated only on DCs. Its Failure Code uses the RFC 4120 values. The ones Microsoft gives causes for:
| Code | Name | Meaning |
|---|---|---|
0x6 | KDC_ERR_C_PRINCIPAL_UNKNOWN | Client not found in Kerberos database. |
0x10 | KDC_ERR_PADATA_TYPE_NOSUPP | Smart card logon is being attempted and the proper certificate can't be located, or the DC has no certificate for smart cards. |
0x12 | KDC_ERR_CLIENT_REVOKED | Client's credentials have been revoked. |
0x17 | KDC_ERR_KEY_EXPIRED | The user's password has expired. |
0x18 | KDC_ERR_PREAUTH_FAILED | The wrong password was provided. |
0x25 | KRB_AP_ERR_SKEW | Clock skew too great. |
Pre-Authentication Type 2 (PA-ENC-TIMESTAMP) is normal for standard password authentication and 15 is used for smart card logon. 4771 isn't generated if Do not require Kerberos preauthentication is set for the account.
Look up related event IDs in the Windows Event ID Lookup, save the query in the PowerShell Cheat Sheet, check source addresses with the IPv4 Subnet Calculator, IPv6 Subnet Calculator, ASN IP Lookup and Cloud IP Lookup, and test log-parsing patterns in the Regex Tester. Related guides: find the source of an account lockout (4740), the trust relationship between this workstation and the primary domain failed and KRB_AP_ERR_MODIFIED (Kerberos event 4).
The user name exists but the password was wrong. Microsoft's NTSTATUS reference calls it STATUS_WRONG_PASSWORD, and the 4625 page says to watch for a number of these in a row against critical or service accounts.
Microsoft defines Status as the reason the logon failed and Sub Status as additional information about the failure. If Status is the generic 0xC000006D (bad user name or authentication information), Sub Status can give the specific reason, for example 0xC000006A for a wrong password or 0xC0000064 for a user that does not exist.
STATUS_ACCOUNT_LOCKED_OUT: the account was automatically locked because of too many invalid logon or password change attempts. Find the computer causing it from event 4740 on the PDC emulator.
On the computer where the logon attempt was made, for example the workstation for a local sign-in or the server for a network logon. It is generated on domain controllers, member servers and workstations, in the Audit Logon and Audit Account Lockout subcategories.
STATUS_LOGON_TYPE_NOT_GRANTED: the user has not been granted the requested logon type, such as interactive or network logon, on that machine. Check the user rights assignment for the logon type shown in the event.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.