0xC004F051: Windows Reports the Key as Blocked, Not Merely Wrong

Fix it now

Microsoft documents 0xC004F051 as the Software Protection Service reporting the product key is blocked, and states the block is held on the activation server. Nothing on your computer holds it, so nothing on your computer clears it. The documented remedy is a different key.

cscript //nologo %windir%\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript //nologo %windir%\system32\slmgr.vbs /ato
cscript //nologo %windir%\system32\slmgr.vbs /dli

1. Confirm which code you actually have. A key that will not install at all is a different problem from one that installs and is then refused.
2. Prove the machine is healthy by installing a different key you know is good. If that one activates, only the original key is affected.
3. Gather the purchase evidence for the blocked key: invoice, order reference and whatever licence statement came with it.
4. If the key came from a volume agreement, speak to whoever administers that agreement before doing anything else.

Do not clear the old key with slmgr /upk until the replacement is in your hand. Microsoft documents that the system enters the Unlicensed state after the next restart, so a machine sitting in a grace period loses that state for nothing.

If a replacement key activates, you can stop here. If you want to establish why the first one was blocked, or you think the block is a mistake, the next section covers both.

Why it happens

Microsoft publishes two codes for a blocked key and they sit on opposite sides of the exchange. 0xC004F051 is the local Software Protection Service reporting that the product key is blocked, and the documented cause is that the key is blocked by Microsoft on the activation server. 0xC004C003 is the activation server saying the same thing directly. The documented remedy for both is identical and short: obtain a new key, install it, activate.

That is the whole reason the usual repair sequence is wasted effort here. Rebuilding the token store, running the troubleshooter, reinstalling Windows, resetting the licensing service – none of them touch a flag recorded against a key in Microsoft’s records. If the key installs without error and only activation fails, everything local is already working correctly and you are looking at a decision that was made elsewhere.

The companion codes in this record are weaker evidence than v1 guidance usually suggests, and it is worth being straight about that. 0xC004C00E and 0xC004C00F appear on Microsoft’s consumer error list, but in the general group meaning the key cannot be used to activate Windows, the activation servers were busy, or a free upgrade was never activated after a reinstall. They are not published as blocked-key codes. 0xC004C002 and 0x803FA066 are not published at all.

Full reference

Telling a block apart from the things it resembles

The codes Microsoft actually publishes for this

That last row matters more than it looks. A MAK that has run out of activations is not blocked, it is spent, and the documented route is to contact the Microsoft licensing activation centre for more activations rather than to buy a replacement key. If your code is 0xC004C020 rather than 0xC004F051, you are reading the wrong article and you may not need to spend anything.

Removing a blocked key safely

The commands below remove the current product key. Microsoft documents that the system enters the Unlicensed state after the next restart. Note the key you are removing, and have the replacement ready before you start.

cscript //nologo %windir%\system32\slmgr.vbs /upk
cscript //nologo %windir%\system32\slmgr.vbs /cpky
cscript //nologo %windir%\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript //nologo %windir%\system32\slmgr.vbs /ato
cscript //nologo %windir%\system32\slmgr.vbs /dli

/cpky is worth including rather than skipping. Microsoft documents it as removing the product key from the registry so that it cannot be recovered from there, which is standard practice after a retail key has been applied. It does not deactivate anything.

What happens to the machine while it is unlicensed

• Windows keeps booting, applications keep running and security updates keep arriving. The block is a licensing state, not a kill switch.
• Personalisation settings in Settings are locked and a watermark appears on the desktop.
• Nothing about your files is at risk from the block itself. If an activation tool put the key there rather than you, the tool is the thing to worry about.
• There is no time limit that makes this worse. You can take a week to sort the licence out.

If you think the block is a mistake

Only whoever holds the entitlement can raise it, and realistically only where you bought directly from Microsoft or from a reseller who can escalate on your behalf with proof of purchase. Keep the invoice, the order reference and the exact code and date. A key bought from a marketplace listing with no paperwork leaves nobody positioned to make that case, which is the practical difference between the two ways of buying.

Every code this article covers

Confirm the fix worked

1. slmgr /dli shows the last five characters of the replacement key, not the blocked one.
2. Licence Status reads Licensed.
3. slmgr /xpr reports permanent activation rather than a remaining period.
4. Settings > System > Activation still reports Windows as active after a reboot.

Questions people ask about this