| Previous | Next |
| STATUS_STACK_OVERFLOW | STATUS_BAD_FUNCTION_TABLE |
STATUS_NO_SUCH_PACKAGE
Meaning and context of STATUS_NO_SUCH_PACKAGE
Windows Authentication Package identifies the Dynamic-Link Library (DLL) loaded and used by theLocal Security Authority (LSA) along with configuration information stored in the Windows registry.
Loading multiple Windows Authentication Packages permits the LSA to support multiple logon processes and multiple security protocols.
LSA Protection prevents unsigned Windows Authentication Packages from being loaded.
Important
Windows Logon use Windows Authentication Package to analyze logon data by following the rules and procedures set forth in a security protocol.Windows Authentication Package are responsible for the following tasks:
- Analyzing logon data to determine whether a security principal is allowed to Access a system or Resource.
Windows Authentication Packages provide Authentication Mechanism services by implementing package-specific functionality for the LsaLogonUser and LsaCallAuthenticationPackage functions provided by the LSA.
After a Windows Logon session is created and associated with a principal, subsequent authentication requests made on behalf of the principal are handled differently than the initial logon. The Windows Authentication Package does not create a new Windows Logon session nor return information for creating a token. The Windows Authentication Package can, however, associate supplemental credentials obtained during a subsequent authentication with the principal's existing Windows Logon session. Supplemental credentials are obtained when access to a requested resource requires information beyond the credentials established by the initial Windows Logon.
Msv1_0.dll is an example of a Windows Authentication Package which accepts a user name and a Hashed password, which it looks up in the Security Account Manager (SAM) database. Depending on the results of the lookup, the MSV1_0 Windows Authentication Package accepts or rejects the authentication attempt.
Native status interpretation
STATUS_NO_SUCH_PACKAGE is 0xC00000FE, an NTSTATUS error value. AllStat describes it as “A specified authentication package is unknown.”. The first useful question is which native API, IRP, protocol operation, or subsystem in the kernel, native API, or subsystem that returned the status produced that status.
Debugging sequence
- Preserve this result before RtlNtStatusToDosError, HRESULT conversion, exception translation, or provider-specific remapping removes information.
- Log the operation associated with such / package, the object or handle type, process and thread identity, and the state transition immediately before the return.
- When user mode receives this result, capture both the native status and the final Win32/COM error so the translation boundary remains visible.
Recovery considerations
A retry is appropriate only after the owner of this result has changed the state described by “A specified authentication package is unknown.”, or when its contract explicitly marks the status as transient. If the value reports corruption, invalid format, access policy, or a lifecycle mismatch, preserve evidence and correct that cause before repeating the request.
Official references
Looking for a different code? Search another status or error code.