What does NTSTATUS 0xC0000083 (STATUS_GUIDS_EXHAUSTED) mean?

 
Previous Next
STATUS_TOO_MANY_GUIDS_REQUESTED STATUS_INVALID_ID_AUTHORITY

STATUS_GUIDS_EXHAUSTED

This is allocator-state exhaustion, not ordinary UUID collision handling

STATUS_GUIDS_EXHAUSTED uses the historical phrase “Authority Agent” in the Windows NTSTATUS definition. The safest interpretation is narrow: the legacy allocation component reported that its authority-agent allocation state was exhausted. The public status catalog does not define the internal counter layout or recovery algorithm.

That distinction matters because modern UUID generation is specified in terms of UUID versions, fields, randomness, time/order properties, and uniqueness considerations. Windows RPC exposes UUID creation independently. It would be incorrect to conclude from this status that all possible GUIDs have been consumed or that a normal UuidCreate loop reached the end of the 128-bit space.

Preserve the subsystem version, allocator database/state, authority identity, and the last successful allocation. If the component persists allocation state, inspect recovery and restore history before resetting anything. Regenerating IDs from a different algorithm can violate the consumer’s namespace assumptions. Because the internal authority-agent mechanism is not publicly specified in the common NTSTATUS catalog, remediation should follow the owning subsystem’s documentation rather than inventing a reset procedure.

What to inspect

  • Identify the exact legacy component that owns the authority-agent state.
  • Preserve allocator state and recovery history before attempting repair.
  • Do not interpret the result as exhaustion of the global 128-bit UUID namespace.

References

Looking for a different code? Search another status or error code.