Fix it now
Microsoft publishes no meaning for these codes, so work from what is repairable. The activation request carries licence description files as well as your key, and when those are stale or inconsistent the request cannot be matched. Rekeying does not help. Refresh the licence files and check the clock first.
w32tm /resync
cscript //nologo %windir%\system32\slmgr.vbs /rilc
net stop sppsvc
net start sppsvc
cscript //nologo %windir%\system32\slmgr.vbs /ato
- Check the clock before anything else. Microsoft documents 0x80072F8F as the device date and time being incorrect, and a wrong clock breaks the secure connection activation needs.
slmgr /rilcreinstalls the licence files that ship with Windows. Microsoft documents it as reinstalling the licences held in the system folders and replacing matching ones in the store – it does not remove your product key.- If it still fails, repair the component store with
DISM /Online /Cleanup-Image /RestoreHealth, thensfc /scannow, reboot and retry. - If the machine is behind a corporate proxy, check the one the system services use:
netsh winhttp show proxy. It is not the browser’s.
Do not reach for a new product key. These codes describe the data travelling with the key rather than the key itself, and a second correct key put into the same store fails in exactly the same way.
If the licence files refresh and activation succeeds, you can stop here. If not, the next section covers what else leaves the store in this state.
Why it happens
An activation request is not just a key. Windows builds a package containing the key, a hardware identifier, and a set of licence description files stating which product, edition and add-ons this installation claims to be. Those files live in the licensing store on disk, placed there by Windows setup and by servicing updates, and the service matches the whole package rather than the key alone.
When the description files are missing, half-updated or contradictory, the request describes something that cannot be resolved. That is the useful mental model for this family, and it explains why rekeying is the wrong instinct: the key may be perfectly valid and never get evaluated at all. None of 0x803FA073, 0x803FA074, 0x803FA076, 0xC004E025, 0xC004E006 or 0xC004E008 is published by Microsoft, so the model comes from what repairs the machine rather than from a documented definition.
The store usually reaches this state after an interrupted feature update, an in-place upgrade that did not finish cleanly, a restored disk image, or an installation that has had components stripped out of it. It can also be produced entirely by the network, when an inspecting proxy terminates and re-signs the TLS session so that the request arriving at Microsoft is not the one your machine sent.
Licence description files are stale after an upgrade
You have this one if Activation worked before a feature update or in-place upgrade and has failed ever since, on a machine that is otherwise healthy.
- Run
slmgr /rilcfrom an elevated prompt to reinstall the licence files. - Restart the licensing service:
net stop sppsvcthennet start sppsvc. - Run
slmgr /atoand read the result. - If the store is still inconsistent, run
DISM /Online /Cleanup-Image /RestoreHealth, thensfc /scannow, reboot and retry.
Microsoft documents /rilc as reinstalling all the licences stored in %SystemRoot%\system32\oem and %SystemRoot%\System32\spp\tokens, replacing matching ones in the store. It does not replace your product key, which is why it is safe to try first.
The system clock is wrong
You have this one if The date or time is out by hours or more, often after a dead CMOS battery, a dual-boot with a different time convention, or a virtual machine restored from an old snapshot.
- Set the time zone correctly, then enable automatic time.
- Force a sync from an elevated prompt:
w32tm /resync. There is no /force parameter – the documented ones are /computer, /nowait, /rediscover and /soft. - If that fails, confirm the Windows Time service is running with
sc query w32time, and on a domain member check the source withw32tm /query /source. - Retry activation once the clock is right.
Microsoft documents 0x80072F8F as the device’s date and time being incorrect, or the device being unable to connect. If you see that code alongside these, the clock is where to start.
An inspecting proxy is rewriting the activation traffic
You have this one if Machines fail on the corporate network and succeed on a mobile hotspot, or a whole site fails at once with no other symptom.
- Ask the network team to exempt Microsoft licensing and activation endpoints from TLS interception, not merely to permit them.
- Include
licensing.mp.microsoft.com, which Microsoft documents as the endpoint used for online activation and some app licensing. - Check the proxy the system account uses rather than the browser’s:
netsh winhttp show proxy. - Retest from an unfiltered connection to prove the diagnosis before requesting a firewall change.
The licensing store or the component store is damaged
You have this one if Several licensing operations fail, the licensing service logs errors as soon as it starts, and slmgr /rilc itself does not complete.
- Repair the component store first:
DISM /Online /Cleanup-Image /RestoreHealth. - Then
sfc /scannow, which uses that store to repair system files, and reboot. - Repeat
slmgr /rilc, since it reinstalls from files DISM may have just repaired. - Reinstall the key with
slmgr /ipkand activate.
Do not go looking for the store on disk to rename or delete files in it. Microsoft documents no such procedure, and the location has changed between Windows versions.
Full reference
Narrowing it down
| Symptom | Most likely area |
|---|---|
| Failure began right after a feature update or in-place upgrade | Licence description files left stale by the upgrade |
| The machine is a restored image or a clone | A licensing store carried over from another installation |
| Only machines behind the corporate proxy fail | TLS inspection altering the activation request |
| The clock is visibly wrong, or the time zone changed recently | The secure connection, and the signed data inside it |
| Several products fail at once, including Store apps | The licensing store or servicing, rather than one product |
| One machine fails and identical ones do not | That machine’s store; start with slmgr /rilc |
The repair sequence, and why that order
slmgr /rilcfirst. It is the narrowest operation, it reinstalls only the descriptive licences, and Microsoft documents that it leaves the product key alone.- Restart the Software Protection service so the reinstalled files are picked up.
DISM /Online /Cleanup-Image /RestoreHealthnext, because it repairs the component store that/rilcreinstalls from.sfc /scannowafter DISM rather than before, since it repairs system files using that store.- Reboot, run
slmgr /rilconce more, then install the key and activate.
Rebuilding the licensing store by hand is not a documented operation, and the path people quote for it comes from Windows 7. Use the commands above. If the store is genuinely beyond repair, an in-place repair install of Windows is the supported route, and it deserves a backup and a maintenance window first.
Commands and what they actually touch
| Command | What it does | Touches your key? |
|---|---|---|
slmgr /rilc |
Reinstalls the licences held in the system folders | No |
slmgr /ipk <key> |
Installs a product key, replacing the current one | Yes |
slmgr /upk |
Uninstalls the key. Unlicensed after restart | Yes |
DISM /Online /Cleanup-Image /RestoreHealth |
Repairs the component store | No |
sfc /scannow |
Repairs system files from the component store | No |
w32tm /resync |
Resynchronises the clock | No |
netsh winhttp show proxy |
Shows the proxy the system services use | No |
When several products fail at once
The same licensing store backs Store app licences and, on some installations, other Microsoft products. If Windows activation, Store apps and Office all started failing on the same day, treat it as a store problem rather than chasing each product separately. Repair once, then re-check all three. It is also the strongest signal that the cause is servicing damage rather than anything to do with a particular licence.
What to check when the repairs change nothing
- Read the Application log filtered by the Security-SPP source, and note whether the service logs errors at start-up or only when a request is made. Those are different problems.
- Confirm the machine is running the edition you think it is.
winvernames the edition;slmgr /dlvnames the product the licensing service thinks it has. - Confirm the installation is not an evaluation or preview build, which carry no licence for the full product.
- Test from an unfiltered connection before asking for a firewall change, so you are asking for something you have proved.
- If the machine is a restored image from another computer, treat a clean build as the realistic answer rather than repairing a store that was never this machine’s.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x803FA073 |
Reported when an activation request cannot be resolved against the product data submitted with it. Microsoft publishes no meaning; repair the licence store rather than replacing the key | not published by the vendor |
0x803FA074 |
The same class of rejection reported through the licensing front end. No published meaning | not published by the vendor |
0x803FA076 |
Seen where the product data held locally is incomplete or inconsistent. No published meaning | not published by the vendor |
0xC004E025 |
Raised by the licensing service about an add-on or supplemental licence referenced by the request. No published meaning | not published by the vendor |
0xC004E006 |
Seen when a licence fails validation locally. No published meaning | not published by the vendor |
0xC004E008 |
Raised when the licensing state cannot be read or verified. No published meaning | not published by the vendor |
Confirm the fix worked
slmgr /dlvreports Licence Status: Licensed with no grace countdown.- The edition shown by
slmgr /dlimatches the edition you actually installed. - The Application log, filtered by the Security-SPP source, shows routine entries rather than repeated failures.
- Reboot and re-check, since a store repair that only half worked usually reverts on restart.
Questions people ask about this
Should I buy a replacement key?
Not for these codes. They describe the data around the key rather than the key itself, and a new key dropped into the same store fails identically. Repair the store first. If activation then fails with an entitlement error instead, that is when a licence question genuinely arises.
Is slmgr /rilc risky?
No. Microsoft documents it as reinstalling the licences stored in the system folders and replacing matching ones in the store. It does not uninstall your product key or deactivate the machine, which is why it is the first thing to try in this family.
Why does it work at home and fail in the office?
Usually TLS inspection. Many corporate proxies terminate and re-sign HTTPS, which changes the request arriving at Microsoft. Allowing the traffic is not enough; the endpoints have to be excluded from inspection. Microsoft publishes licensing.mp.microsoft.com as the endpoint used for online activation.
Should I delete the token store to rebuild it?
No. Microsoft documents no procedure for editing the licensing store by hand, and the path that gets quoted for it comes from the Windows 7 era. Use slmgr /rilc, DISM and sfc; if those cannot fix it, an in-place repair install is the supported route.
Does this affect Office and Store apps too?
It can. The same licensing store backs Store app licences and, on some installations, other Microsoft products. If several started failing on the same day, treat it as one store problem rather than several product problems.
