Fix it now
Microsoft publishes 0xC004C020 as the activation server reporting that the Multiple Activation Key has exceeded its limit, and its documented remedy is to request more activations from the Microsoft Licensing Activation Centers. Nothing on the client is broken and no amount of retrying changes the answer.
cd "C:\Program Files\Microsoft Office\root\Office16"
cscript ospp.vbs /dstatus
cscript ospp.vbs /dhistoryacterr
- Note the last five characters of the installed key from
/dstatus, so you know which MAK you are dealing with. /dhistoryacterrprints the MAK and retail activation failure history, which distinguishes a limit from a run of network failures.- Look the key up in your volume licensing portal. The remaining count lives at Microsoft’s end and is not visible from the client.
- Decide between the two real options: request an activation increase for that key, or buy the licences the deployment actually needs.
- As an interim measure on a machine that must work today, install a different MAK that still has seats:
/unpkey:then/inpkey:and/act.
Microsoft also publishes 0xC004C021, the Multiple Activation Key extension limit having been exceeded. That is what a granted increase looks like when it runs out too.
If a key with seats left activates the machine you are unblocked. If you need to decide what to do about the pool itself, the next section covers where the seats went.
Why it happens
A Multiple Activation Key carries a fixed number of activations. Microsoft’s own wording is that each MAK has a predetermined number of allowed activations based on your volume licensing agreement, and that each Office activation using MAK counts towards the activation limit. When the number is used up, the activation server refuses the next request, and that is the code you have.
The distinction that matters is between activations and devices. The count is consumed per activation, not per device, and Microsoft publishes no mechanism for returning one. Rebuild a machine and activate it again and you have spent two. Reimage a lab of thirty machines twice a year and the arithmetic becomes uncomfortable quickly, without a single extra device existing.
It is worth being careful here, because a lot of confident tables circulate about exactly what does and does not consume a seat. Microsoft publishes the rule quoted above and not much else. Treat any claim beyond it as an inference rather than a fact, and settle a specific question by looking at the consumed count in your volume licensing portal rather than by reasoning about it.
The count itself is not visible on the client. ospp.vbs tells you which key is installed and whether this machine is licensed; the remaining pool lives on Microsoft’s side and is exposed through your volume licensing portal, or through the Volume Activation Management Tool if you use it to manage keys centrally. If somebody tells you the remaining count from a client command, they are reading something else.
The estate genuinely outgrew the key
You have this one if The portal shows zero remaining, and the number of devices you have is close to or above the number of licences you bought.
- Count the devices actually running Office, not the ones you have licences for. The gap is what you need to buy.
- Buy the additional licences and use the key issued with them.
- Install it on the machines that failed:
cscript ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXXthencscript ospp.vbs /act.
There is no supported way to activate more devices than you hold licences for, and asking for an increase to cover real devices is asking Microsoft to help you stay out of compliance.
Rebuilds burned through the pool
You have this one if You have far fewer devices than activations consumed, and the team reimages regularly.
- Request an activation increase for the key through the Microsoft Licensing Activation Centers, which is Microsoft’s documented resolution for this code, and explain the reimaging pattern.
- Reduce future consumption by moving reimaged estates to KMS or Active Directory-based activation, where reactivation costs nothing.
- Where MAK has to stay, capture images with Office rearmed rather than activated, and run
OSPPREARM.EXEbefore Sysprep.
The key is shared more widely than you think
You have this one if The count fell faster than your own deployments explain, and the key has been circulated by email or left in a shared document.
- Find out who holds the key. A MAK in a shared folder or a wiki page gets used by people who were never in your planning.
- Restrict it to your deployment tooling rather than to individuals.
- Request a replacement key if you believe it has left the organisation, and treat the old one as spent.
A MAK is a bearer credential. Anyone with the string can consume your seats, and there is no mechanism tying it to your devices.
The key was deployed to the wrong machines
You have this one if Activations were consumed by devices you did not intend to license this way, such as test virtual machines or a second Office edition.
- Audit which machines carry the key:
/dstatusreports the last five characters, which is enough to identify it. - Remove it from machines that should be using KMS:
cscript ospp.vbs /unpkey:<last five>, then let the GVLK activate against your host. - Request an increase for the seats consumed in error, and expect to justify the request.
Full reference
What is documented about the count, and what is not
| Statement | Status |
|---|---|
| Each MAK has a predetermined number of allowed activations, based on your volume licensing agreement | Published by Microsoft |
| Each Office activation that uses MAK counts towards the activation limit | Published by Microsoft |
| The remaining count is visible in your volume licensing portal or through VAMT, not on the client | Published: the client tools show installed keys and status, not the pool |
| More activations can be requested from the Microsoft Licensing Activation Centers | Published as the resolution for this code |
| Precisely which events consume a seat, device by device | Not published in that detail. Check the consumed count rather than reasoning about it |
MAK against KMS, for an estate that reimages
| MAK | KMS | Active Directory-based activation | |
|---|---|---|---|
| Activation model | A finite pool, consumed permanently | A 180-day licensed period, renewed every seven days | Up to 180 days, renewed from the directory |
| Cost of a rebuild | Another activation from the pool | Nothing | Nothing |
| Infrastructure | None | A host, a DNS record, TCP 1688 | The Office Volume License Pack on a domain controller |
| Minimum count | None | Five for Office | None published |
| Suits | Machines that rarely change and cannot reach a host | Estates above the threshold | Domain-joined estates |
That table is the real argument for moving a lab or a test estate off MAK. The pool is not the problem; the rebuild rate against a finite pool is. A site that reimages weekly will exhaust any key eventually, and the second increase request is a harder conversation than the first.
The client commands worth knowing
| Switch | What Microsoft says it does |
|---|---|
/dstatus |
Displays licence information for installed product keys |
/dhistoryacterr |
Displays the failure history for MAK and retail activation |
/unpkey:<last five> |
Uninstalls an installed key by its last five digits |
/inpkey:<key> |
Installs a product key, replacing an existing key |
/act |
Activates installed Office product keys |
None of those shows how many activations remain. If you need that number, it comes from the volume licensing portal or from the Volume Activation Management Tool, and it is worth checking before a deployment rather than after one fails.
The two companion codes
0xC004C005 and 0xC004C011 have no published descriptions. Both sit in the activation-server family, so both describe a decision taken at Microsoft’s end rather than a fault on the machine, but nobody outside Microsoft can tell you which decision. Read the machine’s own text with cscript ospp.vbs /ddescr: and treat that as the authority.
Before you ask for an increase
- Produce a device count from your management tooling rather than from memory. The request will be assessed against it.
- Compare that count with the licences on your agreement. If devices exceed licences, an increase is the wrong request.
- Note the reimaging pattern, since that is the case increases exist for.
- Have the agreement number and the key to hand. Microsoft’s documented route for this code is the Microsoft Licensing Activation Centers.
When a licence is the actual fix
When a MAK reports zero remaining, the licence is the fix, because the count is the licence. An activation increase is worth requesting where reimaging is the cause and your device count is genuinely below your licence count, and Microsoft’s documented resolution for this code is exactly that request. Where the devices are real, the honest answer is that you are running more copies of Office than you bought. Arco supplies additional Office LTSC 2021 Professional Plus MAK seats to top up an existing deployment, and can check your device count against your agreement first so that you buy the number you actually need rather than guessing.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004C020 |
The activation server reported that the Multiple Activation Key has exceeded its limit. Microsoft’s remedy is to request more activations from the Microsoft Licensing Activation Centers | Microsoft Learn |
0xC004C005 |
An activation-server refusal in the same family. No published description | not published by the vendor |
0xC004C011 |
An activation-server refusal in the same family. No published description | not published by the vendor |
Confirm the fix worked
cscript ospp.vbs /dstatuson the affected machine reports a licensed status.- The last five characters shown match the key you intended to deploy.
cscript ospp.vbs /dhistoryacterrrecords no new failures after the change.- The remaining activation count for that key in your volume licensing portal has decremented as expected.
- An Office application opens with no Unlicensed Product wording in the title bar.
Questions people ask about this
Can I get activations back from decommissioned machines?
Microsoft publishes no client command that returns a MAK seat to the pool. What is documented is the other direction: request more activations from the Microsoft Licensing Activation Centers, and explain that the devices no longer exist.
How do I see how many are left?
Not from the client. The client tools show which key is installed and whether the machine is licensed. The remaining pool lives at Microsoft’s end, exposed through your volume licensing portal or the Volume Activation Management Tool.
Would KMS avoid this?
Yes, for the reimaging problem specifically. A KMS activation is a 180-day licensed period that renews, so rebuilding a machine costs nothing from a pool. It needs five Office clients before it activates anything, so it only helps above that size.
What is 0xC004C021?
Microsoft publishes it as the Multiple Activation Key extension limit having been exceeded. In practice that is the code you see when an increase was granted and has now been used up as well.
Is buying more seats the only option?
No. If your device count is genuinely below your licence count and rebuilds ate the difference, request an increase first, because that costs nothing. Buy only when you are actually running Office on more devices than you are licensed for.
