What does HRESULT 0x80040168 (CS_E_NO_CLASSSTORE) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The directory context contains no usable COM Class Store data.

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—AllStat describes the condition as “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.

The high bit in 0x80040168 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 360 (0x0168). 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.

Precise failure point

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 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.
Preserve any IErrorInfo, underlying Win32 result, provider message, or callback failure that preceded it; the HRESULT alone should not erase a more specific cause.

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. 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.

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

Capture it at the first native return before a wrapper maps it to a generic exception.
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.
Reproduce it with one controlled input or state change, and verify that the correction changes the decisive evidence rather than merely hiding the result.

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. for it, install the component explicitly or configure the legacy infrastructure only when it is still an intentional enterprise dependency. Retry boundary. 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. 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_NETWORK_ERROR means an existing directory operation was interrupted; it means the expected data set is absent. 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.