Office 0xC004C003: Microsoft has blocked this product key permanently

Fix it now

Microsoft publishes 0xC004C003 as “the activation server determined the specified product key is blocked”, and its documented remedy is to obtain a new key from the Microsoft Licensing Activation Centers. The decision sits with the key at Microsoft’s end, so nothing you change on the machine will move it.

cd "C:\Program Files\Microsoft Office\root\Office16"
cscript ospp.vbs /dstatus
cscript ospp.vbs /dhistoryacterr
cscript ospp.vbs /unpkey:XXXXX

1. Record the licence description from /dstatus before removing anything. It names the channel the key came from, and that is the useful evidence in a refund conversation.
2. /dhistoryacterr prints the MAK and retail activation failure history, which distinguishes a block from a run of network failures.
3. Remove the key so Office stops attempting an activation that cannot succeed.
4. Go back to whoever sold it and open a refund request, keeping the order reference and the listing.
5. Install a key you can account for with /inpkey: and activate with /act.

If the key came from your own volume agreement rather than a marketplace, do not remove it yet. That is the one case worth escalating, and the section below says with what.

If a replacement key activates, you are done. If you are trying to work out whether yours is one of the escalatable cases, the next section separates them.

Why it happens

This is a server-side decision about a key, not a fault on a machine. Microsoft’s published text is short: the activation server determined the specified product key is blocked. The published remedy is equally short, and it is the part that settles most of the argument: contact the Microsoft Licensing Activation Centers to obtain a new key. Nowhere does Microsoft describe a route to unblock the old one.

Every key belongs to a channel: retail, OEM, volume, academic, not-for-resale, or a developer subscription. Each channel carries different terms about who may use the key and whether it can be transferred, and a key used outside those terms can be blocked at the activation service. From that point the key still exists, and it activates nothing.

The patterns behind blocked keys are consistent enough to be worth naming, with the caveat that these are the commercial patterns rather than causes Microsoft publishes. Keys stripped from developer or evaluation subscriptions and sold as retail. Volume agreement keys broken up and sold as single licences. Keys bought in bulk with payment that later reverses. Keys sourced in one region and sold into another. The common factor is a seller who was not entitled to transfer what they sold.

Of the three codes here, two are published and one is not. 0xC004B100, “the activation server determined that the computer could not be activated”, is a different refusal from the same server. 0xC004C060 has no published description anywhere, so treat any confident gloss for it with suspicion and read your own machine’s text with cscript ospp.vbs /ddescr:0xC004C060.

Full reference

What cannot move a block, and why people keep trying

Telling a block apart from a bad week on the network

cscript ospp.vbs /dhistoryacterr displays the failure history for MAK and retail activation, which is the fastest way to see whether you are looking at one server decision repeated or a series of different failures. A block returns the same refusal every time from any network. A connectivity problem returns timeouts, and those have their own codes and their own article.

0xC004B100, “the activation server determined that the computer could not be activated”, is a different refusal and does not mean the key is blocked. If that is the code you have, you are in the wrong article.

Where second-hand licences are and are not legitimate

European law does recognise a genuine second-hand software market. In UsedSoft v Oracle (Case C-128/11) the Court of Justice of the European Union held that where a perpetual licence for a downloaded program was first sold inside the European Economic Area with the rightholder’s consent, the distribution right in that copy is exhausted and it may be resold. The conditions are the part sellers leave out: the original holder must make their own copy unusable, and a volume licence cannot be divided into single seats and sold off.

That is why a reputable used-software market exists in Europe and why a properly documented transferred licence can be entirely lawful. It is also why most cheap marketplace keys are not covered by it. If the seller cannot show what the original licence was, who held it, and that it has been made unusable at source, you are not buying an exhausted licence. This is a court decision rather than vendor documentation, and it describes what is lawful rather than what the activation server will accept.

Recovering the money

1. Open the marketplace dispute before anything else. Most have a policy specifically for keys that do not activate, and most have a time limit.
2. Keep the listing, the order reference and the licence description from /dstatus. A screenshot of the refusal is worth more than a description of it.
3. If the marketplace declines, ask your payment provider about a chargeback.
4. Treat silence from the seller as the answer and stop waiting.

While you are unlicensed

Microsoft publishes that an unlicensed installation shows Unlicensed Product in the title bar and that most features are disabled. Your files are not affected and full function returns as soon as a valid licence activates, so this is a commercial problem with a deadline rather than a data emergency. Sort the licence out rather than reinstalling anything.

Every code this article covers

Confirm the fix worked

1. cscript ospp.vbs /dstatus no longer lists the blocked key.
2. The replacement licence is listed with a licensed status.
3. An Office application opens with no Unlicensed Product wording in the title bar.
4. cscript ospp.vbs /dhistoryacterr shows no new failures after the replacement key was installed.
5. You have kept a record of where the new licence came from, since buying again from the same source is the commonest way this repeats.

Questions people ask about this