Fix it now
Microsoft documents 0xC004B001 as the activation server determining that the licence is invalid, and 0xC004B100 as it determining that the computer could not be activated. The request arrived and was refused, so local repairs cannot help. Prove the connection first, then work out what the server is refusing.
cscript //nologo %windir%\system32\slmgr.vbs /dlv
cscript //nologo %windir%\system32\slmgr.vbs /ato
- Confirm the traffic is getting through:
Test-NetConnection licensing.mp.microsoft.com -Port 443in PowerShell. If that fails you have a network problem, not this one. - Check the channel in the
/dlvoutput against what the key was sold as. A volume key on a retail installation, or the reverse, is refused at this stage. - If the code is 0xC004C012, 0xC004C013 or 0xC004C014, stop and wait. Microsoft documents those as the activation server being temporarily unavailable, and Windows activates by itself when it returns.
- If the key is a volume MAK, check the remaining activations with whoever administers the agreement before assuming anything about the key.
Stop after two or three attempts. Repeated failures achieve nothing and can add a second, unrelated error on top of the first.
If a channel correction or a wait clears it, you can stop here. If the refusal is consistent, the next section covers what the server is actually deciding.
Why it happens
When Windows activates online it sends a request describing the product key, the edition and a hardware identifier. Microsoft’s tables separate the refusals that come back into two shapes, and the difference is useful. 0xC004B001 and 0xC004B009 are documented as the activation server determining that the licence is invalid. 0xC004B008 and 0xC004B100 are documented as it determining that the computer could not be activated. The first pair points at the licence; the second at this machine’s request as a whole.
Either way the decision was made on Microsoft’s side, which rules out an entire class of fixes. Rebuilding the token store, running the troubleshooter, reinstalling Windows: none of them alter a decision recorded elsewhere. What is worth doing is establishing whether the licence you are presenting is the one this installation should be presenting at all, because a channel mismatch is refused here and is entirely fixable.
One code in this record is not a refusal at all, and reading it as one is expensive. Microsoft documents 0xC004C013, together with 0xC004C012 and 0xC004C014, as the activation server being temporarily unavailable, and states that Windows will activate automatically once the service is back online. A reader who takes that as a rejection of their key can end up replacing a perfectly good licence to fix an outage that would have cleared on its own.
0xC004B010 is not published. What can be said is that it is raised in the same exchange as the codes above, and that nothing about it justifies telling you the licence you bought is suspect. Retry, and if it persists escalate through whoever sold you the licence or through the volume licensing activation centre.
The channel of the key does not match the installation
You have this one if slmgr /dlv describes the installation as one channel and the invoice describes the key as another.
- Read the description line from
slmgr /dlvcarefully and compare it with the purchase record rather than with memory. - If the machine was built from volume media and you hold a retail key, reinstall from retail media or obtain a matching key.
- Once the channel matches, install with
slmgr /ipkand activate withslmgr /ato.
A volume MAK has spent its activations
You have this one if The key is a MAK from a volume agreement and other machines activated with it recently while this one did not.
- Check the remaining activation count with whoever administers the agreement.
- If the code is 0xC004C020, Microsoft documents that as the MAK having exceeded its limit, and directs you to the licensing activation centre to increase the number of activations rather than to buy again.
- Reclaim activations from decommissioned machines where the agreement supports it.
A MAK spends an activation per machine. Reimaging the same computer repeatedly can consume several unless the previous activation is reclaimed.
Microsoft’s activation service is temporarily unavailable
You have this one if The code is 0xC004C012, 0xC004C013 or 0xC004C014, and the connection test succeeds.
- Do nothing. Microsoft documents these as the service being temporarily unavailable.
- Leave the machine alone and let Windows retry on its own schedule; the documented behaviour is that it activates automatically when the service returns.
- Only investigate further if the same code is still there a day later.
The hardware changed and the entitlement no longer matches
You have this one if The machine activated before, several components or the board were replaced, and the refusal started immediately afterwards.
- Check when activation last succeeded, to confirm the change is the trigger.
- Run Troubleshoot from
Settings > System > Activationas an administrator and take the changed-hardware option if it appears. - If no transferable licence is offered, the entitlement did not survive the change.
There is no entitlement behind the key any more
You have this one if The key installs cleanly, the refusal is consistent from more than one network, and the key was bought cheaply or informally.
- Confirm the refusal is consistent by trying once from a different connection.
- Ask the seller for the licence documentation that accompanies the key.
- If nothing can be produced, treat the licence as gone and replace it.
Full reference
Which refusal is which
| Code | Documented meaning | What it points at |
|---|---|---|
0xC004B001 |
The activation server determined that the licence is invalid | The licence being presented |
0xC004B009 |
The activation server determined that the licence is invalid | The same, from the same stage |
0xC004B008 |
The activation server determined that the computer could not be activated | The request as a whole, not just the licence |
0xC004B100 |
The activation server determined that the computer could not be activated | The same; commonly seen on MAK activation |
0xC004C013 |
The activation server is temporarily unavailable | Microsoft’s service. Wait, do not act |
0xC004B010 |
Not published | Retry and escalate; do not assume the key is bad |
Ruling out the things that look similar
| Symptom | What it actually is |
|---|---|
| The port test to 443 fails | A firewall or proxy problem, not a server refusal |
The key will not install with slmgr /ipk |
A local format, product or edition mismatch |
| Every machine on site fails at once with these codes | A shared key that has run past its entitlement, or a service outage |
| Only machines rebuilt this week fail | Activations being spent faster than the agreement allows |
| A different key activates the same machine | The hardware and network are fine; the original entitlement is the problem |
| The code changes to something else the next day | It was a transient service problem all along |
Offline activation, and what changed about it
Guidance for this error used to say to try telephone activation with slui 4, on the basis that it takes a different path. That advice no longer holds. Microsoft’s offline activation page now states that if you are presented with an activation telephone number you should not call it, and routes the exchange through the product activation portal instead.
- Get the installation ID with
slmgr /dti, or from the option on the activation page that shows it. - Submit it at aka.ms/WindowsActivate and take the confirmation ID it returns.
- Finish with
slmgr /atp <ConfirmationID>. - Confirm with
slmgr /dliandslmgr /xpr.
Offline activation follows the same entitlement checks as the online route. It is the supported way to activate an isolated machine; it is not a way around a refusal, and if the entitlement is genuinely gone it will be refused there too.
Where the difference between suppliers shows up
A key resold outside the terms it was issued under installs locally without complaint and is refused here, because the local check only tests whether the key belongs to this installation while the server tests whether anyone is entitled to it. If you see these codes on a key that cost far less than the market price, that is usually the answer. It is also the point at which the paperwork matters: a supplier who can produce an invoice naming the product and the licence type can escalate a refusal, and one who cannot, cannot.
Before you conclude the licence is gone
- Try once from a different network, to rule out an intercepting proxy rewriting the request.
- Try the same key on a different machine. If it fails there too, the licence is the problem rather than either computer.
- Try a different key on this machine. If that activates, the hardware, store and network are all healthy.
- Wait a day and try once more. A service problem and a refusal look identical on the first attempt and completely different on the second.
- Check the exact code rather than the message. 0xC004C013 and 0xC004B001 produce similar-looking dialogs and mean entirely different things.
When a licence is the actual fix
When Microsoft refuses the licence itself, there is nothing left to configure: the licensing service on your machine is working, the network is working, and the entitlement behind the key is the missing part. That is the usual outcome for keys resold out of volume agreements and for keys attached to reversed transactions. Before you spend anything, rule out the two free endings – a channel mismatch you can correct, and a service outage that clears itself. If neither applies, Arco supplies Windows 11 Pro retail keys with an invoice and licence statement behind them, and will check the channel and edition reported by slmgr /dlv before you order so the replacement activates first time.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004B001 |
The activation server determined that the licence is invalid | Microsoft Learn |
0xC004B009 |
The activation server determined that the licence is invalid | Microsoft Learn |
0xC004B100 |
The activation server determined that the computer could not be activated | Microsoft Learn |
0xC004B008 |
The activation server determined that the computer could not be activated | Microsoft Learn |
0xC004B010 |
Raised in the same exchange as the codes above. Microsoft publishes no meaning; retry and escalate rather than assuming the licence is at fault | not published by the vendor |
0xC004C013 |
The activation server is temporarily unavailable. Documented with 0xC004C012 and 0xC004C014; Windows activates automatically when the service comes back online | Microsoft Support |
Confirm the fix worked
slmgr /atocompletes without returning a code.slmgr /dlireports Licence Status: Licensed.slmgr /xprreports permanent activation rather than a time-limited one.- The channel named in
slmgr /dlvmatches the licence you actually bought.
Questions people ask about this
How do I tell this apart from a network problem?
Test the connection to the activation endpoint on TCP 443 first. If that succeeds, the request reached Microsoft and a refusal is a genuine decision. If it fails, you are looking at a firewall or proxy problem and these codes are a red herring.
Will telephone activation get around it?
There is no telephone activation to try. Microsoft’s offline activation page now tells you not to call the number if one is offered, and routes the installation ID exchange through aka.ms/WindowsActivate. That route runs the same entitlement checks, so it is not a way around a refusal either.
I got 0xC004C013. Is my key dead?
No. Microsoft documents that code, with 0xC004C012 and 0xC004C014, as the activation server being temporarily unavailable, and states that Windows will activate automatically once the service is back. Wait rather than buying anything.
Can Microsoft reinstate a refused licence?
If you bought directly or from a reseller who can escalate, yes, provided the refusal was a mistake. A key from a marketplace listing with no documentation leaves nobody positioned to make that case for you.
Do I have to buy a new licence?
If the channel is simply wrong, no – reinstalling from matching media costs only time. If the service was temporarily unavailable, no. If the entitlement behind the key has been withdrawn, then yes, because no local change alters the server’s answer.
