| 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. The documented description is “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.
Operational meaning
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.
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
- Identify the exact object, method, and lifecycle phase involved in resolving a COM class through legacy Class Store metadata.
- Log CLSID, package candidates, versions, and domain controller.
- Inspect class-to-package mappings separately from package existence.
- Verify whether local registration or a modern package is the intended deployment route.
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.
Correction strategy
Correction. publish the correct class mapping or install the component using its supported deployment mechanism. Retry condition. 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.
Difference from related HRESULTs
CS_E_PACKAGE_NOTFOUND finds no qualifying package; it finds no directory record for the specific CLSID.
Developer and administrator guidance
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.
References
Looking for a different code? Search another status or error code.