0x80070422

Windows Licensing Service Failure: Fix it Fast

Windows Errors Intermediate 👁 10 views 📅 Jun 13, 2026

This error shows up when Windows can't start the Software Licensing service. I'll show you the two-step fix that works 90% of the time.

I know this error is infuriating

You're trying to activate Windows, and instead you get that cryptic "Software Licensing Service Reported That the Product Key Is Not Found" or "Licensing Service Failure" message. It pops up when you're in a hurry — maybe you just reinstalled Windows 10 or 11, or swapped a hard drive. The error code is usually 0x80070422, but sometimes it's just a generic "Windows license not valid." Let's fix it, no BS.

The fix: Restart the Software Licensing service

In 90% of cases, the service is simply stopped or disabled. Here's how to get it running again.

  1. Press Win + R, type services.msc, hit Enter.
  2. Scroll down to Software Licensing (or "Software Protection" on some older Windows 10 builds).
  3. Right-click it and select Properties.
  4. If the service isn't running, click Start. Then set the Startup type to Automatic (not Automatic (Delayed Start)).
  5. Click Apply, then OK.
  6. Now open Command Prompt as admin — right-click Start, choose "Windows Terminal (Admin)" or "Command Prompt (Admin)".
  7. Type:
    slmgr /rearm
    and press Enter. This resets the activation timer.
  8. Reboot your PC. Then go to Settings > Update & Security > Activation and click "Activate."

I've seen this work on everything from a Dell Inspiron running Windows 10 Home to a custom rig with Windows 11 Pro. The key is making sure the service starts automatically — not delayed — because some activation checks happen right at boot.

Why this works

Windows uses the Software Licensing service to validate your product key or digital license. When that service is disabled or stopped, Windows can't talk to the licensing server, so it throws up the failure error. It's often caused by third-party antivirus (looking at you, McAfee), Windows updates that reset service settings, or even a corrupted service state after a crash. By restarting the service and resetting the activation timer, you're basically giving Windows a fresh start to negotiate your license.

Setting the startup type to Automatic (not Delayed) is critical here. I've seen Microsoft's own documentation recommend "Automatic (Delayed Start)" for some services, but for Software Licensing, that delay can cause timeouts — especially on systems with SSDs where boot is fast. Stick with plain Automatic.

Less common variations and fixes

Sometimes the above doesn't cut it. Here are the real-world scenarios I've hit over the years:

1. Corrupted Software Licensing token store

If restarting the service didn't work, the token store (where Windows caches your activation data) might be corrupt. Here's the fix:

  1. Open Command Prompt as admin.
  2. Type:
    net stop slsvc
    to stop the service.
  3. Then delete the token store folder:
    del /f /q %SystemRoot%\System32\spp\store\2.0\*
  4. Restart the service:
    net start slsvc
  5. Run:
    slmgr /rilc
    to reinstall the license files.
  6. Reboot and try activating again.

This one saved me on a Lenovo ThinkPad where the user had used a third-party activation tool that borked the token store. Note: This will wipe any custom KMS configuration, so if you're on a KMS volume license, you'll need to re-enter the KMS key.

2. Windows 11 version mismatch

If you upgraded from Windows 10 to 11 and the error appeared, you might have an edition mismatch. For example, trying to use a Windows 10 Pro product key on a Windows 11 Home install. Check your edition by going to Settings > System > About. If it's wrong, you'll need to do a clean install with the right edition, or use slmgr /ipk [new-key] with a generic key for the correct edition. I've seen this trip up people who downloaded the wrong ISO from Microsoft's media creation tool — it defaults to Home for some systems.

3. Time and date off by more than 24 hours

It sounds stupid, but I've seen this. Windows licensing checks rely on accurate time to validate certificates. If your CMOS battery is dead or you moved time zones and didn't sync, the activation can fail silently. Go to Settings > Time & Language > Date & time, turn on "Set time automatically," then sync. Restart the Software Licensing service and try again.

Prevention — keep this from coming back

Once you've fixed it, you don't want this popping up again. Here's how to lock it down:

  • Never disable the Software Licensing service manually. I know some "optimization" guides recommend disabling services, but leave this one alone. It's not a resource hog.
  • If you use a third-party firewall or antivirus, whitelist C:\Windows\System32\sppsvc.exe. Some aggressive security suites block it, thinking it's phoning home. It is — to Microsoft's activation servers — and that's normal.
  • Keep your Windows up to date. Microsoft has patched several activation-related bugs in cumulative updates. Run Windows Update monthly.
  • Back up your digital license. If you bought a digital license (common on Windows 11), link it to your Microsoft account. That way, after a motherboard swap or a fresh install, you can just sign in and activate without a key. Go to Settings > Accounts > Your info and make sure you see "Windows is activated with a digital license linked to your Microsoft account."

That's it. The service restart and slmgr command fix should get you activated in under 5 minutes. If it doesn't, the token store reset or edition check will. I've walked hundreds of users through this — it's one of those errors that feels scary but has a boring, simple solution.

Was this solution helpful?