| Previous | Next |
| STATUS_TOO_MANY_LUIDS_REQUESTED | STATUS_INVALID_SUB_AUTHORITY |
STATUS_LUIDS_EXHAUSTED
The local LUID allocator could not issue a new value
LUID allocation normally advances an operating-system-maintained sequence. Exhaustion is exceptional and is different from asking for too many values in a single call. It can also reveal corruption or a broken emulation layer rather than realistic consumption by ordinary applications.
Capture the returning component and system lifetime before attempting recovery. Rebooting resets the local uniqueness interval but should not be used to conceal repeated abnormal allocation. Components must not assume LUID values survive restart or compare meaningfully between machines.
What to inspect
- Distinguish allocator exhaustion from a single oversized request.
- Check for loops allocating identifiers without need or retaining them as permanent IDs.
- Preserve system and component logs if the condition repeats after restart.
References
- Microsoft: LUID structure
- Microsoft: AllocateLocallyUniqueId
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.