| Previous | Next |
| STATUS_NO_SUCH_LOGON_SESSION | STATUS_PRIVILEGE_NOT_HELD |
STATUS_NO_SUCH_PRIVILEGE
The privilege itself is not a valid system privilege
This result is about the identity of a privilege, not about whether the caller currently holds it. The privilege name, LUID, or policy entry does not correspond to a recognized Windows privilege.
That distinction matters: a valid privilege missing from a token is a different condition from asking LSA or the security reference monitor for a privilege that does not exist.
What to inspect
- Verify the exact privilege name such as SeBackupPrivilege or SeServiceLogonRight.
- Check spelling, localization mistakes, and use of account rights versus token privileges.
- Compare with STATUS_PRIVILEGE_NOT_HELD when the privilege is valid but absent or disabled in the caller token.
References
- Microsoft: Access tokens
- Microsoft: Configure security policy settings
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.