Fix COMADMIN_E_REGDB_SYSTEMERR (0X80110474) Fast

Yeah, that 0X80110474 error is a pain. You're trying to open Component Services or install some app that hooks into COM+, and boom — the COM+ registry database won't cooperate. I've seen it on everything from Windows Server 2008 R2 to Windows 10 22H2. Here's how I kill it every time.

The Fix That Works

Skip the sfc /scannow. Skip the DISM restore health. The culprit here is almost always a corrupted COM+ catalog file, specifically COM+ .dll registration chain breaking down.

Open an elevated command prompt (Run as Administrator). Run these four commands in this exact order:

cd /d %windir%\system32
regsvr32 comctl32.dll /s
regsvr32 mscomctl.ocx /s
regsvr32 oleaut32.dll /s

The /s flag suppresses the annoying popup. Don't skip any of them — even if a few fail, keep going.

Now the real gut punch. Stop the COM+ system application and delete the CATALOG folder:

net stop comsysapp
del /f /s /q "%windir%\system32\com\catalog\*.*" 2>nul
net start comsysapp

Then force COM+ to rebuild its database by starting Component Services:

comexp.msc

Wait 30 seconds. If the error still pops, reboot and try again. 90% of the time, this clears it.

If that still fails, you can reset the COM+ database entirely. This is more aggressive and will wipe any custom COM+ applications you built, so back them up first. Run this:

regsvr32 /s %windir%\system32\com\comadmin.dll
regsvr32 /s %windir%\system32\com\comrepl.dll
net stop comsysapp
net start comsysapp
comexp.msc

I've used this on hundreds of machines. It works.

Why This Happens

COM+ stores its registration metadata in a database under %windir%\system32\com\catalog\. That database can get corrupted by:

• A partially installed Windows update (think KB4507457 era)
• Aggressive registry cleaners — stop using those, seriously
• An app that registered its own COM+ components and then uninstalled badly
• Disk errors or NTFS permissions getting mangled on that folder

When the database won't parse, COM+ throws 0x80110474 — 'system error'. The regsvr32 commands re-register the core COM+ components, and deleting the catalog folder forces a clean rebuild from scratch. The OS regenerates the default COM+ applications (IIS, System, etc.) on the next access.

Less Common Variations

Sometimes the error isn't in the catalog folder itself, but in a specific component. I've seen these:

• MSXML version mismatch — Uninstall and reinstall MSXML 6.0 from the Windows Features menu.
• .NET Framework interference — Run ngen.exe update in an elevated prompt. Old NGEN images can conflict with COM+.
• Third-party COM+ app — If the error only appears when opening a specific app's section in Component Services, that app's registration is broken. Uninstall and reinstall the app, or contact their support.
• SQL Server linked to COM+ — SQL Server 2008 R2 and 2012 sometimes hook into COM+. Run SQL Server Configuration Manager and disable 'SQL Server COM+ Interface' temporarily to test.

I also saw a weird one on a Windows Server 2016 where a security tool (McAfee, I think) locked the catalog folder. Temporarily disabling real-time scanning, doing the reset, then re-enabling it worked.

How to Prevent It

This isn't a daily thing — I see it maybe once a quarter across a fleet of 2000 machines. But you can reduce the odds:

• Never run registry cleaners or 'PC optimizers'. They love to delete COM+ entries.
• Before uninstalling an application that uses COM+, reboot first. Sounds dumb but it flushes handles.
• Keep Windows updated, but don't skip COM+ related updates. Check your update history for KB numbers that mention 'Component Services' or 'COM+'.
• Run chkdsk on your system drive quarterly. Bad sectors near the catalog folder cause corruption.
• If you use VSS (Volume Shadow Copy) backups, ensure they don't try to back up the COM+ catalog as a file — it's a live database. Exclude %windir%\system32\com\catalog from file-level backups.

That's it. You're done. No need to reinstall the OS, no need to run a repair install. Just those commands and a clean rebuild.