0xC004F064: Non-Genuine Grace Period Expired and Windows Now Nags

Fix it now

Microsoft publishes 0xC004F064 as “The Software Protection Service reported that the non-genuine grace period expired”, and lists the resolution as contacting the Microsoft Licensing Activation Centers. Before you do that, find out whether the machine already holds an entitlement it is not using, because that is the case where this costs nothing.

slmgr /dlv
slmgr /dli
slmgr /xpr

1. Read the licence description and status. slmgr /dli names the channel; slmgr /dlv gives the detail; slmgr /xpr tells you whether anything is still counting down.
2. Check whether the machine has a licence it is not using. A preinstalled computer that was rebuilt often has an entitlement in firmware, and a machine previously activated with a Microsoft account may have a digital licence waiting on it.
3. Run the activation troubleshooter. It appears in Settings under System while Windows is unactivated and disappears once activation succeeds, and you must be signed in as an administrator to use it.
4. If you hold a valid key for the edition that is installed, install it over the top with slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX, then activate with slmgr /ato.
5. Confirm with slmgr /dlv that the licence status reads Licensed.

Install the key over the existing one. Microsoft’s licensing repair guidance says not to use slmgr /upk, and /ipk validates the key against the installed edition and replaces whatever is there.

If that fixed it you can stop here. If not, the next section explains what this code is reporting and why only one of the five codes here has a published meaning.

Why it happens

0xC004F064 is a countdown finishing. Microsoft’s published text is that the Software Protection Service reported that the non-genuine grace period expired, and the resolution it lists is to contact the Microsoft Licensing Activation Centers. Both halves of that matter. The state is not a fault to be repaired, and Microsoft’s own answer is a licensing conversation rather than a command sequence.

It is worth being careful about what the state actually costs you, because writing on this subject exaggerates in both directions. Microsoft does not publish a feature-by-feature account of what changes when the non-genuine grace period ends, so this article will not give you one. What you can rely on is the Activation page in Settings, which reports the state directly, and slmgr /dlv, which gives you the licence status and channel underneath it.

Only 0xC004F064 in this record has a published meaning. 0xC004F067, 0xC004F200 and 0xC004F066 have none that could be found on learn.microsoft.com or support.microsoft.com, and the readings earlier versions of this article gave them were unsourced. 0x4004F068 is a different case again: no page publishes it, but the structure of the value tells you something real. In an HRESULT the top bit is the severity bit – set means failure, clear means success – so a value beginning 0x4 is a status result rather than an error, while one beginning 0xC is a failure. That is a documented property of the value format, not a licensing convention.

So the practical division is this. If you are reading a log and the value begins 0xC004, something failed and the rest of the value identifies what. If it begins 0x4004, the service is reporting state. Microsoft separately publishes 0xC004F065 as the application running within the valid non-genuine period, with the resolution being to obtain and install a genuine product key before the grace period ends – which is the warning that precedes the code this article is about.

Full reference

Which of these codes carry a published meaning

Reading a licensing value at a glance

An HRESULT carries its severity in the top bit: set indicates a failure result, clear indicates a success result. In hexadecimal that puts every failure in the range 0x80000000 to 0xFFFFFFFF and every success or status result below it. So a licensing value beginning 0xC004 is a failure and one beginning 0x4004 is the service reporting state. That single distinction saves a great deal of wasted work, because a 0x4004 value in a log is not a complaint.

Before you buy: the two free checks

1. A firmware entitlement. Machines that shipped with Windows preinstalled generally carry a key in firmware that survives a rebuild. If one exists, install it with slmgr /ipk and activate.
2. A digital licence on an account. A machine previously activated while signed in with a Microsoft account may have an entitlement attached to that account. Sign in with it and run the activation troubleshooter, which is available in Settings under System while Windows is unactivated and requires administrator rights.

Between them these two cover a large share of the machines that arrive at this code, and neither costs anything. Do them before you conclude that a licence is due, and do them before you reinstall, because a reinstall does not create an entitlement that was not there.

What not to do

Do not reach for tools that promise to reset the timer. slmgr /rearm is documented as resetting the activation timers and as being called by sysprep /generalize; it is a deployment switch, and Microsoft publishes no route that restores an expired non-genuine grace period. Anything claiming to reset the state permanently is an activation hack, and it leaves you with a tampered licensing state that is considerably harder to clear than the state you started with.

slmgr /rearm does nothing at all if SkipRearm is set to 1 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform, which is worth knowing if you are wondering why a command appeared to succeed and changed nothing.

How to know when the licence really is the answer

• No firmware key, no digital licence on any account you control, and no volume agreement covering the device.
• A channel in slmgr /dli that does not match anything you bought – a volume description on a standalone consumer machine being the clearest example.
• A machine that was activated by a downloaded utility rather than by a purchase.
• A repair sequence that completes cleanly and leaves the state exactly where it was.

Every code this article covers

Confirm the fix worked

1. slmgr /dlv reports a licence status of Licensed with the channel and partial key you expect.
2. slmgr /xpr no longer reports a countdown for a perpetual licence.
3. Settings, System, Activation reports the machine as activated, and the Troubleshoot option is no longer offered.
4. The Application log under Security-SPP stops accumulating non-genuine status entries.
5. Reboot and re-check, since a state that reverts on restart is telling you something a single successful command did not.

Questions people ask about this