| Previous | Next |
| STATUS_INVALID_IMPORT_OF_NON_DLL | STATUS_ACCESS_DISABLED_NO_SAFER_UI_BY_POLICY |
STATUS_NO_SECRETS
The requested account has no local secret material
STATUS_NO_SECRETS means the local security/account store does not contain the secret material required for the specified account or authentication operation. It is an account-state or credential-store result; it has nothing to do with Microsoft Store sign-in or application downloads.
What to capture
- Record the account or principal, machine role, authentication package or API, and the operation that requested the secret.
- Determine whether the account is expected to have locally stored secret material at this point in its lifecycle, especially after account creation, password/trust changes, restore, migration, or security-database recovery.
- Correlate the first SAM, LSA, Netlogon, or authentication event that accompanies the failure instead of treating a later logon error as the root cause.
Recovery
Restore or re-establish the expected account secret through the supported account, password, or trust-management path for that account type. Do not create arbitrary LSA secrets, edit the SAM directly, or reset an unrelated trust relationship merely because the symbolic name contains “secrets”.
If the account is intentionally not supposed to have local secret material, correct the caller's account selection or authentication flow. Preserve any subsequent status separately because it may identify a different validation stage.
Official references
Looking for a different code? Search another status or error code.