| Previous | Next |
| REGDB_E_PACKAGEPOLICYVIOLATION | CAT_E_NODESCRIPTION |
CAT_E_CATIDNOEXIST
CATID does not exist
CAT_E_CATIDNOEXIST has hexadecimal value 0x80040160 (unsigned 2147746144, signed -2147221152). Windows reports “CATID does not exist”. The narrow interpretation is that the requested component category identifier is not registered. The failing stage is querying or updating category information through the Component Categories Manager.
API stage
Component categories are semantic identifiers, not merely friendly strings. Category definition, localized description, and class membership are separate records and should be diagnosed independently.
- Associate this result with one exact operation in the Component Categories Manager, ICatRegister, ICatInformation, CATID registration, and localized CATEGORYINFO descriptions.
- Confirm that this result came from querying or updating category information through the Component Categories Manager, rather than from cleanup or a wrapper that ran afterward.
Verification steps
- Identify the exact object, method, and lifecycle phase involved in querying or updating category information through the Component Categories Manager.
- Log the exact CATID and operation, not only its friendly name.
- Enumerate registered categories through ICatInformation.
- Distinguish category definition from a class claiming membership in that category.
Interpretation limits
- It can result when the CATID is mistyped, version-specific, or generated but never registered.
- It can result when component membership keys remain after the category definition was removed.
- It can result when the query runs in a registry scope or machine image where the category installer did not execute.
Incident record
A useful incident records the CATID, locale identifier, operation, registry scope, category description, enumerator result, class membership keys, and installation or uninstallation transaction.
- enumerate registered categories through ICatInformation.
Recovery conditions
Correction. register the published category definition through ICatRegister or use a CATID present on the target system. Retry condition. Retry after category installation or identifier correction; do not invent a description for an unknown CATID. Before repeating the operation, separate category definition changes from class-membership changes and roll back only the registration operation that failed.
Practical scenario
A plugin registers itself under a vendor CATID but the base product that defines the category is absent; installing the base category registration restores discovery.
Difference from related HRESULTs
CAT_E_NODESCRIPTION means the CATID exists but lacks the requested localized description; it means the category itself is absent.
Developer and administrator guidance
Store CATIDs as stable identifiers, keep localized descriptions independent from membership, and enumerate current records before updating them. Regression coverage should include unknown CATIDs, missing localized descriptions, repeated registration, class membership without a definition, different locales, and uninstall ordering.
Repair category metadata through the owning component’s installer and verify both category definitions and class membership instead of editing only the friendly description.
References
Looking for a different code? Search another status or error code.