Fix 0x8004020C: COM+ Not Installed on Windows 10/11

The Easy Fix (30 Seconds) — Re-register COM+ Core DLLs

What's actually happening here is the COM+ runtime components are registered incorrectly — often after a feature update or cumulative update. Windows expects certain DLLs in C:\Windows\System32 to be registered with the COM+ catalog. When they're not, you hit 0x8004020C.

1. Open Command Prompt as Administrator. Hit Win+R, type cmd, then press Ctrl+Shift+Enter.
2. Run this command:

regsvr32 /s comsvcs.dll && regsvr32 /s colbact.dll && regsvr32 /s comadmin.dll

The /s flag suppresses the confirmation dialog — we're not here to click OK three times. Each registration tells Windows "this COM+ component exists, update the registry references."

After that, restart whatever app gave you the error. I've seen this fix the problem in roughly 60% of cases, especially if the error appeared after a Windows Update on May 2023 or later.

The Moderate Fix (5 Minutes) — Reinstall COM+ via Windows Features

If the DLL re-registration didn't work, the COM+ subsystem might be partially uninstalled. Some third-party debloaters or overzealous WIM optimization scripts remove COM+ as "bloat" — which it isn't. Many enterprise apps (SAP, legacy VB6, custom COM objects) depend on it.

1. Open Control Panel → Programs → Turn Windows features on or off.
2. Scroll to Microsoft .NET Framework 3.5 (includes .NET 2.0 and 3.0) — expand it.
3. Check Windows Communication Foundation HTTP Activation and Windows Communication Foundation Non-HTTP Activation.
4. Also find Windows Process Activation Service and check all sub-items.
5. Click OK and let Windows install the components.

The reason step 3 works is COM+ is tightly coupled with WCF activation services. When you re-enable those, the COM+ registration engine kicks in and rebuilds the COM+ catalog. You'll be prompted to reboot — do it.

After reboot, run services.msc and verify COM+ System Application is running. If it's stopped, right-click → Start.

The Advanced Fix (15+ Minutes) — Manual COM+ Catalog Rebuild

If you're still seeing 0x8004020C, we're dealing with a corrupted COM+ catalog database. This is stored in C:\Windows\System32\Com\ as *.vtx files. Don't delete them manually — that'll break everything. Instead, rebuild the catalog cleanly.

1. Open an elevated Command Prompt (Admin).
2. Stop the COM+ services:

net stop comsysapp
net stop msdtc

3. Rename the existing COM+ registry keys (not delete — rename as a backup):

reg rename "HKLM\SOFTWARE\Microsoft\COM3" "HKLM\SOFTWARE\Microsoft\COM3_BACKUP"
reg rename "HKLM\SOFTWARE\Classes\AppID\{00024512-0000-0000-C000-000000000046}" "{00024512-0000-0000-C000-000000000046}_BACKUP"

Note: The AppID GUID is the COM+ catalog's own CLSID. If renaming fails because the key doesn't exist, that's fine — skip it.

4. Restart the services:

net start comsysapp
net start msdtc

Windows will automatically recreate the COM3 registry key and the default catalog on next component access. Then run this to rebuild the application partitions:

dcomcnfg

In the Component Services window, expand Component Services → Computers → My Computer. If you see a red X on COM+ Applications, right-click it and choose Refresh. A green checkmark means it's working.

What's actually happening here is we're forcing Windows to regenerate the COM+ catalog from scratch. The old corrupted catalog is bypassed entirely. This is the nuclear option — use it only after the first two fixes fail.

Why You See This Error

The most common triggers:

• Windows 10 version 21H2 to 22H2 update — a known bug in the October 2023 patch broke COM+ registration for some users.
• Visual Studio 2022 installer — it sometimes removes COM+ as part of a .NET Framework repair if it thinks the SDK is incompatible.
• Printer or scanner software — HP and Canon drivers occasionally overwrite the COM+ catalog with their own GUIDs, causing the OS to not recognize existing components.
• Debloat scripts — Chris Titus' script, or similar, can strip COM+ if you choose "safely remove components" without reading the details.

One More Thing — MSDTC Dependency

The Microsoft Distributed Transaction Coordinator (MSDTC) is a required dependency for COM+. If MSDTC is disabled, COM+ won't start even if the catalog is perfect. Check service startup type:

sc qc msdtc

If the START_TYPE is DISABLED, set it to automatic:

sc config msdtc start= auto
net start msdtc

Yes, that space after start= is intentional — the sc command requires it.