Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0xC004B007

0xC004B007 and 0xC004FC03: Windows Cannot Reach the Activation Servers

10 min read Updated October 5, 2026 Windows Activation & Licensing

Fix it now

Microsoft documents 0xC004FC03 as not being connected to the internet, or a firewall blocking activation. 0xC004B007 is not published and sits in a range of server-side refusals, so prove the path first: if the connection test succeeds, this is not a network fault and you are reading the wrong article.

Elevated Command Prompt, in order

netsh winhttp show proxy
w32tm /query /status
w32tm /resync
cscript //nologo %windir%\system32\slmgr.vbs /ato
  1. Test the path from PowerShell: Test-NetConnection licensing.mp.microsoft.com -Port 443. Microsoft documents that host as the endpoint used for online activation.
  2. If that fails, the traffic is being blocked and the fix is a firewall or proxy change, not a licence.
  3. If it succeeds and activation still fails, check the proxy the system services use – it is not the one in your browser. netsh winhttp show proxy shows it; netsh winhttp import proxy source=ie copies the user settings across.
  4. Ask whoever runs the firewall to exempt the Microsoft activation and licensing endpoints from TLS inspection rather than merely permitting them.

Nothing here costs money. These codes are raised before any judgement is made about your key, so anyone selling you a licence on the strength of one is selling you something you do not need.

If activation succeeds after the network change, you can stop here. If the path is clean and the refusal continues, the next section explains why 0xC004B007 may not be a network code at all.

Why it happens

Activation is performed by a system service, not by you, and that single fact explains most corporate cases. The service does not use the proxy configured in your browser or your user profile; it uses the WinHTTP proxy configuration, which is machine-wide and separate. The web works perfectly for the signed-in user while the licensing service has no route out at all, and the code you get says nothing about which of the two is broken.

0xC004FC03 is the one code here Microsoft publishes, and it is published exactly as you would hope: you are not connected to the internet, or a firewall is blocking activation. 0xC004B007 is not published, and that matters more than it sounds. Its neighbours in that range – 0xC004B001 to 0xC004B006, 0xC004B008 and 0xC004B009 – are all documented as the activation server determining that the licence is invalid, or that the computer could not be activated. So a network reading of 0xC004B007 cannot be assumed, and the connection test at the top of this page is what tells you which article you should be in.

Two of the companion codes are also documented as problems at Microsoft’s end rather than yours. 0xC004C012, with 0xC004C013 and 0xC004C014, is documented as the activation server being temporarily unavailable, with Windows activating automatically once the service is back. 0x87E10BC6 is documented as an error on the activation server or in the licensing service, with the recommended action being to wait a few minutes, run the troubleshooter, then open Microsoft Store. Neither is a reason to touch the firewall.

The system proxy is unset or wrong

You have this one if Browsing works, netsh winhttp show proxy reports direct access, and the network requires a proxy.

  1. Read the current setting: netsh winhttp show proxy.
  2. Set it: netsh winhttp set proxy proxy-server=<server:port> bypass-list="<hosts>".
  3. Where the user settings are already right, import them instead: netsh winhttp import proxy source=ie.
  4. Retry with slmgr /ato.

To undo it later, run netsh winhttp reset proxy.

TLS inspection is breaking the connection

You have this one if The port test to 443 succeeds but activation still fails, and the firewall is known to terminate and re-sign outbound HTTPS.

  1. Ask the network team to add the Microsoft activation and licensing endpoints to the inspection bypass list, not merely to the allow list.
  2. Include licensing.mp.microsoft.com, which Microsoft documents as the endpoint for online activation and some app licensing.
  3. Retry and check whether the code changes. A different code after the bypass usually means progress rather than a new problem.

Microsoft also documents that blocking that endpoint requires disabling the Windows License Manager Service, and that doing so blocks online activation. If someone has done that deliberately, the firewall is not where the fix is.

The system clock is wrong

You have this one if The date or time is noticeably off, often after a flat CMOS battery or a firmware reset. Microsoft documents 0x80072F8F for exactly this.

  1. Check the source and state: w32tm /query /status.
  2. Resynchronise: w32tm /resync. There is no /force parameter; the command takes /computer, /nowait, /rediscover and /soft only.
  3. On a domain member, confirm it is syncing from a domain controller rather than an unreachable external source.
  4. Replace the CMOS battery if the clock drifts after every power cycle.

The failure is at Microsoft’s end, not yours

You have this one if The code is 0xC004C012, 0xC004C013, 0xC004C014 or 0x87E10BC6, and the connection test succeeds.

  1. Do nothing to the network. Microsoft documents these as the activation server being temporarily unavailable, or an error in the licensing service.
  2. Wait, and let Windows retry on its own schedule. The documented behaviour is that it activates automatically when the service returns.
  3. For 0x87E10BC6, the documented sequence is to wait a few minutes, run the activation troubleshooter, then open Microsoft Store.

Full reference

Where to look, by symptom

What you observe Where to look
Activation fails on every machine on one network Firewall, proxy or TLS inspection at the edge
Activation fails on one machine only The WinHTTP proxy configuration, or the clock on that machine
It works on guest wireless but not on the corporate network Outbound filtering or inspection on the corporate path
It works over VPN from home but not in the office Split tunnelling is sending activation traffic down the blocked path
The failure started after a firewall change A newly added inspection rule or category block
The port test succeeds and activation still fails Not a connectivity problem. Read the code again

The proxy commands, with the documented syntax

Command What it does
netsh winhttp show proxy Shows the machine-wide proxy the system services use
netsh winhttp set proxy proxy-server=<server> bypass-list=<hosts> Sets it, with an optional bypass list
netsh winhttp import proxy source=ie Copies the current user’s settings into the machine-wide configuration
netsh winhttp reset proxy Clears it and returns to direct access

The parameter names matter. netsh winhttp set proxy <server:port> is widely quoted but the documented form names the parameters, and the bypass list is a separate one. Get it wrong and you will set nothing while believing you set something.

Which endpoints activation needs

Microsoft publishes licensing.mp.microsoft.com as the endpoint used for online activation and some app licensing on Windows 11, and notes that blocking it means disabling the Windows License Manager Service, which blocks online activation. Its ESU guidance separately names https://activation.sls.microsoft.com/BatchActivation/BatchActivation.asmx and https://go.microsoft.com/fwlink/?LinkId=82160 as activation URLs to allow. Ask your network team to work from Microsoft’s current published endpoint list rather than from a firewall rule somebody wrote years ago.

If the machine will never have internet access

Offline activation still exists, but the route has changed and the old advice is now wrong. Microsoft’s offline activation page states that if you are shown an activation telephone number, you should not call it. The installation ID and confirmation ID exchange is done through the product activation portal at aka.ms/WindowsActivate instead.

  1. Get the installation ID: slmgr /dti, or use the option on the activation page that displays it. On earlier builds slui 4 opens the same screen.
  2. Submit the installation ID at aka.ms/WindowsActivate.
  3. Complete activation with slmgr /atp <ConfirmationID>.
  4. Confirm with slmgr /dli and slmgr /xpr.

When the path is clean and it still fails

  • Read the code again. If it is a 0xC004C or 0xC004B code and the connection test passes, the request reached Microsoft and was refused, which is a licensing question rather than a network one.
  • Test from a second machine on the same subnet. A failure on one machine and success on another puts the fault on the machine.
  • Check the Application log for Software Protection Platform entries around the attempt, and compare the times against the firewall log.
  • Confirm no captive portal is intercepting the connection. Guest wireless that needs a browser sign-in gives a machine account nothing to work with.
  • Confirm the Software Protection service is running and set to start automatically with a delayed start.

Every code this article covers

Code What it points at Source
0xC004B007 Seen when activation fails to complete. Microsoft publishes no meaning, and the surrounding codes in the same range are documented as activation-server refusals, so test the connection before treating it as a network fault not published by the vendor
0xC004FC03 You are not connected to the internet, or a firewall is blocking activation Microsoft Support
0xC004C012 Documented with 0xC004C013 and 0xC004C014 as the activation server being temporarily unavailable. Windows activates automatically when the service comes back online Microsoft Support
0x87E10BC6 An error occurred on the activation server or in the licensing service. The documented action is to wait a few minutes, run the troubleshooter, then open Microsoft Store Microsoft Support
Event ID 8208 Logged in the Application log by the Software Protection Platform around activation attempts. Microsoft publishes no description for this event ID, so use it as a timestamp rather than as evidence of a cause not published by the vendor

Confirm the fix worked

  1. Test-NetConnection licensing.mp.microsoft.com -Port 443 succeeds from the failing machine.
  2. netsh winhttp show proxy reports the setting you intended.
  3. w32tm /query /status shows a recent successful synchronisation.
  4. slmgr /ato completes without returning a code.
  5. slmgr /dli reports Licence Status: Licensed.

Questions people ask about this

Does this mean my key is bad?

No. These codes are raised before the key is judged. If the request had reached Microsoft and the key had been refused, you would see a 0xC004C code instead. Nothing here reflects on the licence.

Do I need to buy anything to fix it?

No. This is a firewall, proxy or clock problem and the fix is a configuration change on your network or your machine. Anyone selling you a licence for one of these codes is selling you something you do not need.

Which endpoints does activation need?

Microsoft publishes licensing.mp.microsoft.com as the endpoint for online activation on Windows 11, and names the batch activation URL under activation.sls.microsoft.com in its ESU guidance. The full list changes, so have your network team work from the current published list rather than an old rule.

Can I still activate a machine with no internet at all?

Yes, but not by telephone. Microsoft’s offline activation page says not to call the number if one is shown. Use slmgr /dti to get the installation ID, exchange it at aka.ms/WindowsActivate, then finish with slmgr /atp.

The connection test passes but activation still fails. What now?

Then this is not your article. Read the exact code: a 0xC004B or 0xC004C refusal with a working connection means the request reached Microsoft and was declined, which is a licensing question. The exception is 0xC004C012, 0xC004C013, 0xC004C014 and 0x87E10BC6, which Microsoft documents as its own service being temporarily unavailable.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Windows Activation Error 0xC004C008: Key Already In Use on Another PC License Error 0xC004F304: Active Directory-Based Activation Cannot Find a Licence License Error 0x803F8001 and 0x803F8003: No Usable Entitlement for the Signed-In Account License Error 0xC004D307: Maximum Rearms Exceeded and the Grace Timer Is Gone
โ† Back to Knowledge Base