Windows activation error 0x80070057 translates as the parameter is incorrect. During activation it usually means the Software Licensing service cannot read its own data, either because the licensing store is corrupted or because a pending update has left activation in an inconsistent state. Rebuilding the licensing cache resolves most cases.
What 0x80070057 means here
This is a generic Windows error code that appears in many contexts, including backups, installations and updates. That breadth is why searching for it returns so much irrelevant advice. In an activation context the meaning narrows considerably.
Three situations produce it during activation:
- A corrupted licensing store. The tokens.dat file holding activation data has been damaged, often after an unexpected shutdown during an update
- An incomplete Windows update leaving the Software Licensing service mid-transaction
- Regional or date format settings that the licensing service cannot parse, a less common but genuine cause
Note that a bad product key does not produce this code. If you have just entered a key and seen this, the key is not the problem.
Fix 1: Restart the Software Protection service
Start here, since it is quick and non-destructive.
- Press Windows + R, type services.msc and press Enter
- Find Software Protection in the list
- Right-click it and choose Restart. If Restart is greyed out, choose Start
- Set Startup type to Automatic (Delayed Start) if it is not already
- Retry activation
Fix 2: Rebuild the licensing store
This is the fix that resolves most cases. It forces Windows to discard its cached licensing data and build it again.
- Open Command Prompt as administrator
- Stop the service: net stop sppsvc
- Navigate to the licensing folder: cd %windir%\ServiceProfiles\LocalService\AppData\Local\Microsoft\WSLicense
- Rename the token file: ren tokens.dat tokens.bak
- Start the service again: net start sppsvc
- Re-register the licence: slmgr /rilc
- Restart the PC and retry activation
Renaming rather than deleting matters. If something goes wrong you can rename tokens.bak back and be where you started. Windows generates a fresh tokens.dat automatically on the next start.
Fix 3: Run the Activation Troubleshooter
- Open Settings, then System, then Activation (on Windows 10, Update and Security, then Activation)
- Click Troubleshoot
- Follow whatever it suggests
The troubleshooter only appears when Windows has detected an activation problem, so if you cannot see the option, Windows currently believes it is activated.
Fix 4: Check regional and date settings
Less obvious, but it does happen. A mismatched locale can produce date strings the licensing service cannot parse.
- Open Settings, then Time and language, then Language and region
- Confirm the country or region matches where the PC is actually used
- Under Administrative language settings, check the system locale is sensible
- Restart and retry
Fix 5: Reinstall the product key from the command line
If the store has been rebuilt and the error persists, install the key directly rather than through Settings.
- Open Command Prompt as administrator
- slmgr /upk to uninstall the current key
- slmgr /cpky to clear it from the registry
- slmgr /ipk YOUR-KEY-HERE to install yours
- slmgr /ato to activate
Watch the code that comes back. A different error at this point is the real problem and this one was a side effect. A connection-related code points to error 0x80072F8F, and an invalid-key message points to error 0xC004F050.
Frequently asked questions
Is 0x80070057 caused by a bad product key?
No. This code reflects a problem inside Windows reading its own licensing data, not a rejected key. A bad or mismatched key produces a different code.
Is renaming tokens.dat safe?
Yes, provided you rename rather than delete it and stop the Software Protection service first. Windows rebuilds the file automatically. Keeping the old copy as tokens.bak means the change is reversible.
Will I need to re-enter my product key afterwards?
Sometimes. If the licence was linked to a Microsoft account, it reactivates on its own. If it was activated with a local account, have your key to hand before you start.
Why do I see this error in other parts of Windows too?
0x80070057 is a general-purpose code meaning an invalid parameter was passed. It appears in backups, updates and installations for unrelated reasons. Advice written for those contexts will not fix an activation problem.
Related guides and products
| Resource | Link |
|---|---|
| Error 0x80072F8F explained | Read the guide |
| Error 0xC004F050 explained | Read the guide |
| All Windows licence keys | Browse collection |