COM+ app pause/resume error 0X80110485 fix

You're in Component Services, right-click a COM+ application, try to Pause or Resume, and get this error. You're running a 64-bit Windows Server — 2012 R2, 2016, 2019, or 2022. The application is probably one you imported or created yourself, not one of the built-in system apps. The culprit here is almost always the application's activation type or identity settings.

What causes it

COM+ applications have a little-known restriction: only those configured as server applications (running in their own dllhost.exe process) support pause/resume. If your app is set to run as a library application (in-process with the caller), the COM+ catalog blocks the pause/resume operation. That's what error 0x80110485 means — the COM+ subsystem is saying "I can't pause this, it's not designed for it."

Another less common cause: the application is configured to run under a specific user account that's missing the Impersonate privilege or the COM+ application identity account has been deleted or disabled. But I'd bet 90% of the time it's the library application setting.

The fix

1. Open Component Services — run dcomcnfg from an admin command prompt or Start menu.
2. Navigate to Component Services > Computers > My Computer > COM+ Applications.
3. Right-click the problem application and choose Properties.
4. Go to the Activation tab.
5. Change the activation type from Library application to Server application.
6. Click Apply — you'll get a warning that other apps referencing this COM+ may need updates. That's fine for most cases; click OK.
7. Now go to the Identity tab. Set it to Interactive user (the logged-in user) unless you specifically need it to run as a service account.
8. Click OK to close. The COM+ app will be shut down and restarted automatically.
9. Right-click the application again and try Pause or Resume. It should work now.

What if it still doesn't work

If the fix above didn't help, check these three things:

• COM+ application identity account — go to the Identity tab, pick a specific user (like NT AUTHORITY\NETWORK SERVICE). Make sure that account exists and has Log on as a batch job right. If you're using a domain account, verify it's not locked or expired.
• Corrupted catalog — sometimes the COM+ catalog gets borked. Run this from an admin command prompt:
  

  regsvr32 /s comsvcs.dll
  regsvr32 /s coloader.dll
  regsvr32 /s comadmin.dll

  
  Then restart the COM+ System Application service from services.msc.
• Antivirus or security software — I've seen Cylance and CrowdStrike block COM+ methods related to process management. Temporarily disable the security agent to test. If that fixes it, add an exception for dllhost.exe and comsvcs.dll.

One last thing — if you still get the error after all that, check the event logs. Open Event Viewer, go to Applications and Services Logs > Microsoft > Windows > COM+. Look for any catalog errors or warnings with event ID 4689 or 7031. Those will point you straight to the problem.

Pro tip: Don't bother reinstalling COM+ or the Windows feature — that rarely helps. The fix is almost always in the activation type or identity. Save yourself the reboot.