| Previous | Next |
| ERROR_SERVICE_NOT_FOUND | ERROR_NOT_LOGGED_ON |
ERROR_NOT_AUTHENTICATED
No authenticated identity was established for the operation.
ERROR_NOT_AUTHENTICATED is Win32 error 1244 (0x4DC). A protected operation reached an authentication boundary without a usable authenticated principal. This differs from a bad password: the request may have no completed security context at all, or the context may have been discarded before the operation ran.
Common situations
- an SSPI negotiation has not reached its final success state
- a connection was re-created but the application reused authorization state from the previous connection
- a service executes under an account that has local access but no delegated network identity
- an anonymous, guest, or unauthenticated request reaches an endpoint that requires a named principal
- token acquisition or impersonation ended before an asynchronous task used it
Evidence to retain
Log the authentication mechanism, package name, connection and request IDs, negotiation step, target service principal name, token type, impersonation level, and whether the request crossed a process or machine boundary. Never place passwords, PINs, raw tickets, or bearer tokens in telemetry. It is usually enough to record which credential source was selected and why no authenticated context was attached.
Diagnostic sequence
Start at the first authentication call rather than the protected operation that finally returned 1244. For SSPI, preserve every status from AcquireCredentialsHandle, InitializeSecurityContext, or AcceptSecurityContext and confirm that continuation statuses were handled correctly. Verify that the final context belongs to the same connection on which the operation was sent.
For service code, inspect the process account, impersonation transitions, delegation requirements, and access to credentials in noninteractive sessions. A successful interactive desktop sign-in does not guarantee that a background service can authenticate to a remote resource using the same identity.
Recovery and retry
Restart the authentication exchange with a fresh context, then repeat the protected request only after success is explicit. Do not loop the business operation while leaving authentication unchanged. When user interaction is required, surface a sign-in action; when credentials are unavailable by design, report that limitation instead of silently falling back to anonymous access.
Related results
ERROR_LOGON_FAILURE says supplied credentials were rejected. ERROR_NOT_LOGGED_ON indicates that no network logon session exists for the requested use. Error 1244 focuses on the absence of an authenticated context at the operation boundary.
Example
A client completes the first Kerberos token exchange, receives a continuation status, and incorrectly marks the session authenticated. Its next RPC call fails with 1244. The fix is to continue exchanging SSPI tokens until the security context reports final success and only then enable authenticated commands.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: Noninteractive Authentication
- Microsoft: InitializeSecurityContext
- Microsoft: LSA User Logon Authentication
Looking for a different code? Search another status or error code.