| Previous | Next |
| CS_E_CLASS_NOTFOUND | CS_E_NO_CLASSSTORE |
CS_E_INVALID_VERSION
The software installation data in the Active Directory is corrupt.
CS_E_INVALID_VERSION has hexadecimal value 0x80040167 (unsigned 2147746151, signed -2147221145). Windows reports “The software installation data in the Active Directory is corrupt.” The narrow interpretation is that the directory software-installation metadata contains an invalid or corrupt version. The failing stage is reading or comparing package version data during Class Store lookup.
API stage
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 reading or comparing package version data during Class Store lookup, rather than from cleanup or a wrapper that ran afterward.
Verification steps
- Identify the exact object, method, and lifecycle phase involved in reading or comparing package version data during Class Store lookup.
- Capture all raw version attributes and object revision metadata.
- Compare the object with a known-good export or package publication record.
- Inspect replication conflict objects before editing production data.
Interpretation limits
- It can result when the version attribute has malformed syntax or an unsupported range.
- It can result when a partial administrative update leaves related version fields inconsistent.
- It can result when replication conflict combines metadata from incompatible package revisions.
Incident record
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.
Recovery conditions
Correction. republish or repair the package metadata from an authoritative source and let replication converge. Retry condition. Do not coerce the invalid text into a version; retry only after the object is repaired. 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 package revision is entered as free-form text where the Class Store expects structured version data; republishing through the administration tool restores consistency.
Difference from related HRESULTs
CS_E_SCHEMA_MISMATCH concerns the shape of directory data; it concerns version content inside that data.
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.