Fix COMADMIN_E_APP_FILE_VERSION 0x80110409 Error

What's Happening?

You're trying to install or register a COM+ application and get hit with COMADMIN_E_APP_FILE_VERSION (0x80110409). The system is saying, "This app file has a version number that doesn't match what we're expecting." And it just stops dead.

The Real Fix

Skip rebuilding your whole COM+ catalog—that's overkill. 99% of the time, this error means your application file (.msi or exported .COM file) was created from a different COM+ application version than the one you're trying to install it into.

Step 1: Check the Source Version

Open Component Services (run dcomcnfg). Go to Component Services > Computers > My Computer > COM+ Applications. Find the application you're trying to update. Right-click it, choose Properties, and look at the General tab. Note the Application ID and the application name.

Now, compare that to the application file you're trying to install. If you exported the app from one server and are trying to import it into another server that already has a different version (like a newer build or an older one), you'll get this error.

Step 2: Delete the Existing App (If Safe)

If the current application on the target machine is a dead install or an outdated test version, just delete it: right-click the app in Component Services and select Delete. Then try importing your .COM file again. This worked for a client last month whose print queue COM+ app was from a completely different Windows build.

Step 3: If You Need Both Versions

You can't have two COM+ applications with the same Application ID but different versions in the same partition. So, rename the existing application or export it elsewhere, then import yours. Or, re-export the app from the original server with a matching version.

Here's how to force it if the above doesn't work: open a command prompt as administrator and run:

cd /d %windir%\system32\Com
regsvr32 comadmin.dll
regsvr32 clbcatq.dll
net stop comsysapp /y
net start comsysapp

Then re-try the import. That re-registers the COM+ core components. I've seen this fix stubborn version errors after a Windows update.

Why This Works

COM+ applications store their version inside the application file metadata. When you export from a 64-bit Server 2019 to a 2016 machine, or from a Windows 10 build to a Server 2012 R2, the version numbers can mismatch. The COM+ catalog sees the discrepancy and refuses to overwrite—it's protection against corruption. Deleting the old app or re-exporting from the correct source resets that mismatch.

The regsvr32 trick forces the COM+ catalog to re-read its own DLLs, which clears out stale version cache.

Less Common Variations

Sometimes you get this error even when the versions match. That usually means corrupted COM+ registration. Try this:

Export the app as a .COM file again from the source server, choosing "Export as application" and making sure you check "Export user identities" if needed.
If the app was installed via MSI, uninstall it, then re-run the MSI as administrator. I saw a case where a user installed an MSI without admin rights, and it registered the COM+ app as a different version.
Check the event log under Application and Services Logs > Microsoft > Windows > COM+. You'll often see a more specific error code (like 0x80110401 or 0x80110407) that points to a missing dependency.

Another scenario: you're trying to import a 32-bit COM+ app into a 64-bit server. That won't work unless you create a 32-bit COM+ partition. Go to Component Services > Computers > My Computer > COM+ Partitions, create a new partition, and set it as the default for 32-bit apps. Then import your file into that partition.

Preventing This Next Time

Always export COM+ applications from the same source environment you're deploying to. If you have a staging server and a production server, keep their Windows builds in sync—same major version, same service pack level. Use the Export as application option and name the file with the version number (e.g., PrintSpoolerCOM_v1.2.COM).

Before importing, check the .COM file with Notepad—it's XML at the top. Look for <applicationVersion> and compare it to the target app's version in Component Services. If they don't match, don't bother trying; re-export from the right machine.

And if you're using Group Policy or scripts to deploy COM+ apps, test on a clean VM first. I've had clients deploy a version from a dev machine to 50 servers and hit this error on every one. Save yourself that headache.