About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Error 0xC004C003 is a refusal from Microsoft's activation server: the key was read, sent for activation, and the server said it is blocked. On Microsoft's volume activation page the code is listed for the Multiple Activation Key (MAK) type, with the cause "You can encounter this issue if the MAK is blocked on the activation server." and the solution "Contact the Microsoft Licensing Activation Centers to obtain a new MAK. After you obtain the new MAK, try installing and activating Windows again."
Retyping the same key is not Microsoft's documented fix; its solution is a new key. Confirm which key is installed, check where it came from, and replace it with a key that is licensed for the computer. Do not install keys one after another, because a MAK has a limited number of activations.
What the error means
Microsoft's "Troubleshoot Windows activation error codes" page lists 0xC004C003 with the message "The activation server determined the specified product key is blocked." and one activation type, MAK. Two similar codes are worth telling apart:
- 0xC004C001, "The activation server determined the specified product key is invalid." Microsoft's cause is that "the MAK you enter isn't valid", and it says you can try re-entering the MAK, then contact the Microsoft Licensing Activation Centers if that does not work.
- 0xC004F051, "The Software Protection Service reported that the product key is blocked." It is listed for MAK and KMS, and Microsoft's cause is "This error message appears when Microsoft blocks the product key", with the solution "get a new MAK or KMS key, install it on the system, then try activating again."
0xC004C003 is the one where the activation server, not the local Software Protection Service, reports the block. For a key that has simply been mistyped, see 0xC004F050 instead.
Microsoft's "Get help with Windows activation errors" page for Windows 10 and Windows 11 gives a different reading of the same code for individual devices: "You may see this error because the Windows 11 product key you entered isn’t valid. Product keys are unique—assigned to a specific user to install on a single device. If a key was used (or attempted to be used) on multiple devices, it’s marked as not valid." It tells the reader to provide a different Windows key that is unique to the device, to contact the reseller if the device was bought from one, and to contact the device manufacturer if Windows came preinstalled and the error appeared on first start. It also mentions the Windows Activation Troubleshooter (Settings, System, Activation, Troubleshoot on Windows 11) and, for a device repaired at an independent repair facility, checking whether the repair requires a new licence. Separately, the page says that after a major hardware change such as a motherboard replacement, the troubleshooter on the activation settings page may ask you to go through the reactivation process. That page is written for Windows 10 and Windows 11 devices, and its 0xC004C003 entry does not mention a MAK or a volume key.
Microsoft's volume page tells you what to do for a MAK, and the client page tells you what to do for a key on a single device. Which one applies depends on the kind of key installed, which your licence records show.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| The MAK is blocked on the activation server | 0xC004C003 on every computer using that MAK | Microsoft's page says only that the MAK is blocked on the activation server; a way to test, not Microsoft's step, is to see whether another computer using the same MAK gets the same error |
| The key was used on multiple devices (client page) | 0xC004C003 on a device with a key meant for one device | Licence records show the key assigned to another device |
| The key is not what was bought or issued | Key does not match the licence record | Compare the key against the purchase or issue record |
| Reseller or manufacturer key problem | Error on first start of a new device | Client page: contact the reseller or manufacturer |
Prove the cause before changing anything
All of these only read. Run them in a command prompt on the affected computer. Microsoft's Slmgr.vbs page says /dli, /dlv and /xpr do not need elevated privileges.
Display licence information for the installed edition:
slmgr.vbs /dli
Display detailed licence information:
slmgr.vbs /dlv
Display the activation expiry date:
slmgr.vbs /xpr
Then check your licence records: which key was installed on this computer, who issued it, and whether other computers use the same MAK. If another computer using the same MAK activated earlier and fails now, that is a check of your own, not a Microsoft step, and it may point to a block placed on the key. If the key was meant for one device and is on several, the client page's explanation applies.
Example (illustrative): at contoso.com.au, app01 is a new Windows Server virtual machine built from a template whose MAK is also used on fs01 and rds01. Activation on app01 ends with "The activation server determined the specified product key is blocked." fs01 and rds01 still show as activated. The licence record shows the MAK was issued under a volume agreement for the three servers. Microsoft's solution for 0xC004C003 is to contact the Microsoft Licensing Activation Centers for a new MAK.
Fix
A blocked key cannot be fixed on the computer. The change is a replacement key, obtained from the source Microsoft names, installed and activated.
- For a MAK, contact the Microsoft Licensing Activation Centers and obtain a new MAK. Microsoft's page gives no contact details, so use the route in your licence agreement or on Microsoft's current licensing pages.
- For a key bought for one device, contact the reseller (or the device manufacturer if Windows came preinstalled), as Microsoft's client page says.
- When you hold the new key, install it and activate as below.
Before you change it, make sure you have the output of slmgr.vbs /dlv above and the record of the key that is installed now. Microsoft's page does not describe a command that shows the full installed key.
Risk: the next command replaces the product key installed on this computer. Microsoft's page says "If a key is already installed, it's silently replaced." Run it in an elevated Command Prompt, on the right computer, with the new key.
slmgr.vbs /ipk <5x5 key>
Microsoft says the system "should be restarted or the Software Protection Service should be restarted" after it.
To undo it: run the same command with the key you recorded earlier. That is the blocked key, so putting it back restores the error; do it only if the replacement key turns out to be wrong for this computer.
slmgr.vbs /ipk <previous key>
Microsoft says the system should be restarted or the Software Protection Service restarted after the key is installed.
Disruptive step: restarting the computer, or restarting the Software Protection Service, interrupts the services and sessions on this server for the time it takes. Choose a quiet period. Microsoft's pages give no steps for restarting the Software Protection Service on its own, so restart the computer. Nothing needs undoing; the computer comes back as it was.
Restart the computer now, then continue.
Before you activate, keep the earlier /dlv output: it is the record of the state before activation.
Risk: the next command asks Windows to activate with the installed key. A MAK can be activated only a limited number of times, and Microsoft's page says "By design, you can only activate a MAK a limited number of times." Run it once, with the new key, not as a retry loop.
slmgr.vbs /ato
There is no way back from an activation counted against a MAK with the commands on Microsoft's pages.
Confirm the fix
- Run
slmgr.vbs /dliand check that the licence information shows the edition as licensed. - Run
slmgr.vbs /xpr. Microsoft says it is primarily useful for KMS clients, because MAK and retail activation is perpetual. - Compare the result with another server activated from the same agreement.
- If a different code appears, look it up in Microsoft's table by the code; do not repeat the replacement for a different fault.
What to watch afterwards
- The activation count on the new MAK. Microsoft lists 0xC004C020, "The activation server reported that the Multiple Activation Key has exceeded its limit", and gives the solution "Request more activations to increase limit. If you require more activations, contact the Microsoft Licensing Activation Centers."
- Every other computer using the old MAK. Microsoft's pages say nothing about other computers that use a MAK that has been blocked, so check each one's activation status with
slmgr.vbs /dli. - Where the key sits in your records and who can see it. The new key is typed on a command line, and Microsoft's pages say nothing about hiding it from command history.
- Servers built from the same template. Check which key each one holds with
slmgr.vbs /dlibefore you assume they are covered by the replacement.
Read next
Related articles you may want next.
- TroubleshootingWindows activation error 0xC004F050: "The Software Protection Service reported that the product key is invalid"Windows activation 0xC004F050: the product key is invalid. Check the typed key, the Windows version it belongs to and pasted dashes before replacing it.Read article
- TroubleshootingWindows activation fails with 0xC004F074: no Key Management Service could be contactedError 0xC004F074 means a volume-licensed Windows computer could not activate against its KMS host. Check the host's service, TCP port 1688, the _VLMCS DNS record, the clock and whether the host can activate this Windows version.Read article
- HostingLicence and activation services as day-to-day availability dependenciesHow KMS, volume activation and ISV licence endpoints affect hosted application uptime during normal operations—not only after a disaster restore.Read article
Risks and limits
These commands have not been run or lab-tested.
Microsoft's pages say what the error is and who to contact, and not why a key becomes blocked. The client page's explanation (a key used on more than one device) is written for individual Windows 10 and Windows 11 devices, and the volume page does not repeat it for a MAK. For licence terms, activation limits and entitlements, check the current Microsoft licensing pages and your agreement. Microsoft's pages give no way to unblock a key from the computer.
Sources
- Troubleshoot Windows activation error codes — Microsoft Learn, page dated 2026-02-12, accessed 22 November 2026
- Get help with Windows activation errors — Microsoft Support, date not shown, accessed 22 November 2026
- Slmgr.vbs options for obtaining volume activation information — Microsoft Learn, page dated 2025-07-07, accessed 22 November 2026
This article was originally published on .