| Previous | Next |
| CO_E_SETSERLHNDLFAILED | CO_E_PATHTOOLONG |
CO_E_FAILEDTOGETWINDIR
COM access-control code could not obtain the Windows directory
CO_E_FAILEDTOGETWINDIR is HRESULT 2147549492 (0x80010134) from winerror.h. The documented description is “Unable to obtain the Windows directory.” The relevant context is the COM IAccessControl, DCOM client identity, trustee translation, token inspection, security descriptor, ACL, or serialization workflow.
Where it is encountered
- IAccessControl initialization, access checks, owner/trustee processing, and serialized ACL persistence.
- Server-side DCOM impersonation, client blanket inspection, token and SID lookup.
- Security descriptor construction, DACL canonicalization, file-backed policy storage, or legacy NetAccess migration.
The immediate focus is legacy serialization or support code that requires the Windows directory for temporary or persistent access-control data.
What to verify
Verify that environment, API buffer size, path redirection, service account, and native error are recorded. This distinction prevents it from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.
Correct handling and recovery
Use the documented Windows-directory API with dynamic sizing, avoid hard-coded paths, and verify filesystem access under the service identity.
Reconcile partial output and server-side effects before attempting the operation again.
Practical scenario
A constrained service environment returns an unexpected directory length. The component adopts dynamic path sizing and a product-owned data directory.
Difference from nearby HRESULTs
It is path discovery failure; CO_E_PATHTOOLONG occurs after a path is built beyond supported limits.
Developer and administrator guidance
Document the component that returned the result so future occurrences can be correlated across client, proxy, server, package, and security logs.
References
Looking for a different code? Search another status or error code.