| Previous | Next |
| WININET_E_DECODING_FAILED | CO_E_SCM_ERROR |
CO_E_CLASS_CREATE_FAILED
CO_E_CLASS_CREATE_FAILED means that COM located an activation route but failed while obtaining or invoking the class factory that creates the requested object.
The contract behind the HRESULT
REGDB_E_CLASSNOTREG means no usable registration; CO_E_CLASS_CREATE_FAILED means activation progressed far enough to attempt class-object creation.
Diagnostic worksheet
- CLSID, requested IID, CLSCTX flags, bitness, and activation machine
- InprocServer32 or LocalServer32 registration resolved for that caller
- Module load/entry-point result or server-side class-factory registration event
- Server crash, loader error, dependency failure, and the original activation HRESULT
Reproduce the condition safely
- Activate the same CLSID with a minimal CoCreateInstance client of matching bitness.
- Call CoGetClassObject separately to isolate class-factory acquisition from instance creation.
- Load the registered module with dependency diagnostics in a clean process.
Nearby states and false leads
Use the outcomes to narrow the layer rather than to accumulate unrelated fixes for COM class-factory creation:
Closing the incident
The corrective action should be narrow: Repair the class factory, module dependencies, registration view, or server initialization that fails before object construction.
Close the incident only when CoGetClassObject and instance creation succeed from the intended client architecture, and a missing dependency control reproduces the earlier boundary.
Technical references
Looking for a different code? Search another status or error code.