Fix COMADMIN_E_OBJECT_DOES_NOT_EXIST 0X80110809

Quick answer

Open Command Prompt as admin, run regsvr32 %windir%\system32\clbcatq.dll then restart the COM+ service. This usually brings back the missing object.

What triggers this error

You're trying to open Component Services (dcomcnfg.exe) or run a script that accesses a COM+ application. Suddenly you get: One of the specified objects cannot be found. COMADMIN_E_OBJECT_DOES_NOT_EXIST (0X80110809). It often happens after a Windows update or when you uninstall a program that had COM+ components—like an old antivirus or a database client. The COM+ catalog loses track of the object. It's not gone, just unregistered.

I've seen this most on Windows 10 22H2 and Windows Server 2019 after patch Tuesday. The error is annoying because it blocks you from managing any COM+ app until you fix it.

Fix steps (main method)

Open Command Prompt as admin. Press Windows Key + X, choose "Command Prompt (Admin)" or "Terminal (Admin)". Click Yes on the UAC pop-up.
Re-register the core COM+ library. Type this and press Enter:
```
regsvr32 %windir%\system32\clbcatq.dll
```
You should see a pop-up saying "DllRegisterServer in clbcatq.dll succeeded".
Restart the COM+ System Application service. In the same command window, run:
```
net stop comsysapp && net start comsysapp
```
Wait 5 seconds after the "stopped" message. You'll see "The COM+ System Application service was started successfully".
Refresh Component Services. Open dcomcnfg again. Press Windows Key + R, type dcomcnfg, hit Enter. Expand "Component Services" > "Computers" > "My Computer" > "COM+ Applications". If the error is gone, you're set.

If the error still pops up after step 4, move to the alternative fixes below.

Alternative fixes (if main fix fails)

Re-register all COM+ related DLLs

Sometimes just clbcatq.dll isn't enough. In an admin Command Prompt, run each of these one by one:

regsvr32 %windir%\system32\comadmin.dll
regsvr32 %windir%\system32\catsrv.dll
regsvr32 %windir%\system32\comrepl.dll
regsvr32 %windir%\system32\mscoree.dll

After each one, wait for the success message. Then restart the COM+ service again (step 3 above).

Delete and re-create the COM+ application

If you know exactly which COM+ app is missing (the error usually shows a GUID), you can delete it and re-create it. Here's how:

Open Component Services as admin.
Right-click the COM+ Applications folder, choose "New" > "Application".
Click "Create an empty application". Give it the same name as the missing app. Click Next.
Select "Interactive user" or a specific account. Finish the wizard.

This creates a placeholder. Then you'll need to add the actual components back (right-click the app > "Components" > "New" > "Component" > "Install new component" and browse to the DLL).

Run System File Checker

If the COM+ DLLs are corrupted, run sfc /scannow in admin Command Prompt. It takes about 15 minutes. If it finds corrupt files but can't fix them, run dism /online /cleanup-image /restorehealth first, then re-run sfc.

Prevention tip

Before uninstalling any program, export the COM+ application. In Component Services, right-click the app, choose "Export", then select "Application Proxy" (not the full app). Save it as a .msi file. If the error comes back later, run that msi to restore the component registration.

I've had a user who kept hitting this error every time they rebooted. Turned out their backup software was deleting temporary COM+ objects at startup. We excluded the COM+ catalog folder from the backup scan and the error stopped.

One last thing: if you're on a domain, the error might be permission-related. Make sure your account is in the local Administrators group and has full control over the COM+ catalog. Check by running dcomcnfg, right-click "My Computer", choose "Properties", go to "COM Security" tab. Under "Access Permissions", click "Edit Default". Your account should have Allow for both Local Access and Remote Access.