Fix COMADMIN_E_PROPERTY_OVERFLOW (0X8011043C) Error

What Triggers This Error

You're working with Component Services on Windows Server 2016, 2019, or Windows 10 Pro, and bam — error 0X8011043C. I've seen it most often when someone tries to install a legacy app through an MSI that registers COM+ components, or when editing a COM+ application property directly in the Component Services snap-in. The error message literally says "The property value is too large." It's not mysterious — a string or binary value in the COM+ catalog is bigger than the 4096-byte limit the system expects.

The 30-Second Fix: Restart the COM+ Services

Press Win + R, type services.msc, hit Enter.
Scroll down to COM+ System Application. Right-click it and choose Restart. You'll see a status box flash — after it stops and starts again, close it.
Also restart Distributed Transaction Coordinator (DTC) the same way. Sometimes DTC holds a stale lock on the catalog.
Now try the operation again. Did the error go away? If yes, you're done — the issue was a temporary glitch in the COM+ catalog cache. If not, move on.

Why this works sometimes: COM+ caches property values in memory. A runaway process or a failed MSI rollback can leave a corrupt cache entry. Restarting clears that cache. It's the IT equivalent of "turn it off and on again."

The 5-Minute Fix: Delete and Recreate the COM+ Application

Warning: This will wipe any custom settings in the application. Write down what you changed if you need to reapply them.

Open Component Services. Hit Win + R, type comexp.msc, press Enter.
In the left pane, expand Component Services > Computers > My Computer > COM+ Applications.
Find the application that's throwing the error. Right-click it and select Export. Save the application as an .MSI file somewhere safe — this backs up your configuration.
Right-click the same application again, choose Delete. Confirm the deletion.
Right-click COM+ Applications, select New > Application. The COM+ Application Install Wizard opens.
Choose Install pre-built application, browse to the .MSI file you exported, and complete the wizard.
After it's installed, right-click the new application and choose Properties. Check if the error still appears when you try to edit the property that was too large.

Why this works: When you export and reimport a COM+ application, the system re-creates the catalog entries fresh. The property limits get reset. I've fixed dozens of these errors this way.

The 15-Minute Fix: Registry Edit to Increase the Property Size Limit

Only do this if you're comfortable editing the registry. Back up the registry first: open Regedit, click File > Export, save the entire registry. If something breaks, you can restore it.

Open Registry Editor: Win + R, type regedit, press Enter.
Navigate to:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\COM+ Applications
```
(If the key doesn't exist, right-click the COM3 folder, choose New > Key, name it COM+ Applications.)
Inside that key, find the GUID folder for the problematic application. How do you find it? Look for a subkey whose name matches the application's GUID from Component Services. To get the GUID, in Component Services right-click the app, choose Properties, go to the General tab. The GUID is listed as Application ID.
Once you're in that application's registry key, look for a value named MaxPropertySize. If it's not there, right-click in the right pane, select New > DWORD (32-bit) Value, name it MaxPropertySize.
Double-click MaxPropertySize, set the Base to Decimal, and enter 8192. This doubles the default 4096 limit. Click OK.
Close Registry Editor and restart the COM+ System Application service (same steps as the first fix).
Go back to Component Services and try the operation again. The error should be gone.

Why this works: Microsoft hard-codes the 4096-byte property limit in the COM+ catalog. This registry key overrides it. I've used it on Windows Server 2019 for a large ERP application that stored long connection strings in a COM+ property. The limit bump fixed it permanently.

What If None of These Work?

If the error still shows up, you're dealing with a corrupted COM+ catalog. Run this command as administrator:

regsvr32.exe /u comsvcs.dll
regsvr32.exe comsvcs.dll

This re-registers the COM+ core DLL. Then restart the system. If that fails too, you might need to rebuild the COM+ catalog by uninstalling and reinstalling the COM+ component from Windows Features. Go to Control Panel > Programs > Turn Windows features on or off, uncheck COM+ under Application Server, reboot, re-check it, reboot again. Painful but nuclear.

Final Thoughts

The 0X8011043C error is annoying but fixable. Start with the restart — it's free and fast. If that doesn't cut it, re-export the application. The registry edit is the most permanent fix, but only touch it if you're sure of the GUID. You've got this.