COMADMIN_E_COMP_MOVE_LOCKED (0X8011042D) Fix – Component Move Locked

You're managing COM+ partitions on a Windows Server 2019 or Windows 10 machine. You right-click a component under a partition and pick Move. Then you get this message: COMADMIN_E_COMP_MOVE_LOCKED (0x8011042D). It says the component is locked and can't be moved. This usually happens after you install an update or when another admin has the component open in the Component Services snap-in.

Root Cause

What's actually happening here is that COM+ puts a write lock on a component when any administrative session has it open for editing. The lock prevents two people from moving or changing the same component at the same time. But sometimes the lock doesn't release properly after you close the console. A common trigger: you or another admin opened the component's properties, then closed the window, but the COM+ catalog still thinks it's in use.

The reason step 3 below works is because we tell the catalog to release all stale locks. The component itself is fine — the catalog is just being stubborn.

Fix: Unlock the Component and Move It

Skip restarting the COM+ service — that's overkill. The real fix is to force the lock to clear. Here's the step-by-step.

1. Close all Component Services windows. Every admin that has the snap-in open should close it. If you're alone, just close yours.
2. Kill the dllhost process that might hold the lock. Open Task Manager, go to Details tab. Look for dllhost.exe processes. Right-click each one and End Task. If you see one using high memory, that's often the culprit. But be careful — don't kill dllhost processes running under SYSTEM unless you're sure they're for COM+.
3. Clear the COM+ catalog lock. Open Command Prompt as Administrator. Run:
   

   net stop COMSysApp
   net start COMSysApp

   This restarts the COM+ System Application service. It forces the catalog to drop all locks.
4. Reopen Component Services. Go to Start, type dcomcnfg and press Enter. Expand Component Services, then Computers, then My Computer, then COM+ Applications. Find your partition and the component you want to move.
5. Move the component. Right-click the component, pick Move. Select the target partition (or application) and click OK. This time it should work.

If It Still Fails

Check these things if the error comes back:

• Check if the component is in use by an application. Open Task Manager, look for processes using that specific COM+ app. You can identify it by the Application ID in the COM+ console (right-click the application, Properties, look at the Application ID GUID). Then match that GUID in Task Manager under the Details tab — it shows as a command line argument for dllhost.exe.
• Try moving from a different account. Log in as a domain admin or local SYSTEM account (use psexec -i -s cmd.exe to run a command prompt as SYSTEM). Then launch dcomcnfg from that command prompt and try the move.
• Check for pending updates. A Windows Update that didn't finish can leave COM+ in a weird state. Run wusrmgr or go to Settings > Windows Update and install any pending updates. Reboot.

The lock is almost always a stale session. The service restart clears it. If you still see 0x8011042D after that, something else is holding the component — like a third-party management tool or an antivirus that hooks into COM+. In that case, disable the tool temporarily and try again.