| Previous | Next |
| CS_E_INVALID_VERSION | CS_E_OBJECT_NOTFOUND |
CS_E_NO_CLASSSTORE
There is no software installation data in the Active Directory.
When Windows returns CS_E_NO_CLASSSTORE—HRESULT 2147746152, 0x80040168, signed -2147221144—The documented description is “There is no software installation data in the Active Directory.” The actionable meaning is the directory context contains no usable COM Class Store data. The surrounding operation is attempting legacy automatic class installation in a domain or policy context without Class Store infrastructure.
Precise failure point
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 attempting legacy automatic class installation in a domain or policy context without Class Store infrastructure, rather than from cleanup or a wrapper that ran afterward.
Diagnostic evidence
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 domain membership, policy result, directory bind target, and discovery path.
- distinguish absent infrastructure from a network failure reaching existing infrastructure.
- Confirm whether the application should rely on local or packaged deployment instead.
Resolution path
- Identify the exact object, method, and lifecycle phase involved in attempting legacy automatic class installation in a domain or policy context without Class Store infrastructure.
Distinct causes
- It can result when the feature was never configured in the domain.
- It can result when the client is outside the expected domain or cannot discover the directory partition.
- It can result when policy disables automatic class installation or points to a context with no data.
Retry policy
Correction. install the component explicitly or configure the legacy infrastructure only when it is still an intentional enterprise dependency. Retry condition. Retry after joining the correct context or policy refresh; otherwise suppress repeated automatic-install attempts. 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 standalone workstation calls CLSIDFromProgIDEx expecting domain installation, but no Class Store exists; the product installer provides the required local COM registration.
Difference from related HRESULTs
CS_E_NETWORK_ERROR means an existing directory operation was interrupted; it means the expected data set is absent.
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.