0x87E10BC6 Activation Error: How to Fix It on Windows 11 and 10

The 0x87E10BC6 activation error has a plain cause. Windows reached the activation step but couldn’t finish the conversation with Microsoft’s activation or licensing service.

It appears on Windows 11 and on Windows 10 alike. In most cases the fix is simple.

• Wait a few minutes.
• Check that nothing blocks the connection: a VPN, a proxy, a firewall or a hosts file.
• Run the Activation troubleshooter or the activation command again.

The full message usually reads: “Something prevented us from communicating with our activation servers. Wait a few minutes and then try again.”

Note what it doesn’t say. There’s nothing about a bad key, and nothing about a used key.

That detail matters, because a key problem has its own codes. Treating this one like a key problem usually wastes an afternoon.

What 0x87E10BC6 stands for

Windows couldn’t complete activation because something went wrong while talking to Microsoft’s activation server or licensing service.

Microsoft’s own list of activation codes describes it that way. It recommends three things.

• Waiting a few minutes
• Running the Activation troubleshooter
• Retrying through the Microsoft Store

The product key itself is usually fine.

Think of activation as a short online exchange. Windows sends the key, or the hardware ID behind a digital license, to Microsoft.

The service answers with a license. With this code, that answer never arrives in a usable form.

Sometimes the service is busy. More often the request is stopped or altered on the way out of your network.

Microsoft lists the code on its Get help with Windows activation errors page for both client systems.

The same hexadecimal code also shows up outside activation. Microsoft Store apps or Xbox games can fail to launch with it.

Those cases share the licensing plumbing, since the Store hands out app licenses through the same services. That’s why some forum fixes for games look so similar.

Here the focus is the activation screen under Settings, System, Activation.

Causes

Ranked by how often each turns out to be the real reason, the list looks roughly like this.

The hosts file sits at this path:

C:\Windows\System32\drivers\etc\hosts

How to fix the 0x87E10BC6 activation error

Work from the least invasive step to the most. Most PCs activate before the last one.

1. Wait 10 to 15 minutes. Then open Settings, System, Activation and select Activate, and restart once if the button does nothing.
2. Disconnect any VPN and turn off proxy settings under Settings, Network & internet, Proxy. Pause third-party firewall or web-filtering software for the test.
3. Check date, time and time zone under Settings, Time & language, Date & time. Turn on Set time automatically and select Sync now.
4. Open the hosts file in Notepad as administrator. Remove or comment out lines that point Microsoft domains to 0.0.0.0 or 127.0.0.1, then save and flush DNS.
5. Run the Activation troubleshooter with the Troubleshoot button on the Activation page. The option appears only for an administrator.
6. If “Go to Microsoft Store” is offered, open it. When the Store reports a problem, choose Try again and wait for the confirmation.
7. Open Command Prompt as administrator and run the activation line below. A message box reports success or the exact code.
8. If it still fails, reinstall your own 25-character key and activate again. Skip this with a digital license and no key.
9. Read the “License Status” and “Notification Reason” lines in the detailed view to confirm the result.

ipconfig /flushdns
slmgr /ato
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /dlv

On Windows 10 the Activation page sits under Settings, Update & Security, Activation.

On a work laptop, try a network with no corporate proxy, if your IT policy permits.

The Store retry is the step Microsoft recommends for this code.

I’d run the activation line right after turning the VPN off or editing the hosts file. If it succeeds immediately, you’ve found the culprit. Then you know exactly what to add as an exception before switching that tool back on.

Matching the fix to the cause

Match the symptom to the cause before you touch anything.

• A failure on only one network points to a proxy or firewall.
• A failure right after a privacy tool ran points to the hosts file.
• A failure on every network for an hour or two typically comes from a temporary service issue.

Microsoft’s servers or your PC

Often it’s neither in the strict sense. The PC and the key are fine, and so is Microsoft’s service.

Something in between breaks the exchange. A real service-side problem tends to clear within hours with nothing touched.

If the code survives a day and several networks, look at your own machine: hosts file, security software, clock and services.

There’s a quick way to split the two. Connect the PC to a phone hotspot, with VPN and filtering software off, and press Activate.

If it works, your usual network is the issue, not Windows. If it still fails, move on to the services and the command line.

The overview of Windows 11 activation errors lists the related codes. A message that differs after one of these steps is itself useful information.

The licensing services

All of them start on demand. If a tuning page set any of them to Disabled, activation can fail with communication codes like this one.

So restore the default startup type. Open PowerShell as administrator and check their state:

Get-Service sppsvc, ClipSVC, LicenseManager | Format-Table Name, Status, StartType

A status of Stopped is normal, because these services start when needed. Disabled is not normal.

Some of these services are protected, so a few tools set them through the registry. If services.msc refuses your edit, I’d undo it with the tool that made it.

A restore point from before the tweak works too.

Forums often suggest resetting the Store cache with wsreset.exe. It’s harmless and sometimes helps when the Store step keeps failing. I wouldn’t count on it to repair activation by itself.

On Windows Server

On server systems the code typically has one of two causes.

• The server can’t reach Microsoft’s activation endpoints through a restrictive firewall or proxy.
• It still points to a KMS host.

Administrators on Microsoft’s own forum report it after adding and then removing the Volume Activation Services role. That was on Windows Server 2022.

slmgr /dlv
slmgr /ckms
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato

An evaluation build needs an edition conversion first. Our page on activating Windows Server with DISM covers the two DISM lines for that.

Event Viewer helps too. The Application log under Windows Logs records Security-SPP events with the reason for each attempt.

Servers on isolated networks need their own plan. If outbound HTTPS to Microsoft isn’t permitted at all, online activation can’t work.

The honest options are these.

• A firewall exception
• A KMS host inside the network
• Phone activation, where your license type allows it

Could the product key be the problem

Rarely. Microsoft reserves other codes for invalid, blocked or overused keys.

Say you fix the connection and the code turns into 0xC004C003, 0xC004C060 or 0xC004C008. Then the communication works, and the key is the issue.

That’s progress, and it tells you exactly which page to read next.

For example, 0xC004F074 points to a KMS host that couldn’t be reached. That situation is related but different.

The step-by-step Windows 10 activation guide explains how keys, digital licenses and Microsoft accounts fit together.

If the key turns out blocked or was never genuine, only a valid license fixes that for good.

Need a key? Our Windows 11 Pro key comes as a genuine license. We email it instantly after payment.

What to avoid

Avoid “activator” tools, KMS emulators and random scripts from video comments. They don’t fix this code.

They often add the very hosts entries and service tweaks that cause it, and they may install malware.

Also skip registry edits you can’t undo, and full Windows resets. Neither is needed for a communication problem like this one.

Two smaller traps deserve a line each. Reinstalling the same key ten times does nothing while the connection is blocked.

And don’t switch the edition through DISM on a home PC just to see if it helps.

That typically creates a real key mismatch on top of the original problem.

Where these steps apply

Enterprise editions of the client systems follow the same steps. Menu paths are written for Windows 11, with Windows 10 names where they differ.

Mistakes we see most

• Treating the code as a key problem and buying a second key.
• Retrying over the same VPN again and again.
• Forgetting a hosts file that a privacy script edited months ago.
• Leaving the clock wrong.
• Disabling licensing services to “speed up” the PC.
• Reinstalling the same key ten times.
• Using an activator tool.
• Resetting Windows for a communication problem.
• Leaving a stale KMS host set on a server.

Terms used on this page

A few cases from support

The office proxy

A laptop activates on a phone hotspot and fails at the office. The proxy there asks for authentication. IT exempts the licensing traffic, and activation works.

The privacy script

The code starts after a debloat script. The hosts file sends licensing domains to 0.0.0.0. With those lines removed, activation goes through.

The patient fix

Activation fails on every network one evening. Nothing gets edited. The next morning the PC is activated.

The server and its old host

One 2022 server keeps the code after a role was removed. A stale KMS host is still set. Clearing it lets the key activate.

The disabled service

Some tuning tool has set ClipSVC to Disabled. Activation fails until the default startup type is back.