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 is that the Common Language Runtime required by the component is missing, disabled, incompatible, or failed to initialize. When this result crosses a language or process boundary, preserve its original numeric form before projections replace it with a broad exception class.

Where the result appears

  • This result may surface in managed COM components or mixed native/managed activation.
  • The first boundary to preserve for it is the exact activation, initialization, call-control, or lifetime step that returned it.
  • 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 this result 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 it are: the required runtime is not installed; architecture mismatches; hosting policy forbids loading; runtime initialization failed earlier. Do not treat the cause list for it as a checklist of simultaneous failures; use traces and postconditions to select the matching branch.

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

Correct handling and recovery

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 it needs a bounded attempt count, a state refresh step, and a rule for reconciling work that may already have completed.

Cleanup following it 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 it 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; it means COM cannot obtain a usable CLR for activation.

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

Developer and administrator guidance

Code handling it should classify it by lifecycle and ownership rather than by the high bit alone. For <code>it</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 it 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 it identifies that subsystem.

References

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