Fix COMADMIN_E_REMOTEINTERFACE (0X80110419) in Windows

1. Corrupted COM+ Registration After a Windows Update

This is the most common trigger. I've seen it dozens of times — you install a Tuesday patch, reboot, and suddenly Component Services throws COMADMIN_E_REMOTEINTERFACE (0X80110419) when you try to expand COM+ Applications. The update might have overwritten essential DLLs or registry entries that COM+ relies on.

Here's what to do first. It's the quickest fix and works about 70% of the time.

1. Open an elevated Command Prompt. Press Windows Key + X, then click Command Prompt (Admin) or Windows PowerShell (Admin) — doesn't matter which.
2. Type this command and press Enter:

   regsvr32.exe comadmin.dll

   After you press Enter, you should see a popup that says "DllRegisterServer in comadmin.dll succeeded." If you get an error instead, note the error code.
3. Next, re-register the core COM+ runtime DLLs. Run each of these commands one at a time. Wait for the success message before moving to the next:

   regsvr32.exe comsvcs.dll
   regsvr32.exe colbact.dll
   regsvr32.exe oleaut32.dll
   regsvr32.exe ole32.dll

   Each one should confirm success.
4. Now restart the COM+ Event System and System Event Notification services. Press Windows Key + R, type services.msc, then press Enter.
5. In the Services window, find COM+ Event System. Right-click it and select Restart. Do the same for System Event Notification Service.
6. After both services have restarted, close the Services window. Open Component Services again by pressing Windows Key + R, typing dcomcnfg, and pressing Enter.
7. Expand Component Services > Computers > My Computer > COM+ Applications. The error should be gone now.

If that didn't fix it, don't worry — move to the next section. I've had cases where the update also changed security permissions on the COM+ catalog.

2. Security Permissions on the COM+ Catalog Got Reset

Windows updates can sometimes reset permissions on the %windir%\registration folder or the COM+ catalog registry keys. This is especially common on domain controllers or servers where you've customised COM+ access for a specific application.

Let me walk you through verifying and fixing those permissions. You'll need to be a local admin.

1. Press Windows Key + R, type regedit, then press Enter. Click Yes if UAC prompts.
2. Go to this key:

   HKEY_CLASSES_ROOT\CLSID\{00024500-0000-0000-C000-000000000046}

   That's the CLSID for the COM+ catalog object.
3. Right-click that key, choose Permissions. Make sure Administrators has Full Control and SYSTEM has Full Control. If they don't, click Add and add them.
4. Click Advanced. Check the box Replace all child object permission entries at the bottom. Click OK. Then click OK again.
5. Now check the second key:

   HKEY_CLASSES_ROOT\AppID\{00024500-0000-0000-C000-000000000046}

   Repeat the same steps — make sure Administrators and SYSTEM have Full Control.
6. Close Registry Editor.
7. Open an elevated Command Prompt and run:

   icacls "%windir%\registration" /grant "Administrators":(OI)(CI)F /T

   This gives Administrators full control over the COM+ registration folder. It's recursive, so it might take a minute. Wait until you see "Successfully processed 1 files" — it'll say 1 file but actually processes the folder and all subfolders.
8. Restart the COM+ Event System service again (as shown in step 1). Then open Component Services and check if the error is gone.

If you're still seeing the error, the problem is likely a mismatched or missing COM+ application registration. That's the third cause I'll cover.

3. Corrupted or Missing COM+ Application Registration

This happens when a specific COM+ application (like one from your ERP system or a line-of-business app) has its registration corrupted. The remote interface info gets lost because the app's catalog entry is broken. You'll know this is the case if the error only appears when you expand a particular application, not all of them.

Here's the fix that's worked for me every time on Server 2019.

1. Open Component Services (dcomcnfg).
2. Navigate to Component Services > Computers > My Computer > COM+ Applications.
3. Find the application that's throwing the error. It will likely have a yellow exclamation mark or won't expand at all.
4. Right-click that application and select Export. Choose Application proxy and save it to a folder like C:\temp\appproxy.msi. This creates a backup of the registration.
5. Now delete the problem application. Right-click it and choose Delete. Confirm the deletion.
6. Re-create the application from scratch. Right-click COM+ Applications, select New > Application. The COM+ Application Install Wizard starts.
7. Click Next. Choose Create an empty application. Give it the exact same name as the one you deleted. Select Server application and set the identity to Interactive user (or the specific account it needs — your app's documentation will specify).
8. After the wizard finishes, right-click the new application and select Properties. Go to the Activation tab and make sure it matches the original settings (if you remember them — if not, set it to Server application).
9. Now you need to add the original components. If you have the original DLLs, right-click Components under the application, choose New > Component, then Install new component. Browse to the DLL and add it.
10. If you don't have the DLLs, you might need to reinstall the application that registered with COM+ in the first place. Check the vendor's documentation — sometimes just running a repair install does the trick.
11. After re-creating the app, restart the COM+ Event System service one more time. Then refresh Component Services. The error should be gone.

I've seen this third fix save a lot of headache. If you're still stuck after all this, check the Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > COM+ for more specific error messages. Sometimes the event log gives you the exact component CLSID that's failing.

Quick-Reference Summary Table