Fix 0X80080001 Class Create Failed in Windows

You're in the middle of something — maybe you just clicked a shortcut to open Device Manager, hit Windows Update, or launched a small utility that talks to a background service — and instead of the window you expect, you get a popup that says CO_E_CLASS_CREATE_FAILED with the hex code 0X80080001. The full message reads "Attempt to create a class object failed." This usually appears right after a reboot, sometimes after a Windows Update, and it's especially common on Windows 10 21H2 and Windows 11 22H2 when a COM class is registered but the server that hosts it isn't running.

Let's break down what's actually happening. COM (Component Object Model) is how Windows apps ask other programs to do work. When your app says "I need a class object," Windows looks up the registry, finds the DLL or EXE that should provide it, and tries to start that process. The 0X80080001 code means that lookup succeeded — Windows found the class ID — but the attempt to launch the server failed. Often that's because the DCOM (Distributed COM) service is stopped or disabled, or because the server's account doesn't have the right permissions.

I've seen this error with third-party backup tools, with PowerShell scripts that call Get-WmiObject, and even with the Windows Defender Security Center on some machines. The fix isn't usually complicated, but you need to do steps in the right order. Let's go through them.

Step 1: Restart the DCOM Server Process Launcher

The first thing to try is restarting the service that starts COM servers. It's called "DCOM Server Process Launcher" (service name DcomLaunch). This service is critical — if it's not running, nothing COM-related works. Here's how to restart it:

1. Press Windows + R, type services.msc, and hit Enter.
2. Scroll down to DCOM Server Process Launcher. Right-click it and select Restart.
3. If Restart is grayed out, the service is already stopped. Right-click and choose Start instead.
4. Once it's running, right-click again and select Properties. Make sure the Startup type is set to Automatic. If it's set to anything else, change it to Automatic, click Apply, then OK.

After you restart that service, try launching whatever gave you the error. If it works, you're done. If not, move to step 2.

Step 2: Fix DCOM Permissions for the Component

Sometimes the error is a permission problem. The COM class is registered, but the user account that's trying to create it doesn't have launch or activation rights. You'll need to find the CLSID that's failing. The error message usually doesn't tell you which one, but you can often pinpoint it by looking at the event log.

1. Press Windows + X and select Event Viewer.
2. Go to Windows Logs → System.
3. Look for an event with source DistributedCOM and event ID 10000 or 10001. The description will show the CLSID and the AppID. Write those down.
4. Press Windows + R, type dcomcnfg, and hit Enter. This opens Component Services.
5. Expand Component Services → Computers → My Computer → DCOM Config.
6. Find the component that matches the AppID from the event log. Right-click it and choose Properties.
7. Go to the Security tab. Under Launch and Activation Permissions, select Customize, then click Edit.
8. Add your user account (or the group Users) and give it Local Launch and Local Activation permissions. Check both boxes.
9. Click OK on each dialog to save.

After that, try the failing operation again. If you can't find the specific component, you can try adding your user to the "Distributed COM Users" group, but that's a brute-force approach that might open security holes. Only do that if you're desperate and you're on a single-user machine.

Step 3: Re-register the COM Class

If permissions look fine, the registration might be corrupted. You can re-register the DLL or EXE that provides the class. But you need to know which one. A quick way is to look at the file path from the event log. Usually it's something like C:\Windows\System32\wmidx.dll or C:\Program Files\SomeApp\server.exe.

For a DLL, run this from an elevated command prompt (search for "Command Prompt", right-click, select "Run as administrator"):

regsvr32 /i "C:\path\to\file.dll"

For an EXE that provides a COM class, you usually need to run it with a -regserver flag. For example:

"C:\Program Files\SomeApp\server.exe" -regserver

After re-registering, you might need to reboot. Not always, but don't be surprised if you do.

Step 4: Check for a Broken WMI Repository

Some COM classes rely on WMI (Windows Management Instrumentation). If the WMI repository is corrupt, you'll get 0X80080001 sporadically. Here's how to check and fix it:

1. Open an elevated Command Prompt.
2. Run winmgmt /verifyrepository. If it says "WMI repository is consistent," skip to step 5.
3. If it's inconsistent, run winmgmt /salvagerepository. That tries to rebuild it without losing your settings.
4. If that fails, run winmgmt /resetrepository. This returns WMI to default — you'll lose any custom WMI definitions, but it fixes the error in most cases.

After doing that, restart the Windows Management Instrumentation service (find it in services.msc, same as step 1). Then try again.

Step 5: System File Checker

If none of the above worked, the COM registration might be damaged because of corrupt system files. Run these two commands in an elevated Command Prompt, one after the other:

sfc /scannow

dism /online /cleanup-image /restorehealth

The SFC scan takes a few minutes. DISM can take longer — sometimes 20-30 minutes on older systems. Let them run to completion. Don't close the window even if it looks stuck. After both finish, reboot.

Still failing?

If you've gone through all these steps and the error still pops up, the problem might be a specific third-party program that installed a dodgy COM component. Try a clean boot (type msconfig in Run, disable all non-Microsoft services and startup items, reboot) to see if the error goes away. If it does, enable services one by one until you find the culprit. Also check if the program that triggers the error has an update — I've seen old versions of a few backup utilities throw this error after a Windows feature update.

One last thought: if you're in a corporate environment, Group Policy can block DCOM launching for certain users. That's a bigger issue — ask your IT admin to check the policy "Activation security" under Computer Configuration → Windows Settings → Security Settings → Local Policies → User Rights Assignment. But for most home users, one of the steps above will resolve it.