Fix COM+ Schema Not Found Error 0X80110481

You're Stuck with a COM+ Error That Blocks Things

I get it. You're trying to work with Component Services, or maybe an app that depends on COM+ won't start, and you're staring at error COMADMIN_E_MIG_SCHEMANOTFOUND (0X80110481). It's frustrating because the message doesn't tell you what to do. Let's fix it.

The Direct Fix: Re-register the COM+ Catalog

The root cause is simple — the COM+ catalog in the registry is missing a schema version entry. This usually happens after a Windows update, a failed uninstall of a program that touched COM+, or a registry cleaner that got too aggressive.

Close Component Services if it's open. Also close any Management Console snap-ins that use COM+.
Open Command Prompt as Administrator. Click Start, type cmd, right-click Command Prompt, and pick Run as administrator.
Run these three commands in order. Copy and paste them one at a time. After each, wait for the success message.

regsvr32 /u comadmin.dll

After this command, you should see a popup saying DllUnregisterServer in comadmin.dll succeeded. If you get a different message, stop here and note the error.

regsvr32 comadmin.dll

You should see DllRegisterServer in comadmin.dll succeeded. That's the one we want.

regsvr32 /i comadmin.dll

This last one triggers the COM+ catalog to re-install its schema. You should see the same success message. If not, we'll need to dig deeper.

After all three succeed, restart your computer. Don't skip this restart. COM+ caches a ton of data, and a cold boot clears it out.

Once you're back in Windows, open Component Services. The error should be gone. Test whatever app was failing.

Why This Works

The COM+ catalog lives in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3. Inside that key, there's a subkey called Schema. The error 0X80110481 means that when COM+ tried to migrate or access a schema version during startup, it couldn't find the expected registry entries. The regsvr32 /i command re-runs the DLL's DllInstall function, which recreates the schema subkey and populates it with the correct version numbers. Unregistering and re-registering the DLL first ensures that the old, corrupted registration is fully stripped away.

Less Common Variations of the Same Issue

Sometimes the standard fix doesn't stick. Here are the scenarios I've seen:

Schema key exists but has wrong version

Open Regedit (as Administrator). Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\Schema. Look for a string value named CurrentVersion. It should be something like 1.0 or 2.0 depending on your Windows version. If it's missing or blank, delete the Schema key entirely (right-click, Delete), then run the regsvr32 /i comadmin.dll command again.

System File Checker needed

If the DLL itself is corrupted or missing, regsvr32 will fail. Run sfc /scannow from an admin Command Prompt. Let it finish — this can take 15-20 minutes. Then re-run the three commands from above.

DCOM permissions are blocking access

Less common, but I've seen it. Open Component Services, expand Computers, right-click My Computer, pick Properties. Go to the COM Security tab. Under Access Permissions, click Edit Default. Make sure SYSTEM and Administrators have Local Access allowed. Apply, restart Component Services.

Prevention: Keep Your COM+ Registry Clean

You don't want to chase this error again. Here's what to do:

Don't use registry cleaners. I'm not a fan of them in general, but they absolutely wreck COM+ entries. The COM+ catalog is tightly structured and fragile. Registry cleaners strip out keys they think are orphaned, and COM+ schema is a frequent casualty.
Before you uninstall software that uses COM+ (like older versions of Office, some Visual Studio tools, or custom in-house apps), check if it has a proper uninstaller. Forced deletion of COM+ components leaves schema fragments behind.
When Windows updates roll out, especially the big feature updates, take a system image or restore point first. I can't count how many times a Windows 10 or 11 feature update has bumped the COM+ schema and left old entries stranded. Having a rollback point saves hours.
Monitor your event logs. Open Event Viewer, go to Windows Logs > System, and filter by source COM+. Any warnings about schema mismatches will appear days before the full error shows up. Catch it early, and a simple regsvr32 /i comadmin.dll is all you'll need.

That's it. You should be back up and running. If you hit a wall, the exact error code 0X80110481 is unique enough that searching it with your Windows version (e.g., 'Windows Server 2022') will narrow it down quick. Good luck.