Fix it now
Microsoft publishes 0xC004C009, and the three codes usually seen with it, as one line: the activation server determined the licence is invalid. It is a decision taken at Microsoft’s end about what you presented, so start by reading what is actually installed and which account is signed in, rather than counting devices.
- In File, then Account, read which account Office is signed in as, and what product name is shown. Note whether the account belongs to one person or is shared.
- If the product is a volume or perpetual build, read the installed key with
cscript ospp.vbs /dstatusfrom the Office program folder and confirm it matches the version and edition installed. - If the on-screen message says the account has recently been used to activate too many computers, that is a separate documented condition – wait 24 hours or sign in with a different licensed account, and read the reference section below.
- On any machine that person no longer uses, sign out of Office from File, then Account, so the installation is released.
- If the failures are coming from a Remote Desktop host, a multi-session image or a non-persistent pool, stop activating per device and use shared computer activation instead.
Nothing you run locally changes a decision recorded at Microsoft’s end. Repeating the request produces the same refusal, so spend the effort on establishing what was presented rather than on retrying.
If Office activates you can stop here. If not, the next section explains what is actually being counted, by whom, and why the published meaning of this code is narrower than most people assume.
Why it happens
The first correction is the code itself. Microsoft’s published Office activation tables give 0xC004C009, 0xC004C00A, 0xC004C00B and 0xC004C00D the same single line: the activation server determined the licence is invalid. That is the whole published meaning. It does not say the account has activated too many machines, and treating it as a device-count message sends people to audit their estate when the service may simply have refused what was sent.
The too-many-computers condition is real and Microsoft documents it – but by its message, not by this code. On a shared computer the wording is “Sorry, this Microsoft 365 account has recently been used to activate too many computers. To continue using this product, please try again later or sign in with a different Microsoft 365 account”, and the documented remedy is to wait 24 hours or use a different licensed account. Note what that is: a rate limit over a period, not a permanent per-account ceiling.
There is a separate, published limit that people conflate with it. The Office applications service description publishes five installs per user on PC or Mac for Microsoft 365 Apps for enterprise, Microsoft 365 Apps for business, Business Standard and Business Premium. That is a per-user allowance on ordinary devices, held at Microsoft’s end, and signing out of Office on a machine releases that installation. Neither of these two limits is the published meaning of 0xC004C009, and knowing which one you are actually up against decides everything you do next.
The third mechanism is the one that removes the problem on shared hardware. Shared computer activation licenses the signed-in user for a limited period rather than binding to the machine, and Microsoft documents it as the required method for installing Office on Remote Desktop Services. It has its own rate limit – the too-many-computers message above is documented on the shared computer pages – so it is not unlimited, but it is the only supported way to run Office where many people use one machine.
What was presented was not valid for what is installed
You have this one if A volume or perpetual build, and /dstatus shows a key that does not match the installed version, edition or channel.
- Read the product name, channel and last five key characters from
cscript ospp.vbs /dstatus. - Remove the mismatched key with
cscript ospp.vbs /unpkey:XXXXX. - Install the key issued for that exact version and edition, then
cscript ospp.vbs /act. - If the installed edition is not the one you own, redeploy the right edition rather than looking for a key that will take.
One account is being used by several people
You have this one if The same sign-in appears on machines belonging to different members of staff – an office, reception or shop-floor account.
- List the machines using that account and identify who actually works on each.
- Give each person their own account and their own assigned seat.
- Sign out of Office on every machine moving to a different account, then sign in with the new one.
- Where a genuinely shared machine remains, license it for shared use rather than pointing everyone at one identity.
Worth fixing beyond the error. Shared sign-ins break auditing, make offboarding unsafe, and are outside the terms of a per-user subscription.
Retired devices are still holding installations
You have this one if One legitimate user, no sharing, and a history of replaced or reimaged machines.
- Sign out of Office on any old machine you can still reach. That is what releases the installation.
- For a work or school account, have an administrator review the user’s devices and sessions in the admin centre.
- Have the user sign in once on each machine they still use, so the current set is the recorded set.
Non-persistent virtual desktops are consuming installations
You have this one if A pooled VDI or multi-session environment recreated from an image, with failures appearing within days of a rebuild.
- Stop using device-based activation there.
- Deploy Office with shared computer licensing enabled, or set
SharedComputerLicensingto1(REG_SZ) underHKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configurationin the image. - Confirm the users’ plan carries shared computer activation before relying on it – the setting alone does not grant the right.
- Rebuild the image and confirm new sessions license the user rather than the machine.
The account has hit the shared activation rate limit
You have this one if The message names too many computers activated recently, and it appeared after a burst of activity on shared infrastructure.
- Wait 24 hours, which is Microsoft’s documented remedy, or use a different licensed account meanwhile.
- Find what caused the burst: a pool rebuilt repeatedly, a test loop, or one account used to prove the host works.
Full reference
The three limits people confuse
| Limit | What it is | How it is cleared |
|---|---|---|
| Five installs per user on PC or Mac | Published for Microsoft 365 Apps for enterprise and for business, Business Standard and Business Premium | Sign out of Office on a machine to release its installation |
| Shared computer activation rate limit | An account used to activate too many shared computers within a period | Wait 24 hours, or sign in with a different licensed account |
| Volume key limits | A Multiple Activation Key has a finite pool of activations | A volume licensing question. 0xC004C020 is the published over-limit code |
None of those three is the published meaning of 0xC004C009. Establish which one you are actually facing from the message on screen and from the shape of the failure, then work that limit. Reading the code as a count is how people end up auditing an estate to solve a key mismatch.
The codes in this record
| Code | Published text |
|---|---|
0xC004C009 |
The activation server determined the licence is invalid |
0xC004C00A |
The activation server determined the licence is invalid |
0xC004C00B |
The activation server determined the licence is invalid |
0xC004C00D |
The activation server determined the licence is invalid |
Microsoft publishes the same text across most of the 0xC004B and 0xC004C bands. The uniformity is the point: the service is reporting a decision, not a diagnosis, and the diagnosis has to come from what you presented and from the message the user actually saw.
Shared computer activation on shared hardware
| Item | Value |
|---|---|
| Registry value | SharedComputerLicensing, String (REG_SZ) set to 1 |
| Registry key | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration |
| Token location | %localappdata%\Microsoft\Office\16.0\Licensing |
| Token lifetime | 30 days, renewed automatically while the user is signed in and online |
| Plans that include it | Any plan with Microsoft 365 Apps for enterprise; plans with desktop Project or Visio; education plans with Apps for enterprise; Microsoft 365 Business Premium |
Microsoft’s guidance is that Microsoft 365 Apps for enterprise is supported on user-dedicated VDI, and that to install on Remote Desktop Services you must use shared computer activation. On a session host it is not an optimisation, it is the supported method.
Where extra activations come from
- Machines that were reimaged, scrapped or replaced without anyone signing out of Office first.
- Non-persistent virtual desktops rebuilt overnight, each rebuild presenting as a new device.
- One account used by a team – reception, a workshop, a till – which spends one person’s allowance on everybody’s machines.
- Test loops during a deployment, which is how the shared activation rate limit usually gets tripped.
- A user with a personal and a work account who signs in with whichever one Office offers first.
Before you conclude you need more seats
- Read the on-screen message, not just the hexadecimal code. The two are describing different things and only one of them names a limit.
- Confirm what product is installed and, on a volume build, which key is in it.
- Sign out of Office on the machines the user has genuinely retired.
- On shared hardware, confirm shared computer activation is enabled and that the plan carries the right.
- Count the people who need Office, not the machines they use. That number is what a per-user subscription is priced against.
When a licence is the actual fix
Once you have established that the refusal really is about how many people are working under one identity, the honest answer is a seat each. A per-user subscription licenses one named person on their own devices, so a team sharing one sign-in needs one seat per person, and a Remote Desktop or virtual desktop estate needs a plan that carries shared computer activation for everyone who signs in to it. Microsoft 365 Apps for enterprise is the usual answer for shared infrastructure, and Business Premium carries the same right at the business tier if that suits you better. Arco supplies either, and will help you work out how many people actually need a seat before you buy – releasing installations from machines that no longer exist is free, and it is worth doing first.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004C009 |
The activation server determined the licence is invalid | Microsoft Learn |
0xC004C00A |
The activation server determined the licence is invalid | Microsoft Learn |
0xC004C00B |
The activation server determined the licence is invalid | Microsoft Learn |
0xC004C00D |
The activation server determined the licence is invalid | Microsoft Learn |
Confirm the fix worked
- Open Word on the target machine and confirm File, then Account shows the product as activated with no prompt.
- On a volume build,
cscript ospp.vbs /dstatusreports the licence as licensed and names the key you intended. - On shared infrastructure, confirm the shared computer licensing value is present and that a second user can also activate.
- Confirm the machines the user has retired no longer appear as signed in.
- Come back after a week and confirm no new refusals have appeared, which tells you the cause was fixed rather than the symptom.
Questions people ask about this
Does 0xC004C009 mean too many computers?
No. Microsoft publishes it, along with 0xC004C00A, 0xC004C00B and 0xC004C00D, as the activation server determining that the licence is invalid. The too-many-computers condition is documented separately, by its on-screen message, with a different remedy.
How many devices does one subscription cover?
The Office applications service description publishes five installs per user on PC or Mac for Microsoft 365 Apps for enterprise and for business, and for Business Standard and Business Premium. Check your own plan’s service description if you are close to the limit.
Does signing out really free an installation?
Yes. Signing out under File, then Account releases that installation, and doing it before a laptop is wiped saves an administrator a job later. It is the correct way to retire a machine.
Does shared computer activation have a limit?
It has a rate limit rather than a fixed device count. Microsoft documents the message about an account being used to activate too many computers recently, with the remedy of waiting 24 hours or using a different licensed account. It is not unlimited, but it is designed for many users on one machine.
Do I have to buy more seats?
Only if more people genuinely need Office than you have seats for. If one person has accumulated old devices, releasing them costs nothing. If a team has been sharing one account, then each of them needs their own.
