| Previous | Next |
| CAT_E_NODESCRIPTION | CS_E_NOT_DELETABLE |
CS_E_PACKAGE_NOTFOUND
No package in the software installation data in the Active Directory meets this criteria.
CS_E_PACKAGE_NOTFOUND is the failure HRESULT 2147746148 (0x80040164, signed -2147221148) from winerror.h. The documented description is “No package in the software installation data in the Active Directory meets this criteria.” In practical terms, No directory-backed software package satisfies the class-installation criteria. Interpret it in the context of searching legacy Active Directory software-installation data for a COM class or ProgID.
Relevant contract
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 searching legacy Active Directory software-installation data for a COM class or ProgID, rather than from cleanup or a wrapper that ran afterward.
Likely cause branches
- It can result when no published package maps to the requested class.
- It can result when version, architecture, language, or policy filters exclude every candidate.
- It can result when directory replication has not delivered the package metadata to the contacted domain controller.
Evidence to preserve
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.
- Record the search criteria and domain controller rather than only the HRESULT.
- Verify package publication and class mappings in the same directory context.
- Compare results across replicated controllers before changing client registration.
Diagnostic sequence
- Identify the exact object, method, and lifecycle phase involved in searching legacy Active Directory software-installation data for a COM class or ProgID.
Recovery and retry
Correction. publish or select a matching package, relax only an incorrect criterion, or install the component through a supported modern deployment path. Retry condition. Retry after directory replication or package publication; immediate retries against unchanged criteria add load without new evidence. 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 client requests an x64 class but only an x86 package is published; adding the correct architecture package resolves lookup without copying registration entries.
Difference from related HRESULTs
REGDB_E_CLASSNOTREG concerns local usable registration; it concerns the legacy directory search for something that could be installed.
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.