Skip to content

Est. 2011·Microsoft Partner 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

License Error 0xC004B001

Office 0xC004B001: the activation server says the licence is invalid

12 min read Updated October 5, 2026 Office & Microsoft 365 Licensing

Recommended fix

Microsoft Office 2024 Professional Plus - LTSC Volume key online activation

Original price was: 49,90 €.Current price is: 16,90 €.

Fix It Now

Fix it now

0xC004B001 is Microsoft’s activation service refusing what you presented. The published meaning is short: the activation server determined that the licence is invalid. Nothing local failed, so the work is finding out why the service said no – the key does not match the installed product, the channel is wrong, or the key has been withdrawn.

Run these in an elevated Command Prompt on a volume-licensed Office install

cd "C:\Program Files\Microsoft Office\root\Office16"
cscript ospp.vbs /dstatus
  1. Read three things out of the /dstatus output before touching anything: the product name, the channel, and the last five characters of the installed key. That tells you what is actually on the machine rather than what you meant to install.
  2. If ospp.vbs is not in that folder, you are on Microsoft 365 Apps. Microsoft states the script does not work there; run .\vnextdiag.ps1 -action list from the same folder instead, and treat any product key you were given as the wrong tool for this install.
  3. Remove the rejected key with cscript ospp.vbs /unpkey:XXXXX, using the last five characters shown by /dstatus.
  4. Install the key issued for that exact version and edition with cscript ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX, then run cscript ospp.vbs /act.
  5. If the same code comes back, stop retrying. The refusal is recorded against the key at Microsoft’s end and repeating the request produces the same answer.

On 32-bit Office running on 64-bit Windows the folder is C:\Program Files (x86)\Microsoft Office\root\Office16. Older guidance gives the path without root\; both resolve to the same place on a Click-to-Run install, and root\Office16 is what the current documentation uses.

If Office now reports itself licensed you can stop here. If the service refused a second time, the next section explains what it is deciding and why no local change alters it.

Why it happens

Microsoft splits Office activation failures into two published groups, and the group a code belongs to tells you which machine to work on. Codes in the 0xC004F range come from the Software Licensing Service running on your own computer: a licence that could not be found, a manifest that is wrong, a verification that could not be completed. Codes in the 0xC004B and 0xC004C ranges come back from Microsoft’s activation service and describe a decision taken there.

0xC004B001 sits in the second group. Microsoft publishes one line for it – the activation server determined that the licence is invalid – and publishes the identical line for 0xC004B002 through 0xC004B006, 0xC004B009 and for the 0xC004C005 to 0xC004C011 band. That uniformity is the useful part. The service is not telling you which of several problems it found; it is telling you that it looked at what you sent and would not accept it. Everything below is about narrowing that down from your side, because the service will not narrow it for you.

What it will not tell you is worth stating plainly, because it saves hours. It does not say the network is broken – the request clearly arrived. It does not say Office is damaged – a damaged install fails earlier and with a different code. And it does not say your entitlement is wrong in the abstract; it says this particular key, presented against this particular product, was refused.

The key does not match the installed product

You have this one if /dstatus names one Office version or edition and the key was issued for a different one.

  1. Take the product name from /dstatus, not from the purchase order. Reference images and deployment mistakes routinely put a different edition on the disk from the one that was bought.
  2. Remove the mismatched key: cscript ospp.vbs /unpkey:XXXXX.
  3. Install the key issued for that version and edition, then cscript ospp.vbs /act.
  4. If the installed edition is not the one you hold a licence for, redeploy the right edition rather than looking for a key that will take.

A Standard key will not activate Professional Plus, and a key for an earlier Office release will not activate a later one. Neither combination degrades gracefully; both are refused outright.

A volume key was presented to a subscription install

You have this one if There is no ospp.vbs in the Office folder, or vnextdiag.ps1 is present and reports a licence whose ID begins EWW.

  1. Confirm which family you are on. Microsoft states that from version 1910 Microsoft 365 Apps stopped using the Office Software Protection Platform, and that ospp.vbs does not work for it or for subscription Project and Visio.
  2. Run .\vnextdiag.ps1 -action list from the Office folder to see what the subscription install thinks it holds.
  3. Licence it by signing in with an account that has a seat assigned, not by installing a key.

The installation channel and the key disagree

You have this one if The build came from one source and the key from another – a consumer download being handed a volume key, or the reverse.

  1. Read the channel from /dstatus and compare it with what your licence covers.
  2. Redeploy from the source that matches: volume media and the Office Deployment Tool for a volume licence.
  3. Install the matching key and activate.

The key has been withdrawn at the service

You have this one if The key activated machines successfully in the past and now fails everywhere at once, including on machines that were licensed before and have been rebuilt.

  1. Stop deploying it. Every further attempt is refused the same way.
  2. Establish where it came from and whether there is an invoice and an agreement behind it.
  3. Replace it with a key you can trace, then reactivate the affected machines.

Microsoft publishes a separate code, 0xC004C003, for a key the activation server has determined is blocked. If that is what you are seeing, it is a different and more final answer than this one.

Full reference

Reading the two published groups apart

Range Where the decision was made What that means for you
0xC004B*** Microsoft’s activation server The request arrived and was refused. Work on the key and the product, not the machine
0xC004C*** Microsoft’s activation server Same. Microsoft publishes most of this band with the same licence-invalid text
0xC004F*** The Software Licensing Service on this PC A local licence, manifest or verification problem. A different family of fixes

Microsoft’s own error tables for Office are organised exactly this way, with an activation-server list and a Software Licensing Service list, so the first character after 0xC004 is a reliable signpost even when the specific code is not published.

The ospp.vbs options this article uses

Command What Microsoft documents it as doing
cscript ospp.vbs /dstatus Displays licence information for installed product keys
cscript ospp.vbs /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx Installs a product key, replacing an existing one
cscript ospp.vbs /unpkey:value Uninstalls an installed product key, identified by its last five characters
cscript ospp.vbs /act Activates the installed Office product keys
cscript ospp.vbs /sethst:kmstest.contoso.com Sets a KMS host name
cscript ospp.vbs /remhst Removes the KMS host name and resets the port to 1688

Microsoft documents ospp.vbs as applying to volume-licensed Office LTSC 2024, Office LTSC 2021, Office 2019 and Office 2016, including Project and Visio. It says the script does not work for Microsoft 365 Apps or for subscription versions of Project and Visio.

When the same key works elsewhere

A key that activates on one machine and is refused on another is not, in fact, a server-side refusal for the second machine, and this code is then the wrong lead. Check what differs: the installed edition, the architecture, the channel, and whether the machine actually reached Microsoft at all. A request that never left produces network-shaped codes rather than a licence-invalid answer from the server.

Codes that arrive at the same dialog from a different place

Code What Microsoft publishes Where it leaves you
0xC004C003 The activation server determined the specified product key is blocked Permanent. Nothing local reverses it
0xC004C001 The activation server determined the specified product key is invalid Check the key itself before anything else
0xC004C020 The Multiple Activation Key has exceeded its limit A volume licensing question, not a product-mismatch question
0xC004F050 The Software Protection Service reported that the product key is invalid Local licensing service, not the activation server

What is not published, and how to treat it

Two of the codes people see alongside this one, 0xC004C014 and 0xC004C00C, are not in Microsoft’s published Office activation tables at all. The tables cover 0xC004C005, 006, 009, 00A, 00B, 00D and 011 and stop there. Treat an unpublished neighbour as what it visibly is – another refusal from the same service, in the same exchange – and diagnose from the published code you also have. Do not let a page that offers you a confident meaning for one of them change your plan; if the vendor has not published it, that meaning was reconstructed by somebody who wanted the story to work.

Before you conclude you need a different licence

  1. Confirm the exact product name and edition from /dstatus on the failing machine.
  2. Confirm the last five characters of the installed key match the key you intended to install.
  3. Retype the key once, in case of a transcription error, then activate. Once is a genuine check; twice tells you nothing new.
  4. Test the same key on a second machine of the same edition. Refused on both means the key; accepted on the other means the machine.
  5. If the key came through a volume agreement, look it up in your own licensing portal before buying anything. Keys deployed from the wrong agreement are common and cost nothing to correct.

When a licence is the actual fix

When the activation service refuses a key outright, no configuration on your side changes the answer, because the decision is not being taken on your side. Either the key is for a different product, in which case you need the right one, or it has been withdrawn, in which case it will not work again anywhere. Arco supplies Office LTSC 2024 Professional Plus as a genuine perpetual licence with an invoice behind it, and we will check the version, edition and architecture actually installed on your machines before issuing a key, because the most common reason this code repeats is a key that was correct for the product somebody thought was deployed.

Every code this article covers

Code What it points at Source
0xC004B001 The activation server determined that the licence is invalid Microsoft Learn
0xC004B002 The activation server determined that the licence is invalid – Microsoft publishes the same text as for 0xC004B001 Microsoft Learn
0xC004C006 The activation server determined the licence is invalid Microsoft Learn
0xC004C014 Seen in the same exchange as the codes above. Microsoft’s published activation-server table covers 0xC004C005, 006, 009, 00A, 00B, 00D and 011 and does not include this one not published by the vendor
0xC004C00C Another refusal returned by the activation service. Not in Microsoft’s published table; read it alongside whichever documented code you also have not published by the vendor

Confirm the fix worked

  1. cscript ospp.vbs /dstatus reports the licence status as licensed.
  2. The last five characters shown match the key you intended to install.
  3. The product name in that output is the edition you hold a licence for.
  4. Rebuild or reboot one machine and confirm it activates again without anyone touching it.
  5. Activate a second machine from the same key to confirm the fix was the key and not that one computer.

Questions people ask about this

Will reinstalling Office help?

No. Nothing on the machine failed. The request was built correctly, sent successfully and refused by Microsoft’s activation service. A reinstall produces an identical request and an identical refusal.

Does 0xC004B001 mean my key is blocked?

Not necessarily. Microsoft publishes a separate code for a blocked key, 0xC004C003, described as the activation server determining that the product key is blocked. 0xC004B001 is the broader licence-invalid refusal, and a product or edition mismatch produces it just as readily.

Why does the code look the same for several different problems?

Because Microsoft publishes one text across most of the 0xC004B and 0xC004C bands. The service is reporting a decision, not a diagnosis. That is why the fix starts with reading what is installed rather than with reading the code.

Can I use ospp.vbs on Microsoft 365 Apps?

No. Microsoft states the script does not work for Microsoft 365 Apps or subscription versions of Project and Visio, which moved off the Office Software Protection Platform at version 1910. Use vnextdiag.ps1 from the same folder instead.

Is a cheap key from a marketplace worth trying?

It is worth understanding what you are buying. A licence sold well below the cost of the licence is usually somebody else’s entitlement, and when the service withdraws it, it stops working on every machine at once, including ones that were activated months earlier. There is no local remedy for that.

Need a genuine license?

Microsoft Office 2024 Professional Plus - LTSC Volume key online activation

Microsoft Office 2024 Professional Plus - LTSC Volume key online activation

Original price was: 49,90 €.Current price is: 16,90 €.

Get It Now

Instant digital delivery · Genuine license · 15 years trusted

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Office for Mac 0xD000000C: the keychain cannot store the sign-in Free Fix Office 30015-4: the Click-to-Run install fails part way through License Error Office 0xC004F038: your KMS count is below the minimum of five clients Free Fix Office 0x8007139F and 0xC0020017: the licensing service cannot reach the KMS host
← Back to Knowledge Base