What does HRESULT 0x80040166 (CS_E_CLASS_NOTFOUND) mean?

 
Previous Next
CS_E_NOT_DELETABLE CS_E_INVALID_VERSION

CS_E_CLASS_NOTFOUND

The CLSID was not found in the software installation data in the Active Directory.

The native value 0x80040166 is CS_E_CLASS_NOTFOUND, unsigned 2147746150 and signed -2147221146. According to AllStat, it means “The CLSID was not found in the software installation data in the Active Directory.” Treat it as evidence that the requested CLSID is absent from the directory software-installation data; the operation in progress is resolving a COM class through legacy Class Store metadata.

The high bit in 0x80040166 is set, so this is a failure rather than a success or informational result. Its facility field is 4 (FACILITY_ITF) and its low 16-bit code is 358 (0x0166). Those bit fields classify the value, but they do not identify the failing object by themselves; the native method, object identity, and first producer of this result remain essential.

Operational meaning

Understanding this result requires this subsystem context: These CS_E values describe the legacy directory-backed COM Class Store. Public documentation is limited; the exact owner is the component performing automatic installation or directory lookup, so traces must identify that component rather than assigning the HRESULT to every modern COM activation path.

  • Associate this result with one exact operation in automatic class installation or lookup through COM Class Store policy and directory-backed software-installation objects.
  • Confirm that this result came from resolving a COM class through legacy Class Store metadata, rather than from cleanup or a wrapper that ran afterward.
  • Preserve any IErrorInfo, underlying Win32 result, provider message, or callback failure that preceded it; the HRESULT alone should not erase a more specific cause.

Cause model

  • It can result when the package exists but does not advertise this CLSID.
  • It can result when the application requests a class introduced by another version or edition.
  • It can result when class mapping was removed or not replicated even though package metadata remains.

Troubleshooting workflow

  1. Capture it at the first native return before a wrapper maps it to a generic exception.
  2. Identify the exact object, method, and lifecycle phase involved in resolving a COM class through legacy Class Store metadata.
  3. Log CLSID, package candidates, versions, and domain controller.
  4. Inspect class-to-package mappings separately from package existence.
  5. Verify whether local registration or a modern package is the intended deployment route.
  6. Reproduce it with one controlled input or state change, and verify that the correction changes the decisive evidence rather than merely hiding the result.

What to log

A useful incident records the requested CLSID or ProgID, directory object DN, package identifier, version, deployment path, domain controller, schema version, policy state, bind result, and object size. Also retain the application and component build, architecture, process and thread IDs, COM apartment, operation correlation ID, elapsed time, and the first state-changing event before the failure. When logging it, redact content and credentials while preserving types, lengths, hashes, opaque identities, and lifecycle generations needed to reproduce its contract.

Correction strategy

Correction. for it, publish the correct class mapping or install the component using its supported deployment mechanism. Retry boundary. Retry after metadata or replication changes; selecting an unrelated package by product name is not a safe substitute. Before repeating the operation, determine whether directory metadata, package staging, or a local installation changed before failure and avoid deleting a directory object whose ownership is not established.

Practical scenario

A suite package is published, but its optional imaging component CLSID was omitted from class mappings; updating the package metadata enables targeted installation. This isolates it within legacy COM Class Store and Active Directory software-installation metadata and provides a regression test for the stated correction.

Difference from related HRESULTs

CS_E_PACKAGE_NOTFOUND finds no qualifying package; it finds no directory record for the specific CLSID. Keep those outcomes separate in exception mappings, telemetry dimensions, user messages, and automated retry policy.

Developer and administrator guidance

Treat CS_E results as a legacy automatic-installation contract, preserve directory and policy diagnostics, and fall back to ordinary COM registration only when the product explicitly supports it. Regression coverage for it should include missing packages and classes, duplicate objects, malformed paths, version and schema mismatch, directory outages, administrative limits, and partial publication of metadata.

Operational repair for it must target the evidence-backed owner: involve the Active Directory or software-deployment owner, verify policy and domain-controller evidence, and use the management system that created the package or class-store object. Retain before-and-after traces for it so the change can be attributed and reversed.

References

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