Windows System Errors
Windows 0x80040154 Class not registered
Reviewed for reference consistency: April 11, 2026
Class not registered
What 0x80040154 Means
The 0x80040154 error on the Windows System Errors indicates class not registered. This typically occurs due to missing or unprivileged com/activex components.
The 0x80040154 code is a classic COM (Component Object Model) error. It means an application tried to create an instance of a software component that is not correctly listed in the system registry.
How to fix 0x80040154
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
Re-register the affected component
Class not registered means a CLSID is missing from the registry. Re-register the DLL the app reported as failing, from an elevated prompt.
regsvr32 yourcomponent.dllRegister with the matching bitness
A 32-bit component on 64-bit Windows must be registered with the SysWOW64 copy of regsvr32, or the mismatch keeps failing.
%SystemRoot%\SysWOW64\regsvr32 yourcomponent.dllReset the Microsoft Store
For built-in apps, resetting the Store cache rebuilds the registrations that back its components.
wsreset.exeRepair the application
If a specific app raises it, use Settings, Apps, the app, Advanced options, Repair to restore its registry links without a full reinstall.
Technical Background
Windows relies on the registry to 'find' software components. Each component has a unique Class ID (CLSID). When an app asks to use a component, the OS looks up that CLSID to find the associated file (DLL).
If the CLSID is missing from the registry, or if it points to a file that no longer exists, the request fails with 'Class not registered'. This is common after partial uninstalls or when system files are replaced by older versions.
In many cases, this error is a sign of a broken 'plumbing' layer between the app and the operating system. It usually requires re-registering the affected components using the 'regsvr32' tool.
Common Causes
- Missing or unprivileged COM/ActiveX components
- Broken registry links for a required system DLL
- Mismatch between 32-bit and 64-bit application components
Typical Scenarios
- A 32-bit application fails to load a 64-bit system component on a modern Windows version
- The Microsoft Store or a built-in app crashes because its internal registration data is corrupted
What to Know
Re-registering the affected DLL file or performing an in-place repair of the application often restores the missing registry links. In some cases, resetting the Microsoft Store via 'wsreset' fixes this for built-in apps.
Frequently Asked Questions
Common questions about Windows 0x80040154 error
It means Windows cannot find a specific internal part of a program it needs to run. This is usually due to a broken registry link or a missing system file.