Windows activation error 0xC004E003 means the Software Licensing service could not validate your licence. It appears most often after an in-place upgrade or a large cumulative update, when the licensing store is left holding data Windows can no longer verify. Rebuilding that store and re-registering the licence resolves it in most cases.
What causes 0xC004E003
Validation is a check that the licence on the machine still matches what Microsoft recorded. When that check fails, Windows cannot confirm the installation is genuine and reports this code.
The usual triggers:
- An in-place upgrade, for example Windows 10 to Windows 11, where the old licence data survives but no longer validates against the new build
- An interrupted cumulative update leaving licensing files half-written
- Damaged system files affecting the licensing components
- System tuning or cleanup tools that removed licensing files they should have left alone
A genuine key that previously worked and now reports this has almost always hit one of the first two.
Fix 1: Re-register the licence files
The least invasive step, and often enough on its own.
- Open Command Prompt as administrator
- Type slmgr /rilc and press Enter
- Restart the PC
- Retry activation
This reinstalls the licence files Windows ships with, without touching your product key.
Fix 2: Repair system files
If re-registering did not help, the licensing components themselves may be damaged. Run these in order, since DISM repairs the source that SFC draws from.
- Open Command Prompt as administrator
- DISM /Online /Cleanup-Image /RestoreHealth and wait. This can take fifteen minutes or more and may appear stuck around 20 percent. Let it run
- sfc /scannow and wait for it to complete
- Restart the PC
- Retry activation
Running SFC before DISM is a common mistake. If the component store is damaged, SFC has nothing clean to repair from and reports failures it cannot fix.
Fix 3: Rebuild the licensing store
If the error survives both steps above, discard the cached licensing data.
- Open Command Prompt as administrator
- net stop sppsvc
- cd %windir%\ServiceProfiles\LocalService\AppData\Local\Microsoft\WSLicense
- ren tokens.dat tokens.bak
- net start sppsvc
- slmgr /rilc
- Restart, then reinstall your key with slmgr /ipk YOUR-KEY-HERE and activate with slmgr /ato
Have your product key available before you begin. If the licence is tied to a Microsoft account it will return on its own, but if the PC uses a local account you will need to enter the key again.
Fix 4: Check the licensing services are running
- Press Windows + R, type services.msc and press Enter
- Confirm Software Protection is running and set to Automatic (Delayed Start)
- Confirm Windows Update is not disabled. Licensing depends on it in places
- Restart both, then retry activation
Third-party debloating and privacy scripts frequently disable these services. If you have run one, this is a likely cause.
When the licence genuinely will not validate
If every step above fails and activation still reports 0xC004E003, the licence itself may no longer be valid for this machine, whether because it has exceeded its activation count or because hardware has changed since it was issued.
A hardware change produces error 0x803FA067 more often, so read that first if you have replaced a motherboard recently. If you bought your key from us, contact support, since every LicenceHouse key carries a 30-day warranty.
Frequently asked questions
Did an upgrade to Windows 11 break my licence?
Not permanently. An in-place upgrade can leave the licensing store in a state the new build cannot validate, which is what this error reports. Re-registering the licence files usually restores it without a new key.
How long does DISM take?
Commonly ten to thirty minutes depending on the machine. It often pauses around 20 percent for several minutes. Interrupting it can leave the component store worse than before, so let it finish.
Will these steps delete my files?
No. Everything here touches licensing components only. Your documents, applications and settings are unaffected.
Do I need my product key before starting?
Have it to hand. Fixes 1, 2 and 4 do not require it. Fix 3 may, if the licence was not linked to a Microsoft account.
Related guides and products
| Resource | Link |
|---|---|
| Error 0x803FA067 after a hardware change | Read the guide |
| Error 0x80070057 explained | Read the guide |
| Error 0xC004F034 explained | Read the guide |
| All Windows licence keys | Browse collection |