COMADMIN_E_NOTCHANGEABLE (0X8011042A) Quick Fix: Unlock Disabled COM+ Objects

What the 0X8011042A Error Actually Means

If you're seeing COMADMIN_E_NOTCHANGEABLE (0X8011042A) in Component Services or the Event Viewer, here's the short version: COM+ has locked down a component and won't let you change it. I've seen this in two real-world scenarios: (1) someone tried to reconfigure a COM+ application while it was still running, and (2) a permissions screw-up after a Windows update nuked the COM+ partition settings. Either way, the fix follows the same flow. Start simple, get complex if that fails.

The 30-Second Fix: Restart the COM+ System Application

Half the time, the error is just a stale lock on the COM+ catalog. Here's the quickest fix I know — a client last month hit this after a botched Windows 11 23H2 patch. Do this:

1. Open Component Services (run comexp.msc).
2. Expand Component Services > Computers > My Computer > COM+ Applications.
3. Right-click COM+ System Application and choose Shut down.
4. Right-click it again and choose Start.

Now try whatever change you were making. If it works, you're done. If not, move on.

The 5-Minute Fix: Re-register the COM+ Core DLLs

Sometimes the error pops because the core COM+ libraries (oleaut32.dll, comsvcs.dll) got corrupted or unregistered. I've seen this on Server 2022 after a security update went sideways. Run these commands in an elevated Command Prompt (Win+X, Terminal Admin):

cd /d %windir%\system32\regsvr32 /s oleaut32.dll\regsvr32 /s comsvcs.dll\regsvr32 /s colbact.dll\regsvr32 /s es.dll

After each, you should get a confirmation dialog — if any fail with an error, you've got a deeper corruption. But usually they all succeed. Reboot, then try the COM+ change again.

The 15+ Minute Fix: Reset COM+ Partition Permissions (Registry Edit)

Here's where it gets real. The error 0X8011042A often traces back to broken permissions on the COM+ partition in the registry. Microsoft's official fix involves a registry key that controls access to the COM+ catalog. Do this carefully.

First, back up the registry: File > Export. Save the whole thing.

Then navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\

Right-click the COM3 key, select Permissions. Make sure SYSTEM and Administrators have Full Control. Also check Everyone has Read. If not, add it.

Next, delete this key (if it exists):

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\PartitionCache

That cache can get stale and lock components. Deleting it forces COM+ to rebuild it.

Finally, restart the COM+ System Application service from the Services console (services.msc). Then try your change.

If Nothing Works: Rebuild the COM+ Catalog

Last resort — I've only needed this twice in ten years. It wipes all custom COM+ applications, so export them first (right-click each app > Export). Then:

1. Stop the COM+ System Application service.
2. Open an elevated command prompt.
3. Run: reg delete HKLM\SOFTWARE\Microsoft\COM3 /f
4. Reboot. COM+ will recreate the catalog on startup.

Re-import your apps. This has fixed the error every time I've tried it.

Pro tip: If the error happens when you try to modify a specific third-party COM+ app, check if that app's process (dllhost.exe) is still running. Kill it with Task Manager, then retry. Nine times out of ten, that's the lock.

That's it. Start with the reboot of COM+ System Application. Move to re-registering DLLs. If still stuck, hit the registry permissions. You'll beat 0X8011042A in under 20 minutes.