Fix it now
Microsoft publishes 0xC004C003 as the activation server determining that the specified product key is blocked, and its documented resolution is to contact the Microsoft Licensing Activation Centers for a new key. The decision was taken at the server. Nothing on this PC is being questioned, so nothing on this PC will change it.
slmgr /dli
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato
- Check the last five characters
slmgr /dlireports against the key you meant to use. One wrong character puts you on a different key range entirely. - Retype the key once, carefully, and retry activation. Once is a genuine check for a transcription error; twice tells you nothing new.
- If the same code returns, contact the Microsoft Licensing Activation Centers. That is Microsoft’s documented route for this code, and it is the only one that can change anything.
- If the key came from an employer or a volume agreement, ask whoever manages that agreement before doing anything else.
- If you are seeing 0x803FA067 instead, do not assume a block. Microsoft lists that code with invalid keys and busy activation servers, so retry and check the key first.
Blocked is a decision about the key, not about the installation. Reinstalling Windows, changing hardware or running troubleshooters presents the same key from the same account and gets the same answer.
If a valid key activates, you are done. If the block is confirmed, the next section explains what that means and what it does not.
Why it happens
Activation is a conversation between your machine and Microsoft’s activation service, and this code is the service’s answer rather than your machine’s. Microsoft’s activation error list publishes 0xC004C003 as “The activation server determined the specified product key is blocked”, with a resolution of contacting the Microsoft Licensing Activation Centers to obtain a new key and then reinstalling and activating Windows. That is the whole of what is documented, and it is enough to rule out every local remedy at once.
Microsoft’s consumer activation help describes the same code more loosely, as a product key that is not valid, and offers the activation troubleshooter and a different key. Both readings come from Microsoft, and the difference matters mainly for what you do next: the volume licensing route is the one that can distinguish a genuinely blocked key from a mistyped one.
0x803FA067 is where a lot of advice goes wrong, and it is worth being precise. Microsoft’s activation help lists it – as 0x803FA067L – alongside 0xC004C001, 0xC004C004, 0xC004F004, 0xC004F005 and 0xC004F050, under keys that are not valid, activation servers that are busy, or an upgrade that did not activate. It is not listed with the blocked-key entry. So a machine reporting 0x803FA067 is not necessarily reporting a block, and the reasonable first move there is to retry and check the key rather than to conclude the key is finished.
0xC004C803, 0xC004C04F and 0x803FA0C8 turn up in the same discussions. Microsoft publishes no meaning for any of them, so read them as refusals from the activation service and diagnose from the channel and the source of the key rather than from the digits.
The key really is blocked
You have this one if The same code returns after one careful retype, and the key was bought somewhere you cannot get an invoice from.
- Contact the Microsoft Licensing Activation Centers, which is the documented route for this code.
- Have ready where the key came from, when it stopped working, and any agreement or order reference.
- If the key came from a marketplace seller, ask for a refund rather than a replacement; a replacement from the same batch behaves the same way.
- Install a key you can trace to an invoice, then activate.
A blocked key often worked at first. Activation happened, the machine ran for weeks, and the block was applied afterwards – which is why nothing you did on the day it stopped explains anything.
The key belongs to an organisation, not to you
You have this one if The machine was activated with a corporate key at some point, and you have since left the organisation or bought the hardware second-hand.
- Ask the organisation whether the machine is entitled to remain on their agreement. Sometimes it is, and one call resolves it.
- If it is not, remove the key:
slmgr /upk, thenslmgr /cpky. - Install a licence of your own and activate with
slmgr /ato.
slmgr /cpky removes the key from the registry to prevent it being read off the machine. Microsoft describes it as best practice for retail deployments.
You are not on the key you think you are
You have this one if The code appeared straight after typing a key by hand, with no earlier period of successful activation.
- Compare the last five characters from
slmgr /dliagainst the key you meant to use. - Retype carefully, watching for characters that read alike in print.
- Retry
slmgr /atobefore concluding anything about a block.
It is 0x803FA067 and not a block at all
You have this one if The Settings app reports 0x803FA067 and slmgr has not been run, or reports something different.
- Retry activation after a few minutes. Microsoft groups this code with the activation servers being busy.
- Check the key itself, since the same group covers keys that are not valid.
- Run the activation troubleshooter from Start, Settings, System, Activation.
- Only if a documented block code appears should you treat the key as finished.
Full reference
Where the key came from, and what to expect
| Source of the key | Realistic outlook |
|---|---|
| A marketplace listing far below local retail | The seller cannot reinstate a key the activation service has refused |
| An employer’s volume key on a personal machine | Not yours to use, and it can be withdrawn centrally at any time |
| A key from an agreement that has since ended | Keys tied to a lapsed agreement stop activating new machines |
| A subscription or evaluation key on a production PC | Outside the terms it was issued under |
| A certificate of authenticity sticker of unknown provenance | May already be claimed on another machine |
| A key with an invoice and a named channel | Worth taking to the Licensing Activation Centers, because there is something to check |
Commands, and what they do to the machine
| Command | Effect |
|---|---|
slmgr /dli |
Shows which key is installed, including the last five characters, and its channel |
slmgr /ipk <key> |
Installs a key, validating it against the installed operating system |
slmgr /ato |
Attempts activation now |
slmgr /upk |
Uninstalls the product key. The system is Unlicensed after restart unless a new key is installed |
slmgr /cpky |
Removes the key from the registry so it cannot be read back off the machine |
slmgr /upk and slmgr /cpky leave the machine unlicensed. Run them only once the replacement key is in front of you, and expect a desktop watermark in the interval.
Codes worth telling apart before you give up on a key
| Code | What Microsoft publishes |
|---|---|
0xC004C003 |
The activation server determined the specified product key is blocked |
0xC004C001 |
The activation server determined the specified product key is invalid |
0xC004C008 |
The key could not be used: already used on another device, or a host key past its limit of 10 activations on 6 computers |
0xC004C020 |
The Multiple Activation Key has exceeded its limit |
0x803FA067 |
Listed with invalid keys, busy activation servers and failed free upgrades |
0xC004F050 |
The product key is invalid. Check for typos, and for hyphens turned into dashes by a paste |
The practical value of that table is that only one row is permanent. An invalid key may be a typo. A busy server clears on its own. A MAK over its limit has a documented route to more activations. A blocked key is the one where the answer is a different key, and it is worth confirming you are actually looking at that row before you accept it.
Things that do not work, and why people keep trying them
- Reinstalling Windows. The refusal is about the key, and a reinstall presents the same key.
- Registry edits under the licensing keys. They change what the local machine believes, not what the activation service has recorded.
- The activation troubleshooter, where the key is genuinely blocked. It is worth running once, because it is free and it resolves neighbouring problems, but it does not overturn a server-side decision.
- Buying a replacement from the same seller. Keys come in batches, and a batch that has been blocked tends to have been blocked together.
- Third-party activation tools. They work by not asking the activation service, which leaves the machine unlicensed and, in a business, in a worse position than it started.
What blocked does not mean
It does not mean your machine is damaged, that files are at risk, or that Windows will stop working. Windows moves into a notification state: a desktop watermark, personalisation settings locked, periodic prompts. Data, applications, domain membership and network access are untouched, and everything returns to normal when a valid key is activated.
It also does not mean the key was necessarily counterfeit when it was issued. Keys are blocked for how they were distributed as often as for what they are, which is why a key can be genuine, unused, and still refused. Genuine and usable are separate claims, and this code speaks only to the second.
When a licence is the actual fix
Where the block is confirmed and the Licensing Activation Centers cannot issue a replacement under an agreement you hold, a legitimate key is the only fix. Arco is a Microsoft licence reseller, and what you get with a Windows 11 Pro retail key bought properly is not a different string of characters but a traceable one, with an invoice behind it and a channel it can be checked against. That matters more than it sounds: it is what makes a future reactivation after a hardware change a support conversation rather than a dead end. Before ordering, send the output of slmgr /dlv so the edition can be confirmed – and if the code you are actually seeing is 0x803FA067, we will tell you to retry rather than sell you anything.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004C003 |
The activation server determined the specified product key is blocked. Microsoft’s documented resolution is to contact the Licensing Activation Centers for a new key | Microsoft Learn |
0x803FA067 |
Microsoft lists this with invalid product keys, busy activation servers and failed free upgrades – not with the blocked-key entry. Retry and check the key before concluding a block | Microsoft Support |
0xC004C803 |
An activation-service refusal seen alongside these. No published meaning | not published by the vendor |
0xC004C04F |
Another refusal from the same part of the service. No published meaning | not published by the vendor |
0x803FA0C8 |
Reported by the Settings activation client in similar circumstances. No published meaning, and no source pairs it with a specific 0xC004C code | not published by the vendor |
Confirm the fix worked
slmgr /dlireports Licence Status: Licensed on the new key.- Start, Settings, System, Activation shows the machine activated with no remediation link.
- The last five characters in
slmgr /dliare those of the key you intended to install. - Reboot and re-check, so you know the state is permanent rather than a grace period.
- Leave the machine a week and check again, since a block takes effect at validation rather than instantly.
Questions people ask about this
Can a blocked key be unblocked?
Not by you. Microsoft’s documented route is to contact the Licensing Activation Centers, which can issue a new key where an agreement supports it. Any service claiming it can unblock a key for a fee is selling you something else.
Will I lose files or applications?
No. Windows moves into a notification state, which means a desktop watermark, locked personalisation and periodic prompts. Data, applications and network access are untouched, and everything returns to normal once a valid key activates.
Why did it work for months and then stop?
Because the block was applied after you activated. It takes effect at the next validation rather than instantly, which is why nothing you did on the day it failed explains anything.
I am seeing 0x803FA067. Is my key blocked?
Not on the strength of that code. Microsoft lists it with keys that are not valid, activation servers that are busy, and free upgrades that did not activate. Retry after a few minutes, check the key you actually installed, and run the troubleshooter before drawing any conclusion.
How do I avoid buying another key that fails?
Buy from a seller who issues an invoice, states the licence type plainly and can say which channel the key comes from. A price far below the market for that edition is the reliable warning sign, because the margin has to come from somewhere.
