| Previous | Next |
| ERROR_TOO_MANY_LUIDS_REQUESTED | ERROR_INVALID_SUB_AUTHORITY |
ERROR_LUIDS_EXHAUSTED
The local LUID allocator could not supply another identifier
A LUID is unique only on the local system and its uniqueness guarantee lasts only until reboot. Access-token statistics use LUIDs for TokenId, AuthenticationId, and ModifiedId, while privileges are also represented by locally meaningful LUID values. This status therefore concerns the local identifier namespace used by security and other subsystems, not Active Directory RID allocation or globally unique object identifiers.
Because normal systems should not approach this condition casually, preserve diagnostic context. Record uptime, identifier-heavy workload behavior, and the component that requested the LUID. A restart changes the local allocation epoch and may clear the immediate condition, but repeated exhaustion points to a leak, runaway creation path, or corrupted request pattern that needs investigation. Do not infer that deleting users or groups will replenish LUIDs; those accounts are represented by SIDs and use a different allocation mechanism.
What to inspect
- Record system uptime and the component performing the failed allocation.
- Look for runaway creation of tokens, logon sessions, or other LUID-consuming objects.
- Do not troubleshoot this as Active Directory RID or account-SID exhaustion.
References
Looking for a different code? Search another status or error code.