Last updated: June 2, 2026
Class Not Registered. This guide explains the root cause and walks you through the proven fix - usually resolved in under five minutes.
net stop sppsvc && regsvr32 sppc.dll && net start sppsvcsfc /scannow in elevated CMD to repair any broken component registrations.slmgr /ato.slmgr /xpr to confirm activation.Run these commands in an elevated Command Prompt (right-click → Run as administrator):
> slmgr /rearm > slmgr /ato > slmgr /xpr
0x80040154 is the "Class not registered" COM error. In an activation context it means a system component the licensing service depends on - usually part of the Software Protection Platform - isn't properly registered with Windows. It sounds technical, but it's a registration glitch that's straightforward to repair.
Restoring the component and re-running activation clears the error. The simplest approach is to let KMSPico re-apply activation, which reinitialises the licensing path. If you're repairing manually, run sfc /scannow to restore system files, ensure the Software Protection service is started, then re-run the slmgr commands from an elevated prompt.
Related repair-type errors: 0x80073712 and 0x80070002.
To understand 0X80040154 it helps to know where Windows keeps its activation state. Two areas matter: the component store, which holds the system files that servicing and licensing rely on, and the token store, which holds the licence tokens themselves. When an update is interrupted or a disk hiccup damages either area, the licensing service can no longer read a consistent picture of your licence and raises an error. This is why simply retrying activation does not help; the data underneath is inconsistent. Repairing the component store with DISM, replacing damaged files with SFC, and then rebuilding the token store restores the foundation so a fresh activation has something solid to write to.
Manually, the fix is a repair sequence: DISM, then SFC, then a token-store rebuild, then re-activation. Automatically, a tool can perform the final activation step once the repairs are done, giving Windows a clean licence to settle on.
Both routes end at the same place: a Windows installation that reports itself as permanently activated. The manual path gives you full visibility into each step, while the automatic path trades that visibility for speed and fewer chances to mistype a command. Neither changes your files or your data; they only write the licensing state that 0X80040154 was blocking.
Because 0X80040154 is rooted in damaged licensing components rather than configuration, the durable fix is to repair the underlying files first and then write a clean activation state on top. Local KMS activation is a good final step here: once the component store and token store are healthy, applying a fresh volume activation gives Windows a known-good licence to work from.
DISM /Online /Cleanup-Image /RestoreHealth to fix the servicing store from Windows Update.sfc /scannow to replace any remaining corrupted files.slmgr /ato and confirm with slmgr /xpr.If you would rather not run each command by hand, a one-click tool performs the same sequence and reports the licensed state when it finishes.
Download the verified release and start activating Windows or Office in seconds.
Archive password: 123456
Download KMSPico RAR