What does HRESULT 0x80010137 (CO_E_FAILEDTOCREATEFILE) mean?

CO_E_FAILEDTOCREATEFILE

COM could not create its access-control serialization file

CO_E_FAILEDTOCREATEFILE is HRESULT 2147549495 (0x80010137) from winerror.h. AllStat describes it as “Unable to create file.” 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.

The caller should keep CO_E_FAILEDTOCREATEFILE intact through logging, exception translation, and RPC or language projection boundaries.

Decisive interpretation boundary

Before choosing recovery, verify that path, desired access, sharing, disposition, filesystem, service identity, and native error are known. That boundary prevents CO_E_FAILEDTOCREATEFILE from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.

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

The immediate focus for CO_E_FAILEDTOCREATEFILE is file creation for serialized ACL or IAccessControl state after path and identifier construction. Keep CO_E_FAILEDTOCREATEFILE attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Diagnostic sequence

• Capture the raw unsigned value 0x80010137 and symbolic name CO_E_FAILEDTOCREATEFILE 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_FAILEDTOCREATEFILE.
• Reconstruct the operation timeline for CO_E_FAILEDTOCREATEFILE, including object creation, thread or apartment initialization, security setup, callbacks, mutations, shutdown, and cleanup.
• Prove the decisive condition: path, desired access, sharing, disposition, filesystem, service identity, and native error are known.
• Inspect every output parameter, handle, interface pointer, token, SID, ACL, stream, buffer, server-side object, or asynchronous result produced before CO_E_FAILEDTOCREATEFILE.
• Reproduce CO_E_FAILEDTOCREATEFILE 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 target path and filesystem for CO_E_FAILEDTOCREATEFILE.
• Preserve CreateFile flags and disposition for CO_E_FAILEDTOCREATEFILE.
• Preserve process token and directory ACL for CO_E_FAILEDTOCREATEFILE.
• Preserve native last error for CO_E_FAILEDTOCREATEFILE.
• Preserve partial file and rollback state for CO_E_FAILEDTOCREATEFILE.

For CO_E_FAILEDTOCREATEFILE, 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_FAILEDTOCREATEFILE, use hashes, lengths, GUIDs, and SID strings rather than logging confidential payloads or credentials.

Correct handling and recovery

Correct directory existence and ACLs, available space, sharing conflicts, or path construction. Remove partial files and keep the prior valid serialization intact.

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

Difference from nearby HRESULTs

CO_E_FAILEDTOCREATEFILE is storage creation failure; CO_E_PATHTOOLONG identifies the path-length cause before or during creation.

A support tool discussing CO_E_FAILEDTOCREATEFILE should name the neighboring result only after the originating API and decisive state are known.

Lifetime, retry, and cleanup rules

After CO_E_FAILEDTOCREATEFILE, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. For CO_E_FAILEDTOCREATEFILE, 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_FAILEDTOCREATEFILE 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_FAILEDTOCREATEFILE crosses native, managed, scripting, RPC, or WinRT projection boundaries, preserve the unsigned 32-bit HRESULT. Unit tests for CO_E_FAILEDTOCREATEFILE should assert the code-specific postcondition and resource ownership, not merely that an exception was thrown.

After CO_E_FAILEDTOCREATEFILE, avoid broad permission grants or system-wide resets unless code-specific evidence proves a global configuration problem. Define who owns retry, cancellation, cleanup, policy changes, package repair, and user-facing messaging for CO_E_FAILEDTOCREATEFILE.

Practical scenario

A service upgrade changes the account and loses write access to its ACL store. Installation grants the application directory the minimal required rights.

A regression test should reproduce CO_E_FAILEDTOCREATEFILE, 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_FAILEDTOCREATEFILE.
• Microsoft: IAccessControl::IsAccessAllowed — official Microsoft documentation relevant to CO_E_FAILEDTOCREATEFILE.
• Microsoft: AccessCheck — official Microsoft documentation relevant to CO_E_FAILEDTOCREATEFILE.
• Microsoft: LookupAccountSidW — official Microsoft documentation relevant to CO_E_FAILEDTOCREATEFILE.
• Microsoft: LookupAccountNameW — official Microsoft documentation relevant to CO_E_FAILEDTOCREATEFILE.
• Microsoft: access control lists — official Microsoft documentation relevant to CO_E_FAILEDTOCREATEFILE.
• Microsoft: canonical ACE order — official Microsoft documentation relevant to CO_E_FAILEDTOCREATEFILE.
• Microsoft: HRESULT values — official Microsoft documentation relevant to CO_E_FAILEDTOCREATEFILE.

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