What does HRESULT 0x80004028 (CO_E_CLRNOTAVAILABLE) mean?

 
Previous Next
CO_E_CLASS_DISABLED CO_E_ASYNC_WORK_REJECTED

CO_E_CLRNOTAVAILABLE

COM activation requires an unavailable CLR

CO_E_CLRNOTAVAILABLE is HRESULT 2147500072 (0x80004028) from winerror.h. AllStat describes it as “The common language runtime is not available.” The value must be interpreted at managed COM components or mixed native/managed activation, because the same high-level symptom can come from a different contract boundary and require different cleanup.

The decisive interpretation for CO_E_CLRNOTAVAILABLE is that the Common Language Runtime required by the component is missing, disabled, incompatible, or failed to initialize. When CO_E_CLRNOTAVAILABLE crosses a language or process boundary, preserve its original numeric form before projections replace it with a broad exception class.

Where the result appears

  • CO_E_CLRNOTAVAILABLE may surface in managed COM components or mixed native/managed activation.
  • The first boundary to preserve for CO_E_CLRNOTAVAILABLE is the exact activation, initialization, call-control, or lifetime step that returned it.
  • For CO_E_CLRNOTAVAILABLE, record whether the failure occurred before an object identity existed, while a method was running, or during shutdown; those phases imply different ownership and retry rules.

Triage of CO_E_CLRNOTAVAILABLE starts by locating the exact owner of the failing state, including object identity, apartment, package, and deployment generation.

Typical causes and interpretation boundary

Common cause categories for CO_E_CLRNOTAVAILABLE are: the required runtime is not installed; architecture mismatches; hosting policy forbids loading; runtime initialization failed earlier. Do not treat the cause list for CO_E_CLRNOTAVAILABLE as a checklist of simultaneous failures; use traces and postconditions to select the matching branch.

The check that separates CO_E_CLRNOTAVAILABLE from nearby HRESULTs is: the Common Language Runtime required by the component is missing, disabled, incompatible, or failed to initialize. A recovery decision for CO_E_CLRNOTAVAILABLE should wait until the decisive condition is observed in call data, component state, or metadata.

Evidence and telemetry

  • Record CO_E_CLRNOTAVAILABLE together with the CLSID, IID, method or control operation, server type, process architecture, and component build.
  • Capture CO_E_CLRNOTAVAILABLE evidence: managed server identity; requested CLR version; runtime installation; bitness; activation configuration; CLR load events.
  • Preserve the apartment model, thread ID, package or service identity, activation flags, UTC time, and correlation ID associated with CO_E_CLRNOTAVAILABLE.
  • For CO_E_CLRNOTAVAILABLE, retain the earliest lower-level Win32, RPC, MSI, SxS, CLR, loader, or security event instead of logging only the final HRESULT.
  • After CO_E_CLRNOTAVAILABLE, mark every returned interface pointer, handle, cookie, or output parameter as valid only when the owning API explicitly says so.

When recording CO_E_CLRNOTAVAILABLE, retain structural metadata and redact content-bearing arguments, authentication material, and personal data.

Diagnostic sequence

  • Capture the raw value 0x80004028 and symbolic name CO_E_CLRNOTAVAILABLE before a wrapper translates it to a generic exception.
  • Identify the exact COM entry point and lifecycle phase for CO_E_CLRNOTAVAILABLE: initialization, activation, QueryInterface, method execution, cancellation, registration, or teardown.
  • Validate the decisive condition for CO_E_CLRNOTAVAILABLE: the Common Language Runtime required by the component is missing, disabled, incompatible, or failed to initialize.
  • Test the principal causes separately for CO_E_CLRNOTAVAILABLE: the required runtime is not installed; architecture mismatches; hosting policy forbids loading; runtime initialization failed earlier.
  • Correlate client and server timelines, including process launch, class registration, RPC activity, security negotiation, and cleanup around CO_E_CLRNOTAVAILABLE.
  • Change one precondition at a time, reproduce CO_E_CLRNOTAVAILABLE, and verify both the HRESULT and the object or server state after the call.

Correct handling and recovery

For CO_E_CLRNOTAVAILABLE, the appropriate recovery is to install or repair the supported runtime, align component architecture and activation configuration, and avoid loading an arbitrary CLR version. A retry policy for CO_E_CLRNOTAVAILABLE needs a bounded attempt count, a state refresh step, and a rule for reconciling work that may already have completed.

Cleanup following CO_E_CLRNOTAVAILABLE must be generation-aware: do not destroy shared state or outputs owned by an earlier successful operation.

Practical scenario

A legacy managed COM server requires .NET Framework in a minimal image; deployment installs the supported feature and reruns registration.

Coverage for CO_E_CLRNOTAVAILABLE should include the exact failure, a corrected success case, and the closest related HRESULT so classification remains stable.

Difference from related HRESULTs

COR_E_* values may describe failures after the CLR loads; CO_E_CLRNOTAVAILABLE means COM cannot obtain a usable CLR for activation.

Tests and telemetry should encode the boundary around CO_E_CLRNOTAVAILABLE so future wrappers do not flatten it into an ambiguous generic exception.

Developer and administrator guidance

Code handling CO_E_CLRNOTAVAILABLE should classify it by lifecycle and ownership rather than by the high bit alone. For <code>CO_E_CLRNOTAVAILABLE</code>, initialization failures normally require rebuilding the process or thread environment, capability results require a fallback, and uncertain remote outcomes require reconciliation before retry.

Operational dashboards should keep CO_E_CLRNOTAVAILABLE distinct from generic COM failures and attach deployment, service, package, runtime, policy, and architecture dimensions. Administrators should avoid broad registry edits, blanket firewall changes, or permission expansion unless the captured evidence for CO_E_CLRNOTAVAILABLE identifies that subsystem.

References

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