What does HRESULT 0x80110404 (COMADMIN_E_ALREADYINSTALLED) mean?

 
Previous Next
COMADMIN_E_KEYMISSING COMADMIN_E_APP_FILE_WRITEFAIL

COMADMIN_E_ALREADYINSTALLED

COMADMIN_E_ALREADYINSTALLED is the failure HRESULT 0x80110404 (signed decimal -2146368508, unsigned decimal 2148598788). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0404.

COM+ installation identity and duplicate state: exact meaning of COMADMIN_E_ALREADYINSTALLED

The COM object being registered is already present in the target catalog context. An installation or registration path attempts to add an object that COM+ already recognizes.

AllStat records this condition as “The object is already registered”.

Where COMADMIN_E_ALREADYINSTALLED occurs

COM+ installation updates the catalog, class registration, type-library metadata, and files as one supported deployment workflow; a duplicate result must be resolved at that workflow boundary. In the specific case of COMADMIN_E_ALREADYINSTALLED, resolve the existing CLSID, application, and component file before deciding whether the operation is an idempotent deployment or a version conflict.

Evidence to collect before repair

  • Evidence for COMADMIN_E_ALREADYINSTALLED should include application ID, CLSID, component DLL path, version, and hash, captured before a repair changes state.
  • Collect existing Components and Applications collection entries when diagnosing COMADMIN_E_ALREADYINSTALLED; without it the symbolic HRESULT is underdetermined.
  • The COMADMIN_E_ALREADYINSTALLED investigation needs installer/package identity and previous deployment result so the exact failing boundary remains reconstructable.
  • For COMADMIN_E_ALREADYINSTALLED, preserve registry and catalog ownership for the conflicting identifier; it anchors the failure to the real administration object.

Diagnostic sequence for COMADMIN_E_ALREADYINSTALLED

  • At the COMADMIN_E_ALREADYINSTALLED boundary, enumerate the existing application and component before changing anything.
  • The next COMADMIN_E_ALREADYINSTALLED diagnostic action is to decide whether the operation is install, update, repair, or migration.
  • To isolate COMADMIN_E_ALREADYINSTALLED, use the owning installer or COMAdmin method for the chosen path.
  • For COMADMIN_E_ALREADYINSTALLED, avoid manual deletion of only catalog or registry fragments.
  • At the COMADMIN_E_ALREADYINSTALLED boundary, repopulate and compare the resulting identities and file versions.

Difference from nearby COMADMIN results

COMADMIN_E_APPLICATIONEXISTS is specific to an application, and COMADMIN_E_COMPONENTEXISTS is specific to a component in the application.

Retry and recovery

Use an update/reinstall procedure or remove the verified stale registration; blind retries reproduce the duplicate.

Practical administration scenario

A deployment reruns component installation without uninstalling the prior package and receives this duplicate-registration result.

Official Microsoft references for COMADMIN_E_ALREADYINSTALLED

Looking for a different code? Search another status or error code.