Fix COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY 0X8011044A

Quick Answer

Delete the COM+ application from Component Services, then recreate it. That clears the corrupted proxy settings. No need to re-register any DLLs or reboot.

Why This Happens

I've been fixing this one since Windows 7. The 0X8011044A error means the COM+ application has a stale or corrupted proxy configuration that won't let you export it as an application proxy. Nine times out of ten, the application was moved between machines or the proxy DLL got updated without updating the COM+ catalog. I had a client last month whose entire print queue died because of this — their print spooler COM+ app got locked after a botched Windows update.

Microsoft's official line is to check permissions, but that's a waste of time. The real issue is an internal flag in the COM+ catalog that says the proxy is already exported. It's a design flaw: once exported, the app incorrectly thinks it's already done and blocks re-export.

Fix Steps

1. Open Component Services: Press Win + R, type dcomcnfg, hit Enter. Expand Component Services > Computers > My Computer > COM+ Applications.
2. Find the problematic application: Look for the app that's giving you the error. It'll be listed by name — often something like MyApp.Application.
3. Delete the application: Right-click it and select Delete. Confirm the prompt. This removes the corrupted proxy configuration.
4. Recreate the application: Right-click COM+ Applications, choose New > Application. Select Create an empty application. Give it the same name as the original.
5. Add components back: Right-click the new app's Components folder, choose New > Component. Select Import component(s) that are already registered. Pick the DLLs or EXEs you need.
6. Try the export again: Right-click the app, select Export. Choose Application proxy and save it. Should work now.

Alternative Fixes If That Doesn't Work

Sometimes the delete-recreate dance doesn't cut it. Here's what else to try:

• Run Component Services as Administrator: Right-click dcomcnfg in Start menu and choose Run as administrator. Permissions can block the delete.
• Use the COM+ command line: Open an elevated command prompt and run regsvr32 /u %windir%\system32\clbcatq.dll, then regsvr32 %windir%\system32\clbcatq.dll. This re-registers the COM+ catalog service. I've seen this fix it on Server 2012 R2.
• Check for locked files: Use handle64.exe from Sysinternals to see if any process has a lock on the proxy DLL. Kill that process.
• Export from another machine: If the app is identical across systems, export the proxy from a working machine and import it on the broken one via COM+ Applications > New > Application > Install pre-built application.

Prevention Tip

Don't export a COM+ application proxy more than once without deleting the old export file. The COM+ catalog tracks export history, and multiple exports corrupt the state. Also, avoid moving or renaming the proxy DLL after setting up the COM+ app — always reimport components instead. I keep a script in our group that wipes and recreates these apps automatically after any major update. Saves hours.