CO_E_CLASS_DISABLED (0X80004027) Fix for Windows

What’s This Error Really Mean?

You’re trying to open some app or component — maybe a printer driver, maybe a small business accounting tool, maybe a legacy app that came from a CD — and Windows throws CO_E_CLASS_DISABLED (0X80004027). The message: “The component or application containing the component has been disabled.”

This usually happens because something turned off the COM+ class in the registry or in the Component Services snap-in. Could be a security policy, could be a clean-up tool that got aggressive, could be a side effect of an app update. I had a client last month whose print queue died because a vendor’s COM component got flagged by Windows Defender.

Here’s the fix. Start with the fastest, dirtiest trick. If that doesn’t work, move to the moderate one. If it’s still broken, roll up your sleeves for the advanced fix.

Fix 1: The 30-Second Re-Register (Beginner)

This fixes maybe 40% of cases. Windows lost track of the COM class registration. Running regsvr32 on the relevant DLL or OCX re-registers it and often brings it back to life.

1. Press Win + X and choose Windows Terminal (Admin) or Command Prompt (Admin).
2. Type:

   regsvr32 /u [filename]

   then press Enter. Replace [filename] with the actual DLL or OCX file — for example, regsvr32 /u mscomct2.ocx.
3. Then type:

   regsvr32 [filename]

   and press Enter.
4. Restart the app.

If you don’t know the file name, look in the app’s installation folder. Common suspects: mscomctl.ocx, comdlg32.ocx, tabctl32.ocx. If the error came from a specific app, check its event logs or the error detail — it often lists the CLSID or file name. Google that CLSID to find the component.

If regsvr32 says “access denied,” that’s a permissions issue — skip to Fix 3.

Fix 2: Check Component Services (Intermediate – 5 Minutes)

If the quick re-register didn’t do it, the COM+ class might actually be disabled in the Component Services management console. This is especially common on Windows Server editions or locked-down corporate desktops.

1. Press Win + R, type dcomcnfg, and press Enter.
2. In the left pane, expand Component Services > Computers > My Computer > DCOM Config.
3. Find the app or component that’s causing the error. It’s usually listed by its friendly name — if you don’t see it, look in COM+ Applications instead.
4. Right-click the component, choose Properties.
5. Go to the Security tab. Under Launch and Activation Permissions, select Customize, then click Edit.
6. Make sure the user account running the app has Allow for Local Launch and Local Activation. Add Everyone if you’re not sure — but that’s a security risk for production. Better: add your specific user or the Users group.
7. Also check the Identity tab. It should be The interactive user unless the app needs a specific service account.
8. Click OK, close dcomcnfg, restart the app.

I’ve seen this fix dozens of times on Windows 10 Pro machines where IT pushed a security policy that accidentally killed COM+ launch rights. If you’re on a domain, the policy might override — you’ll need an admin to adjust it.

Fix 3: Registry Hack – The 15-Minute Fix (Advanced)

If neither of the above worked, the component is likely disabled at the registry level. This happens when a component’s “Disable” value gets set to 1, or its permissions are locked down. This is the nuclear option — make a backup before touching.

1. Open the Event Viewer (eventvwr.msc). Look under Windows Logs > Application for an error with event ID 100 or 10005. It often lists the CLSID or the DLL path.
2. Open Registry Editor (regedit.exe).
3. Navigate to:

   HKEY_CLASSES_ROOT\CLSID\{clsid}

   Replace {clsid} with the actual GUID from the event log.
4. Look for a DWORD value named Disable. If it exists and is set to 1, change it to 0. If it doesn’t exist, you’re fine — skip.
5. Now check the permissions on that key. Right-click the CLSID folder, choose Permissions. Ensure SYSTEM and Administrators have Full Control, and Users have Read.
6. Also check HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{clsid} — same structure.
7. Close regedit, run regsvr32 again on the DLL (as in Fix 1), restart the app.

One client had a printer driver disabled by a third-party security suite that wrote that Disable=1 value. Took me 20 minutes to find it. Once I flipped it back to 0 and re-registered the DLL, it worked.

When to Give Up and Reinstall

If you’ve tried all three and still get the error, the component itself might be corrupted or a newer version broke compatibility. Uninstall the app, reboot, and reinstall from the original source. If it’s a driver, get the latest version from the manufacturer — not from Windows Update, but from their site. I’ve seen old printer drivers fail on Windows 11 because the COM class was written for an older OS.

Also check if the app needs a dependency like Visual C++ Redistributable or .NET Framework. Missing runtimes can cause this error too.

Good luck. You’ll probably nail it with Fix 1.