| Previous | Next |
| E_ADS_INVALID_FILTER | RPC_E_CALL_REJECTED |
E_UNEXPECTED
Unexpected catastrophic HRESULT escaped the component
E_UNEXPECTED is HRESULT 2147549183 (0x8000FFFF) from winerror.h. The documented description is “Catastrophic failure.” The value must be interpreted at a COM method or runtime path that encountered an invariant violation not represented by a more specific contract result.
The component reached an internal state it considered impossible or unrecoverable for the current operation. Keep the symbolic name beside the raw hexadecimal value so later analysis does not collapse the result into an unrelated COM family.
Where the result appears
- This result may surface in a COM method or runtime path that encountered an invariant violation not represented by a more specific contract result.
Determine the object and lifecycle phase that owned this result; a UI symptom cannot establish whether the origin was the caller, proxy, runtime, server, or metadata producer.
Typical causes and interpretation
Common cause categories are: memory corruption; violated internal invariant; swallowed earlier error; incompatible binary; race or teardown bug. Evaluate these branches independently and require evidence from the owning API before promoting one branch to the root cause.
Key distinction: the component reached an internal state it considered impossible or unrecoverable for the current operation.
Correct handling and recovery
The appropriate recovery is to stop broad retries, preserve a dump and timeline, isolate the component, and fix the earliest invariant violation rather than handling this as a normal input error. The owner of retry must define idempotency, refreshed state, maximum attempts, backoff, and cancellation responsibility.
After this result, apply the API-specific validity rules to outputs and release only resources whose ownership transferred during this attempt.
Practical scenario
A server returns the code after an earlier failed initialization was ignored; preserving the first failure reveals the missing state transition.
A regression test should force the relevant precondition, assert native outputs, fix only that condition, and confirm the expected neighboring result.
Difference from related HRESULTs
E_FAIL is a generic operation failure; it signals a stronger internal invariant or catastrophic condition.
References
Looking for a different code? Search another status or error code.