| Previous | Next |
| CO_E_OBJNOTCONNECTED | CO_E_RELEASED |
CO_E_APPDIDNTREG
Meaning and numerical form
CO_E_APPDIDNTREG is HRESULT 2147746302 (0x800401FE; signed -2147220994). AllStat records its meaning as “Application was launched but it didn't register a class factory”. In practical terms, it is returned when COM launches a local server executable but the process does not register the requested class factory within the activation window.
The severity bit in 0x800401FE is set, so this result is a failure result rather than a success or informational status. Its facility is 4 (FACILITY_ITF) and its low 16-bit code is 510 (0x01FE). Those fields classify the value but do not identify the component instance, call, object or input that produced it.
Likely causes
- Possible cause 1 for it: the server fails before calling CoRegisterClassObject.
- Possible cause 2 for it: startup blocks on UI, configuration, networking or a deadlock.
- Possible cause 3 for it: the process registers a different CLSID or uses registration flags inconsistent with activation.
Where the failure belongs
This result belongs to COM activation and object lifetime. COM activation is a sequence rather than one registry lookup: identifier resolution, class registration, module or process start, class-factory publication, marshaling, and object lifetime can fail independently. The decisive condition is this: COM launches a local server executable but the process does not register the requested class factory within the activation window. Record the first native producer instead of relying only on a framework exception translated several layers later.
Do not infer from this result alone that reinstalling, rebooting or repeating the whole workflow is appropriate. Because it can cross process and language boundaries, its correction depends on the object identity, lifecycle generation, input and state at the first failing call.
Diagnostic sequence
- Capture this result at the first native return and identify the exact object and method.
- Confirm that the observed path matches this the condition: COM launches a local server executable but the process does not register the requested class factory within the activation window.
- compare the live state with the method contract before changing configuration.
- collect the code-specific evidence listed above and preserve any more specific preceding error.
- change one evidence-backed cause at a time, then repeat the smallest operation that can prove the correction.
- Add a regression check that distinguishes it from the related outcomes described below.
Evidence to collect
A useful it record includes the native API or interface method, component or CLSID, process and thread IDs, architecture, apartment where relevant, operation correlation ID, elapsed time, input identity, and the first state-changing event before failure. When diagnosing it, preserve IErrorInfo, an inner HRESULT, Win32 status, device event or provider message when available.
- Capture 1 for it: process creation result, PID, command line and startup timestamps.
- Capture 2 for it: the requested CLSID and every CoRegisterClassObject call made by the server.
- Capture 3 for it: early server logs, crash reports and wait chains before registration.
Telemetry for it should retain types, lengths, hashes, stable opaque identifiers and lifecycle generations while redacting content and credentials. This makes repeated incidents comparable without exposing paths, object identities, user data or credentials.
Correction and retry boundary
- Corrective action 1 for it: call CoRegisterClassObject promptly after minimal initialization.
- Corrective action 2 for it: move slow optional work after class-factory registration or report a specific startup failure.
- Corrective action 3 for it: correct CLSID and REGCLS usage and verify registration is revoked on shutdown.
Retry guidance for it. Retry after the server startup cause is fixed or after a transient dependency becomes available; use bounded backoff because repeated launches can create orphaned processes. A it retry must avoid this hazard: launch duplicate servers, reuse stale proxies or repeat an activation whose side effects are unknown. It must also preserve the evidence needed to locate the original producer of it.
Difference from nearby HRESULTs
CO_E_APPNOTFOUND means the executable could not be located; it means it launched but failed to publish the requested class factory. Keep these outcomes separate in logs, exception mappings, user messages, dashboards and automated retry policy.
Practical scenario
A local server waits indefinitely for a remote configuration endpoint before registering its class factory; registering first and completing deferred initialization removes it. The result scenario narrows the result to a reproducible contract boundary and supplies a concrete before-and-after test.
Developer and operational guidance
Code handling it should log the failed stage before cleanup, keep ownership and lifecycle transitions explicit, and avoid converting every failure into a generic message. Tests for it should cover the primary cause, one adjacent HRESULT and the retry boundary so a future change cannot turn a deterministic contract failure into an uncontrolled loop.
Operational repair for it should use supported product installation, COM registration, activation and class-factory lifetime paths. Avoid unsupported configuration edits or component replacement unless evidence identifies that layer. Retain the original trace and a post-fix trace so the result can be attributed and the change reversed.
Official Microsoft references
Looking for a different code? Search another status or error code.