💻 Where This Error Shows Up
I first ran into 0x80040154 when the Windows Photos app wouldn't launch at all, just an instant error dialog and nothing else. A quick search showed I wasn't alone — the same error code pops up when installing Microsoft Office, running a Windows Cumulative Update, opening Device Manager or certain Control Panel applets, or launching third-party software that relies on Windows' COM (Component Object Model) framework. Because the underlying cause differs depending on when it hits, the fastest way to solve it is to match your situation to the right cause below rather than trying every fix at random. That's exactly what this post is built to do.
⚠️ What "Class Not Registered" Actually Means
Underneath the scary-looking hex code, 0x80040154 simply means Windows tried to load a COM "class," a registered software component that handles a specific task like opening an image, rendering a Control Panel page, or applying an update, and couldn't find it in the registry where it expected it. It's not a virus and it's not usually a sign of serious corruption; it's closer to a missing address in a phone book. The dialog itself is usually short: just "Class not registered" with an OK button, sometimes with the error code appended, and closing it does nothing to fix the underlying registration gap.
🔍 Causes and Fixes at a Glance
Here's a quick map of the most common causes and which fix below addresses each one, so you can jump straight to the section that matches your situation:
| Cause | Typical Trigger | Fix |
|---|---|---|
| Corrupted system files | Happens after updates, sudden shutdowns, or malware cleanup | SFC + DISM scan |
| Specific DLL unregistered | One app or feature fails consistently, others are fine | Re-register with regsvr32 |
| Corrupted Windows Update components | Only happens during Windows Update / Cumulative Update | Windows Update troubleshooter |
| Damaged user profile | Error follows you across multiple apps on one account only | Test with a new user account |
| Misconfigured DCOM permissions | Business/IT-managed PCs, after a policy change | Check dcomcnfg settings |
🛠️ Walking Through Each Fix
Row 1 — Run SFC and DISM
Open Command Prompt as administrator and run the two scans below in order. SFC checks and repairs protected system files, and DISM repairs the underlying Windows image that SFC pulls from, so running both back to back gives the best chance of catching whatever is broken.
DISM /Online /Cleanup-Image /RestoreHealth
Row 2 — Re-register the Specific DLL
If only one app or feature triggers this error, check Event Viewer (Windows Logs → Application) around the time of the crash for a DLL name tied to the failure, then re-register it with regsvr32 from an elevated Command Prompt.
Row 3 — Run the Windows Update Troubleshooter
If the error only shows up while installing a Windows Update or Cumulative Update, go to Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run, and let it detect and repair the update components automatically.
Row 4 — Test With a New User Account
Go to Settings → Accounts → Family & other users → Add account, create a local test account, sign in, and try the same app or update. If it works there, your original user profile is the corrupted piece, and you'll need to migrate your data to a fresh profile.
Row 5 — Check DCOM Configuration
Press Win + R, type dcomcnfg, and navigate to Component Services → Computers → My Computer → DCOM Config. This is mostly relevant on work or managed PCs where a Group Policy change altered COM permissions; if you're not on a managed device, you can usually skip this step.
🧩 Still Blocked? Extra Steps
If SFC and DISM both come back clean and the app-specific DLL fix didn't apply to your case, check whether the error started right after installing or removing a specific piece of software, since some installers deregister shared COM components on uninstall. Rolling that program back or reinstalling it can restore the missing registration. It's also worth confirming Windows itself is fully up to date, since Microsoft periodically ships COM-related fixes through standard Cumulative Updates. As a last resort for a single stubborn app, a full uninstall and reinstall of just that app (not the whole OS) resolves the remaining edge cases.
❓ FAQ
Q. Is 0x80040154 a sign of malware?
A. Not typically. It's almost always a registration or system-file issue, though it's still worth running a scan if the error appeared alongside other unusual behavior.
Q. Will SFC /scannow delete any of my files?
A. No, it only repairs core Windows system files and does not touch your personal documents, photos, or installed apps.
Q. Do I need to know which DLL is failing before I start?
A. No — start with SFC and DISM first, since that fixes the majority of cases without needing to hunt down a specific file.
Q. Can I get this error on Windows 10 as well as Windows 11?
A. Yes, 0x80040154 is a general COM error that isn't tied to one Windows version, and the fixes above apply to both.
✅ Wrap-Up
#0x80040154 #ClassNotRegistered #WindowsError #COMError #SFCDISM #WindowsUpdateError