0xC004C008 Activation Error: How to Fix It on Windows 10, 11 and Server

New motherboard in, Windows boots, and the watermark of a 0xC004C008 activation error sits in the corner. Settings shows a code where “activated” used to be. The 0xC004C008 activation error says one thing: Microsoft’s server has counted this key on too many devices.

In a hurry? Open the phone activation dialog, call the number and type in the ID you hear back. Most people finish in about five minutes.

slui 4

Didn’t work, or you’d like to know why the code shows up at all? The rest of this page breaks it down.

What the 0xC004C008 activation error code means

On screen you get Microsoft’s official wording: “The activation server determined that the specified product key could not be used.” Not particularly informative.

Microsoft’s list of Windows activation errors explains it further. The key is already used on another device. Or on more devices than the license terms permit.

Microsoft’s advice comes in two parts. A separate key per device. Or phone activation after a significant hardware change.

In plain words, Microsoft thinks you’ve used your key on too many computers. That could be true. It could be a false positive from a hardware change. Or somebody else used the same key before it got to you.

The reason doesn’t change the symptom. The request goes to Microsoft, Microsoft says no, and you’re stuck with the watermark.

At system level the error carries this name:

SL_E_CHPA_MAXIMUM_UNLOCK_EXCEEDED

CHPA stands for “Clearing House Product Activation”. That clearing house is the database where Microsoft keeps the count.

A lot of people assume this code calls for a new key. In most cases that’s not true. The usual fix is getting Microsoft’s counter reset for your device.

What causes the 0xC004C008 activation error

Microsoft keeps a counter on the server side. Every time Windows tries to activate with a given key, it calls home. The counter ticks up.

Go past the number your license permits, and every later attempt fails with this code. The mechanism itself is pretty basic.

What’s interesting is how people bump into the limit. It usually isn’t piracy.

Motherboard swap, the most common trigger

By far the most common reason people land on this page. In support requests, a fresh board swap comes up more often than any other cause.

It comes down to how Windows builds its hardware fingerprint. That hash leans heavily on the motherboard: the model, the serial, the BIOS UUID. Swap the board, and the whole hash shifts.

Microsoft’s side doesn’t know your drive and key are the same. To the server it looks like the license is trying to activate on a brand new PC.

Other hardware barely matters. A new CPU, more RAM, a move from a SATA SSD to NVMe, a new graphics card. Windows won’t care, and activation complaints after those are rare.

Change the board, though, even to a very similar one. You’ll be staring at this error within minutes of booting into the “new” system.

The key is still active on another PC

Retail and OEM keys are single-device licenses. Say the old PC got wiped or sold with the key still installed. Microsoft’s database still shows the key assigned to that machine.

When you activate on the new build, the server flags the key as already in use. OEM is worse. Those keys don’t transfer between motherboards at all, legally speaking.

The command that removes a key from the old PC is this one. Run it there, before the wipe:

slmgr /upk

A cheap gray market key

Seven-dollar keys on sketchy sites, random Telegram sellers, that one Reddit DM. Almost always stolen volume license keys, or keys from regions they were never meant to leave.

They activate at first. Then Microsoft notices a batch being used hundreds of times and wipes the whole lot. A key that was fine last week and fails today? That’s probably what happened.

MAK or KMS hit the cap

IT admin territory, mostly. Microsoft documents that a KMS host key can be activated up to 10 times, on no more than six different computers. Past that, you request more.

MAK keys have a fixed activation count baked into the licensing agreement. Blow past the cap, and every activation after that fails. Sometimes with this code, sometimes with 0xC004C020, its MAK-specific cousin.

To get the limit raised, you contact the Microsoft Licensing Activation Center.

Cloned VMs

A bunch of VMs spun up from a single golden image, all expecting the same retail key to work. Each clone registers as its own machine. One VM activates, the rest start failing.

For any kind of VM scale, we’d use AVMA or KMS. Retail keys are the wrong tool for that job.

The same list as a quick lookup. Cause on the left, the matching fix on the right.

How to fix the 0xC004C008 activation error

First confirm which key is installed and what license type it is. Then pick the matching route. Here’s the short version.

1. Open Settings, System, Activation on Windows 11. On Windows 10 it’s Settings, Update & Security, Activation. Note the edition and the exact error.
2. In an admin Terminal, display the license information. Compare the partial key with yours and read the channel.
3. For a changed motherboard with a license linked to your Microsoft account, select Troubleshoot. Choose “I changed hardware on this device recently” and sign in. Tick “This is the device I’m using right now”, then select Activate.
4. Retail key, now used only on this PC? Open the phone activation dialog. Call the number shown, enter the Installation ID and type in the Confirmation ID you hear back.
5. If the dialog doesn’t open or shows no Installation ID, restart the Software Protection service and run a system file check. Then try again.
6. Still refused on the phone? Contact Microsoft support with your key and proof of purchase. Or the seller who supplied the key.
7. For a volume license on a server or company PC, request more activations from the Microsoft Licensing Activation Center. A MAK can also be activated by phone.
8. If the key is really in use on another PC you still run, buy a separate key for this one. Enter it with Change product key.

The commands behind steps 2, 4, 5 and 7:

Each of these routes gets its own section below, with the details that trip people up.

Fix 1: phone activation, step by step

Of everything on this page, this is the method that matters most. For retail keys it’s more reliable than the troubleshooter or any slmgr trick.

The reason is simple. You’re dealing with Microsoft’s clearing house directly. Not with the automated web services. The clearing house has the authority to override activation counters on the spot.

With a genuine key it typically takes 5 to 15 minutes. That depends on how busy the phone line is in your country. In most cases it works on the first call. A second call sorts out most of the rest.

Before you dial

• The full 25-character key, on paper or in a text file.
• The activation window open, with the Installation ID visible.
• Notepad open for the Confirmation ID.
• A phone with a keypad you can reach during the call.
• The honest answer to “how many PCs”.
• Proof of purchase nearby, in case an agent asks.

The call

1. Press Win + R to open the Run dialog.
2. Type the command below into the box and press Enter. A phone activation window opens.
3. Pick the country you’re physically in right now, not the one where you bought the license. Click Next.
4. The next screen shows a toll-free number and, below it, your Installation ID. Keep this window open. You’ll read from it while on the phone.
5. Dial the number. An automated system picks up almost instantly, with no hold music.
6. When prompted, use the phone keypad to enter each of the 9 blocks of the Installation ID. The robot reads each block back to confirm.
7. At some point the system asks how many PCs this license is installed on. Key only on this PC now? The answer is “1”. Any higher number gets the call rejected or routed to an agent.
8. The robot then reads out a Confirmation ID, 48 digits in a steady stream. Don’t try to memorize it. Have a notepad ready.
9. Type the Confirmation ID into the activation dialog and click Activate. Windows shows the success screen within a second or two.

slui 4

A common slip on that question: counting a reinstall of the same PC as a second machine. It’s still one PC.

When the robot hands you to a person

Occasionally the automated system decides your case is too unusual and routes you to a real human. Don’t hang up.

Be brief with the agent. You got 0xC004C008, and here’s why: new motherboard, reinstall, hardware failure. Real agents have extra tools to reset activation counts by hand.

It’s not the usual path. It’s not rare either, and we’d plan a few extra minutes for it.

When the dialog doesn’t open at all

Try it through an admin command prompt. Right-click the Start button and pick the Terminal or Command Prompt entry marked Admin. Type the same command there and press Enter.

The Run-box route has a reputation for hanging on random machines. The command line tends to work when it doesn’t.

One more thing to verify: the Software Protection service has to be running. Press Win + R and open the services console. Scroll to “Software Protection”, internal name sppsvc.

services.msc

If the Status column says anything other than “Running”, right-click the entry and pick Start.

Mistakes on the call

• Picking the country of purchase. Pick the country you’re in.
• Counting a reinstall as a second PC.
• Trying to memorize the Confirmation ID.
• Closing the dialog during the call. The Installation ID has to stay on screen.
• Hanging up when an agent comes on the line.

Type the Confirmation ID into Notepad while the robot reads it. Then copy it block by block into the activation window. One wrong digit, and you call again.

When the phone dialog fails

Sometimes the dialog refuses to cooperate. It opens a blank window with no Installation ID. It hangs forever on “contacting the activation server”. Or it crashes immediately.

That usually points to a corrupted licensing store or a dead Software Protection service. The fixes below go from fastest to most invasive.

Restart the Software Protection service

Software Protection, sppsvc, manages everything licensing-related. When it’s hung or dead, nothing activation-wise works, the phone dialog included. A restart is the smallest possible intervention, and sometimes it’s all you need.

From an admin command prompt:

net stop sppsvc
net start sppsvc

Both lines should finish in under 5 seconds. Wait 10 seconds for the service to settle, then try the phone dialog again.

A typical case: the service crashes silently after a cumulative update. Everything else looks normal. Only the activation side is broken.

Repair system files with SFC and DISM

If the restart didn’t do it, check whether system files got corrupted along the way. A failed update can do that. So can a malware cleanup gone wrong, or plain file system corruption.

sfc /scannow

That takes roughly 5 to 15 minutes, depending on how much it finds. If SFC repairs something, reboot and retry the phone dialog.

If SFC reports corruption it couldn’t fix, run this next:

DISM /Online /Cleanup-Image /RestoreHealth

DISM takes longer, sometimes 20 minutes or more. It pulls clean copies of system files from Windows Update. Once it finishes, reboot once more and try activation again.

Rebuild the licensing store, tokens.dat

The nuclear option, if the previous two didn’t help. Windows keeps its local licensing state in a file named tokens.dat. The folder is in the listing below.

When the cached data in there gets corrupted, Windows can’t generate a valid Installation ID. So the phone dialog has nothing to show you.

Microsoft documents a rebuild for exactly this case, in the original KB 2736303. Rename the file, let Windows reinstall its license files, restart twice.

1. Open Command Prompt as administrator and stop the Software Protection service.
2. Go to the store folder.
3. Rename the file.
4. Start the service again.
5. Reinstall the system license files.
6. Restart the computer twice. Then install your key again and try online or phone activation.

net stop sppsvc
cd %windir%\System32\spp\store\2.0
ren tokens.dat tokens.bar
net start sppsvc
cscript.exe %windir%\System32\slmgr.vbs /rilc

After the two restarts:

slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato

The file is renamed, not deleted, so the original state is still there as tokens.bar. If something goes sideways, stop the service and rename it back. You’re where you started.

It can rescue machines where nothing else worked. Worth trying before you give up.

One warning from the same Microsoft article. Install the key over the old one, as in the listing. Never uninstall the key first as part of this repair.

Microsoft’s online activation page

In some countries the phone line now sends you to a web page, aka.ms/aoh, and reads out no Confirmation ID. Worth trying when the call itself goes nowhere.

Open that address in any browser, sign in with a Microsoft account and follow the prompts. Not every license type is supported there. It takes 30 seconds to try. Better than sitting on hold.

Fix 2: the Activation troubleshooter

This one only works with a digital license tied to a Microsoft account. In that case it clears the error in a few clicks. No phone calls.

It works best when you changed hardware on the same PC. And when the Microsoft account is the one that activated the license originally.

On Windows 11:

1. Open Settings with Win + I.
2. Go to System, then Activation.
3. Click the Troubleshoot button.
4. When the troubleshooter finds the problem, click “I changed hardware on this device recently”.
5. Sign in with the Microsoft account your Windows license is attached to.
6. A list of devices linked to the account shows up. Pick the current PC and click Activate.

On Windows 10:

1. Open Settings with Win + I.
2. Go to Update & Security, then Activation.
3. Click Troubleshoot and walk through the prompts.

New PCs with Windows preinstalled

One more case where we’d run the troubleshooter first. A brand-new box from Dell or HP, Windows preinstalled, and an activation error anyway. Lenovo machines do it too.

On those PCs the key sits in the firmware, under OEM Activation 3.0. The troubleshooter checks it again against the installed edition.

PC makers’ support pages commonly suggest a couple of reboots and the troubleshooter as the first step. On a recent OEM laptop, we’d try this before phone activation.

The troubleshooter only appears while Windows isn’t activated. Don’t go looking for it on a working PC.

Fix 3: re-entering the product key with slmgr

Local licensing data occasionally goes stale, in ways that don’t show up as any specific error. Putting the key back in sometimes clears the weird state. More switches? Slmgr commands.

It also tells you whether the block is really on the server side. Run these one at a time in an admin Command Prompt:

slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato
slmgr /cpky

Older guides start by removing the key first. Skip that on the PC you’re fixing. Microsoft’s own licensing documentation says to install a key over an existing one, and never to uninstall it for that.

Keep the uninstall command for the old PC you’re retiring.

Online activation throws the same code again after all of this? Then the issue is server-side, not local. No local fix will help at that point, and we’d move on to phone activation or to support.

A useful check while you’re in slmgr

slmgr /dlv

That prints the detailed license information. Look at the “License Status” line near the bottom, and at the partial key, the last 5 characters.

Status “Notification” or “Unlicensed”, with a partial key that matches yours? Then the correct key is installed, and Microsoft’s server won’t approve it.

That distinction matters. It rules out typos and wrong-key scenarios before you start calling support.

Fix 4: Microsoft support

Phone activation failed, the troubleshooter can’t fix it, and slmgr isn’t helping. Time to bring in a Microsoft support rep.

They have backend access to the activation database and can see your key’s full activation history. A manual reset of the count? Support handles that. Same if the key got compromised and needs a replacement.

Three ways to reach them:

• The Get Help app. Type “Get Help” into Start search and pick the Activation category. Describe the issue, and it routes you to chat or phone.
• The support.microsoft.com/contactus page. Pick Windows, then Activation. Request a callback or open a live chat.
• For volume licensing, the Microsoft Licensing Activation Center for your region. Or manage the agreement in the Microsoft 365 admin center, which replaced the old VLSC portal.

Have the product key handy before you reach out. Proof of purchase too, if you can dig it up: the order confirmation email, a reseller receipt, anything timestamped.

The conversation itself usually takes 10 to 15 minutes. Typically the rep resets the activation counter on their side. After that, online activation goes through without complaint.

If the key came from us

Your key came from HypestKey and shows this code? Contact us before you spend an afternoon on hold.

Email support@hypestkey.com or use the live chat. Send the error code and the steps you already tried. If a key doesn’t activate, we help you fix it or send a replacement.

Bought the key somewhere else? Ask anyway. We’ll tell you honestly which of three things applies.

• You can fix it yourself by phone.
• Microsoft support needs to reset the count.
• The key is blocked and can’t be saved.

What to send us

• The exact code from Settings.
• The Windows edition and version.
• What changed before the error: new board, reinstall, new PC.
• Which fixes you tried, and what each one answered.
• Your order number. Not the full key in a screenshot.

Checking the status before and after each fix

Check the status before you start, and again after each attempt. Two ways, pick whichever feels less painful.

Through Settings. On Windows 11 go to System, then Activation. On Windows 10 it’s Update & Security, then Activation. You’ll see either “Windows is activated with a digital license” or the specific error with a few buttons.

Through the command line. Open an admin prompt and use slmgr with one of these switches:

slmgr /dli
slmgr /dlv
slmgr /xpr

The field to watch is “License Status” in the detailed output.

Where the setting lives in Windows 11 24H2 and 25H2

Click the little arrow next to “Activation state” to expand it. Current status, Change product key and the troubleshooter are all in there.

A lot of older guides still send you to the Update & Security path. That’s only right on Windows 10.

One known quirk on 24H2: the troubleshooter sometimes takes longer to connect. Stuck on “Diagnosing your PC” past 2 minutes? Don’t kill it. It eventually comes back, just slow.

When the troubleshooter can’t handle it, open the Get Help app and pick the activation topic. Paste the exact error code. It saves explaining everything to a support bot from scratch.

Which fix to try first

Start with your situation, not with a random fix.

After a motherboard swap

Try the troubleshooter first. With a license linked to a Microsoft account, you can be activated in under 30 seconds. No luck there? Move to phone activation.

After a reinstall on the same hardware

Run online activation from an admin prompt. If it returns the same code, jump directly to phone activation.

A reinstall on the same hardware with the same key shouldn’t normally trigger this error. When it does, phone activation sorts it out.

With a key from a non-Microsoft retailer

Phone activation is the first move. If the call rejects the key, ask the seller for a replacement.

They ghost you or refuse? The key almost certainly came from a gray market source. You’ll need a new one from a trusted channel.

For IT admins at a KMS or MAK limit

Skip the consumer fixes entirely. Call your region’s Microsoft Licensing Activation Center and request more activations. Have your VL Agreement number ready.

0xC004C008 versus 0xC004C060: which activation error is which

A classic mixup. The two codes read identically at first glance. Both start with 0xC004C, and both show up in the same dialogs.

They mean completely different things, though. Confusing them can waste hours on fixes that have no chance of working.

Once Microsoft blocks a key, it stays blocked. No amount of phone calls brings it back.

The fastest way to confirm which one you have is the detailed license view. Look at the “Notification Reason” field.

slmgr /dlv

We’d check this before committing an hour to a phone call that can’t work. The blocked-key case has its own walkthrough in our 0xC004C060 activation error guide.

Related codes that look like the 0xC004C008 activation error

Several codes look like this one and point to different problems. Match the exact code before choosing a fix.

A different code calls for a different fix. Only the MAK code in the last row tells basically the same story: the cap was hit.

Microsoft’s own activation error code reference lists both, with the KMS limit. For every other common code, we keep the full list in the Windows 11 activation errors overview.

The 0xC004C008 activation error on Windows Server

Servers get hit with this too. It hurts more there, because server downtime costs actual money.

The root cause is the same: the key ran out of activations. On a server that’s almost always a KMS host key. Microsoft permits up to 10 activations on no more than six computers.

MAK keys over their limit show 0xC004C020 instead. Both get fixed the same way: the Microsoft Licensing Activation Center adds activations.

MAK keys

Grab the Installation ID with the first line. Then call the Licensing Activation Center for your region. They give you a Confirmation ID, and you enter it with the second line.

slmgr /dti
slmgr /atp <ConfirmationID>

Admins report that weekend calls can take more than one attempt to get through.

KMS host keys

For a KMS host key past the limit, the Licensing Activation Center can add activations. The detailed license view shows the current activation count.

We walk through the full server process in our guide to Windows Server 2022 activation.

Why the license type matters

The license type decides why you hit this code and how you recover.

The channel shows up in the license information: RETAIL, OEM, VOLUME_MAK or VOLUME_KMS.

OEM is the trickiest. The board died and got replaced? That OEM key is basically dead too. Microsoft sometimes makes an exception through phone activation, and sometimes doesn’t.

Retail is the most flexible. Move it between PCs as often as you like. Just remove the key from the old one before you wipe it.

Need a fresh key? A genuine one from a trusted reseller is the safer path.

Moving a retail key to a new PC the clean way

1. On the old PC, sign in with a Microsoft account and check that Windows shows as activated.
2. Write down the key, or find the purchase email.
3. Uninstall the key on the old PC, with the command from the section on causes.
4. Wipe or retire the old PC.
5. Install Windows on the new PC and enter the key.
6. If the code appears anyway, go to phone activation and answer “1”.

The order matters. Removing the key first follows the license terms: one device at a time.

When none of the fixes work

Phone activation, the troubleshooter, slmgr and Microsoft support have all failed. Then the cause is almost always one of three things. None of them can be fixed locally.

The key is dead

It came from a sketchy seller, and Microsoft revoked it. No amount of troubleshooting brings a blocked key back. A new one is the only way forward.

An OEM key on different hardware

OEM dies with the original motherboard. The board is gone, so the key is gone. Microsoft support might grant an exception if you explain what happened. No promises.

The key doesn’t match the edition

A Home key on a Pro install fails. Check in the detailed license view that the partial key matches what you entered. Then confirm the edition.

In any of those three cases, the practical move is a new key. Straight from Microsoft, through Settings, System, Activation, Go to Microsoft Store. Or from a trusted reseller with genuine keys.

Need a genuine key? Windows 11 Pro, with instant email delivery.

If you leave it unfixed

Windows keeps running and still installs security updates. It just stays unactivated.

The watermark is the first thing you’ll see. It sits on top of games. It shows up during video calls and screen sharing at work. Kind of embarrassing.

Personalization gets locked. One workaround still works outside Settings: right-click an image and choose “Set as desktop background”. The whole thing feels locked down anyway.

Microsoft went with the nag approach. Nothing actually breaks.

Running unactivated long-term does technically break the license terms. For personal use, nobody from Microsoft is knocking on your door. For business use, a software audit could bite. Easier to activate the thing and move on.

Preventing it next time

Four habits avoid the error in most cases.

Link the license to a Microsoft account

Do it before you touch any hardware. It’s the single best thing you can do. It takes 30 seconds and makes a later reactivation painless.

Remove the key from the old PC

Do it before you format or sell the machine. One command on the old PC frees the slot:

slmgr /upk

Keep the key where you can find it

Save the purchase email. Screenshot it, or write the key down. On the phone with Microsoft, having all 25 characters ready speeds things up a lot.

For VMs, use AVMA or KMS

Not individual retail keys. One retail key per cloned VM is begging for this error, especially in anything clustered or lab-like.

Before a hardware upgrade: a short checklist

• Sign in with a Microsoft account and open the Activation page.
• Look for the line that says the digital license is linked to the account.
• Note the edition, Home or Pro.
• Find the key or the purchase email.
• Back up anything on the system drive you can’t lose.
• After the swap, give Windows an internet connection before judging the result.

A quick word on Office

Microsoft Office has its own activation errors, and some look almost identical. Code 0xC004F074 shows up on both products. That goes for Office 2019 and 2021. Office 2024 too.

Unactivated Office drops into reduced functionality mode after about 30 days. Files still open, but editing and saving stop. At work that kills productivity, so we’d activate both Windows and Office on any new setup.

Two last notes. The “Activate Windows” watermark has its own story. And Microsoft’s generic installation keys are for installation only, not for permanent activation.

Myths about the 0xC004C008 activation error

• “A reinstall clears it.” It doesn’t. The counter lives on Microsoft’s servers, and a fresh install asks the same server.
• “You always need a new key.” In most cases you don’t. The count gets reset, and the same key activates.
• “It proves the key is pirated.” Usually it’s a hardware change or a moved license.
• “A new graphics card can trigger it.” As a rule, it doesn’t. The motherboard is what counts.
• “The phone line costs money.” The dialog shows a toll-free number for your country.
• “Generic installation keys fix it.” Those are for installation only. They never activate anything permanently.
• “One fix works for every code that starts the same way.” It doesn’t, and the comparison above shows why.

Terms used on this page

Typical 0xC004C008 activation error cases

The new board, the old drive

Same Windows install, same NVMe drive, same key. Only the motherboard is new. The server refuses the key anyway, and one phone call later Windows is activated.

The reinstall that changed nothing

Someone wipes the drive, installs Windows fresh and enters the same key. The same code is back before the desktop has settled. Half a day gone. The phone call that follows takes ten minutes.

The key that worked last week

A very cheap key from a marketplace activates fine at first. A week later the code appears, and the phone system refuses the key too. The seller doesn’t answer. A genuine key ends the story.

The lab full of clones

A row of virtual machines from one golden image, one retail key. The first VM activates, and the others fail one by one. KMS for the lab solves it.

The answer that wasn’t “1”

On the call, the robot asks how many PCs carry the license. The caller counts the old install on the same machine and says two. The call gets routed to an agent. Next time the answer is one, and it goes through.

Where these steps apply

Menu paths differ slightly between Windows 10 and Windows 11, as noted in each step. The slmgr and SLUI commands are the same everywhere.