How to fix the "class not registered" error (0x80040154) in Windows 11

Have you ever tried to open an app or click a link in Windows 11, only to find nothing happens? Maybe certain file types suddenly won’t open, or programs fail to launch even though everything seems fine. These frustrating symptoms can be the first sign of a deeper issue: the “Class Not Registered” error. This problem often surfaces after system changes like updates, software installs, or configuration adjustments. Because it affects multiple applications at once, users can waste time troubleshooting individual programs without seeing any improvement, making it harder to pinpoint than a typical app-level error.

The “Class Not Registered” error in Windows 11 can disrupt multiple apps at once, prevent file types from opening, and break links, sometimes spreading across system processes. In this article, we’ll cover the broader implications of this error, including the risks of leaving it unresolved, and show the most reliable ways to fix it

Impact of the “Class Not Registered” error in Windows 11

The “Class Not Registered” error (0x80040154) is a specific signal that Windows 11 can’t find a required Component Object Model (COM) class in the system registry. Unlike a standard software crash, this error indicates a breakdown in the communication layer between the operating system and its installed programs.

In technical environments, this error almost always points to a deep-seated registration failure rather than a minor application bug. It frequently appears after incomplete Windows feature updates or when aggressive registry cleaners accidentally delete critical COM or DCOM entries.

• Architecture mismatches: A significant cause is the conflict between 32-bit and 64-bit components, where an application attempts to call a class registered only in a different registry hive.
• Corrupted system DLLs: System-level files that handle shared tasks may become unregistered during failed in-place upgrades, making valid Windows components invisible to the OS.
• Systemic vs. localized: While a typical bug only breaks one program, 0x80040154 often affects multiple apps because the underlying class factory is missing system-wide.

» Here’s how to disable Windows updates and manually re-enable Windows updates

Practical effects on the end user

This error manifests in ways that directly disrupt a user’s workflow and often makes the operating system appear broken. Because COM components are shared services, a single failure can prevent the most basic tasks from being completed.

1. Launch failures: Applications may open briefly and then close immediately or display opaque error dialogs that offer no clear path to a fix.
2. Broken file associations: Double-clicking files like PDFs or images may result in no action because the handler responsible for opening them is no longer registered.
3. Inaccessible system tools: In severe cases, core Windows features like the Settings app or Control Panel applets will refuse to load.

The severity of this issue is high because it signals that the OS-level infrastructure is failing to provide required services to applications.

Risks of unresolved registration errors

Leaving this error unaddressed increases systemic risk and can lead to a cascade of failures that eventually necessitate a full system wipe and reinstall. COM registration integrity is a cornerstone of Windows application compatibility and long-term servicing.

• Cascading failures: As Windows updates or new software installations occur, more features may attempt to call the broken class, leading to a growing list of failing applications.
• Update instability: Future Windows updates may fail to install or roll back unexpectedly because the installer cannot validate the existing corrupted components.
• Reduced self-healing: Over time, standard repair tools like System File Checker (SFC) or DISM may become less effective as the registry corruption deepens.

How to fix error 0x80040154 in Windows 11

Repairing a “Class Not Registered” error often requires modifying the Windows Registry or re-registering core system components. Because these areas are vital to the stability of the entire operating system, you must establish a safety net before attempting any technical remediation.

Registry-level changes are not granular; a single mistake can ripple across unrelated applications or even prevent Windows from booting. Creating a restore point and backing up specific registry keys act as “bookmarks” in time, allowing you to undo changes if the system becomes unstable.

Follow these steps to create a system restore point:

1. Type “Create a restore point” in your search bar and click “open”

2. Under the System Protection tab, select your C: Drive and click the Configure button

3. Ensure “Turn on system protection” is selected, then click OK

4. Click the Create button at the bottom of the window

5. Provide a clear description, such as “Pre-Fix 0x80040154,” and click Create to save the state

Follow these steps to export a registry key:

If you plan to edit the registry, exporting the specific key you are working on is the fastest way to recover from a typo or accidental deletion.

1. Press Win + R, type regedit, and press Enter to open the Registry Editor

2. Navigate to the specific folder (key) you intend to modify, then right-click it and select Export from the context menu

3. Choose a safe location like your Desktop, name the file, and click Save

After completing the registry safety steps above, use the methods below to address error 0x80040154 depending on the underlying cause.

» Check out these registry editor challenges and how to overcome them

Take note: Although Methods 1, 2, and 3 are all executed through Command Prompt, they rely on different Windows repair tools and address different underlying causes of the error.

Method 1: Re-register the DLL

This method is designed for IT administrators and users troubleshooting specific “Class Not Registered” errors where the system file is present on the disk but the registry connection is broken.

It is highly effective for fixing registration gaps caused by failed updates or third-party interference.

Follow these steps:

For this example, we’ll use shell32.dll, which is frequently associated with “Class Not Registered” issues in File Explorer.

1. Search “Command Prompt” in the search bar, and select “Run as administrator”

2. Navigate to the core system folder by pasting the following command and pressing Enter: cd C:\Windows\System32

3. Execute the registration command by pasting: regsvr32 shell32.dll Wait for the RegSvr32 dialog box to appear. If it says “DllRegisterServer in shell32.dll succeeded” the registration was successful

4. Click OK and restart your computer to ensure the changes are fully inherited by all system processes

Take note: If you receive an error stating the module was not found, the DLL file may be missing from your system entirely, and you may need to run a system repair tool like System File Checker.

» Find out how to restart a remote computer using Windows

Method 2: System File Checker (SFC)

This method is designed for administrators who suspect that the “Class Not Registered” error is caused by missing or corrupted protected system files. SFC acts as a repair tool by comparing your current Windows files against a known-good backup in the system store.

Follow these steps:

1. Open the Command Prompt as administrator

2. Type the following command and press Enter: sfc /scannow

3. Wait for the scan to reach 100%. Do not close the window while the verification is in progress

4. Review the final message:

• “Windows Resource Protection found corrupt files and successfully repaired them” indicates a likely fix.
• “Windows Resource Protection did not find any integrity violations” means your system files are healthy, and the issue lies elsewhere.

Method 3: Deployment Image Servicing and Management (DISM)

DISM is for users who find that SFC is unable to fix the problem or reports that the “source files” are corrupted. It repairs the actual Windows Image (the component store) that SFC uses for its repairs, pulling fresh data from Windows Update.

Follow these steps:

1. Open the Command Prompt as administrator

2. Type the following command to repair the system image and press Enter: DISM /Online /Cleanup-Image /RestoreHealth

3. Wait for the progress bar to complete; this process can take several minutes depending on your internet connection. Once you see “The restore operation completed successfully,” restart your computer

Important: Run Method 2 (SFC) again immediately after this to ensure all individual files are now fixed using the repaired store.

» Make sure you know how to use the DISM command in Windows 11

Method 4: Windows settings

This method is for users experiencing the error within specific applications, such as the Calculator, Photos, or Mail apps. It targets the app’s individual registration without affecting the rest of the operating system.

Follow these steps:

1. Search “Settings” in your search bar and click “open”

2. Navigate to Apps > Installed apps

3. Find the app causing the error, click the three dots (…), and select Advanced options

4. Scroll down and click Repair. This attempts to fix registrations while keeping your data

5. If the error persists, click Reset. WARNING: This will delete the app’s local data and force a total re-registration

If both fail, go to Settings > Apps > Default apps and ensure the correct program is assigned to your file types

Method 5: PowerShell

PowerShell is for advanced users or situations where the Windows GUI is itself broken or throwing the “Class Not Registered” error. It forces a “deep” re-registration of every Windows app package directly from the source manifests.

Follow these steps:

1. Search “PowerShell” in your windows search bar and click “run as administrator”

2. To re-register all Windows apps for your current account, paste the following command and press Enter: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

3. You’ll see several lines of yellow text indicating the deployment status; ignore any red errors for apps that are currently in use. Once the command prompt returns to a blinking cursor, restart your PC

» Did you know you can paste in PowerShell?

In a managed enterprise IT environment, you can’t afford to run these PowerShell commands manually on every individual workstation. Atera’s RMM platform allows you to deploy these re-registration scripts across your entire fleet of endpoints simultaneously, ensuring global consistency.

By using Atera’s AI Copilot, you can instantly generate and validate these complex PowerShell scripts to target specific errors without writing them from scratch. This centralized approach means you can monitor the success of your repairs from a single dashboard, turning hours of manual labor into a few clicks.

» Find out how to run PowerShell Commands on a remote computer

Keep your systems stable with Atera

Dealing with “Class Not Registered” errors can be a real headache, but getting these registration fixes down is a game-changer for keeping your network running smoothly.

When you pair these technical steps with Atera’s RMM platform, you can clear up these errors across every workstation you manage before they start causing trouble for your users. By centralizing your response, you move away from desk-side visits and toward a more proactive, automated approach to system maintenance.

» Interested? Start a free trial with Atera