What does HRESULT 0x80010136 (CO_E_FAILEDTOGENUUID) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

COM could not generate a UUID for access-control persistence

Previous	Next
CO_E_PATHTOOLONG	CO_E_FAILEDTOCREATEFILE

CO_E_FAILEDTOGENUUID

COM could not generate a UUID for access-control persistence

CO_E_FAILEDTOGENUUID is HRESULT 2147549494 (0x80010136) from winerror.h. AllStat describes it as “Unable to generate a uuid.” In the COM IAccessControl, DCOM client identity, trustee translation, token inspection, security descriptor, ACL, or serialization workflow, the code identifies a specific failure boundary and should not be replaced by a generic COM exception.

Telemetry should preserve CO_E_FAILEDTOGENUUID as a separate outcome rather than merging it with unrelated COM or WinRT failures.

Decisive interpretation boundary

Before choosing recovery, verify that the UUID API result, RPC runtime state, system health, and collision-handling path are captured. That boundary prevents CO_E_FAILEDTOGENUUID from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.

For CO_E_FAILEDTOGENUUID, also confirm that all observed objects, tokens, buffers, proxies, metadata files, or ACLs belong to the current operation generation and were not retained from an earlier attempt.

Where it is encountered

CO_E_FAILEDTOGENUUID can be returned during IAccessControl initialization, access checks, owner/trustee processing, and serialized ACL persistence. For CO_E_FAILEDTOGENUUID, record the interface, method, component version, thread, apartment, process, and correlation ID.
CO_E_FAILEDTOGENUUID can be returned during server-side DCOM impersonation, client blanket inspection, token and SID lookup. For CO_E_FAILEDTOGENUUID, record the interface, method, component version, thread, apartment, process, and correlation ID.
CO_E_FAILEDTOGENUUID can be returned during security descriptor construction, DACL canonicalization, file-backed policy storage, or legacy NetAccess migration. For CO_E_FAILEDTOGENUUID, record the interface, method, component version, thread, apartment, process, and correlation ID.

The immediate focus for CO_E_FAILEDTOGENUUID is creation of a unique identifier for serialization files, access-control objects, or temporary state. Keep CO_E_FAILEDTOGENUUID attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Diagnostic sequence

Capture the raw unsigned value 0x80010136 and symbolic name CO_E_FAILEDTOGENUUID before a language projection, exception wrapper, or generic COM helper replaces it.
Identify the exact interface, method, callback, activation request, metadata query, access-control operation, or marshaling boundary that returned CO_E_FAILEDTOGENUUID.
Reconstruct the operation timeline for CO_E_FAILEDTOGENUUID, including object creation, thread or apartment initialization, security setup, callbacks, mutations, shutdown, and cleanup.
Prove the decisive condition: the UUID API result, RPC runtime state, system health, and collision-handling path are captured.
Inspect every output parameter, handle, interface pointer, token, SID, ACL, stream, buffer, server-side object, or asynchronous result produced before CO_E_FAILEDTOGENUUID.
Reproduce CO_E_FAILEDTOGENUUID with the smallest safe input, change only the suspected precondition, and verify that both the HRESULT and postcondition change as predicted.

Evidence and telemetry

Preserve UUID generation API and native status for CO_E_FAILEDTOGENUUID.
Preserve process and machine identity for CO_E_FAILEDTOGENUUID.
Preserve generated value if any for CO_E_FAILEDTOGENUUID.
Preserve temporary object purpose for CO_E_FAILEDTOGENUUID.
Preserve retry after system repair for CO_E_FAILEDTOGENUUID.

For CO_E_FAILEDTOGENUUID, also record UTC time, process and thread IDs, apartment type, component version, security or package identity where relevant, and a correlation ID. For CO_E_FAILEDTOGENUUID, use hashes, lengths, GUIDs, and SID strings rather than logging confidential payloads or credentials.

Correct handling and recovery

Treat identifier generation as a hard precondition, repair runtime or entropy failures, and never substitute timestamps or predictable counters for security-sensitive identity.

An unchanged retry loop for CO_E_FAILEDTOGENUUID can duplicate effects, deepen reentrancy, or hide an invalid lifetime transition.

Difference from nearby HRESULTs

CO_E_FAILEDTOGENUUID precedes file creation; CO_E_FAILEDTOCREATEFILE means an identifier or path was available but opening storage failed.

The distinction around CO_E_FAILEDTOGENUUID should be represented explicitly in control flow and operational dashboards.

Lifetime, retry, and cleanup rules

After CO_E_FAILEDTOGENUUID, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. For CO_E_FAILEDTOGENUUID, release only resources owned by the failing attempt, cancel callbacks through their documented mechanism, and avoid double close, double commit, repeated activation, or replay of a non-idempotent remote method.

The retry policy for CO_E_FAILEDTOGENUUID should state the trigger, maximum attempts, cancellation owner, and reconciliation step for effects that may have completed elsewhere.

Developer and administrator guidance

When CO_E_FAILEDTOGENUUID crosses native, managed, scripting, RPC, or WinRT projection boundaries, preserve the unsigned 32-bit HRESULT. Unit tests for CO_E_FAILEDTOGENUUID should assert the code-specific postcondition and resource ownership, not merely that an exception was thrown.

For CO_E_FAILEDTOGENUUID, change the smallest component, identity, ACL, package, or threading boundary that the evidence identifies, then reproduce the same operation. Define who owns retry, cancellation, cleanup, policy changes, package repair, and user-facing messaging for CO_E_FAILEDTOGENUUID.

Practical scenario

An access-control save cannot obtain a UUID and therefore does not create a shared temporary filename. Diagnostics capture the native RPC status.

A regression test should reproduce CO_E_FAILEDTOGENUUID, assert the raw HRESULT and all relevant outputs, then correct only the decisive condition and verify the intended success or neighboring failure result.

References

Microsoft: IAccessControl — official Microsoft documentation relevant to CO_E_FAILEDTOGENUUID.
Microsoft: IAccessControl::IsAccessAllowed — official Microsoft documentation relevant to CO_E_FAILEDTOGENUUID.
Microsoft: AccessCheck — official Microsoft documentation relevant to CO_E_FAILEDTOGENUUID.
Microsoft: LookupAccountSidW — official Microsoft documentation relevant to CO_E_FAILEDTOGENUUID.
Microsoft: LookupAccountNameW — official Microsoft documentation relevant to CO_E_FAILEDTOGENUUID.
Microsoft: access control lists — official Microsoft documentation relevant to CO_E_FAILEDTOGENUUID.
Microsoft: canonical ACE order — official Microsoft documentation relevant to CO_E_FAILEDTOGENUUID.
Microsoft: HRESULT values — official Microsoft documentation relevant to CO_E_FAILEDTOGENUUID.

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