How to Fix the 0xC004C060 Activation Error on Windows and Office

What Does 0xC004C060 Mean?

So. Product key goes in, Activate button gets clicked, and Windows fires back 0xC004C060. The popup says something about “we can’t do this for you right now, try again later.” Cool. Try again later. Like that ever works.

What it boils down to: the activation server on Microsoft’s end got your key, ran it against their database, and marked it “no longer valid.” Their words, not mine. KB article for this error uses that exact phrase. Not much else to go on though, which is the annoying part. At least we know the issue is with the key, not some broken Windows service.

Seen this error on all kinds of machines. Brand new Windows 11 box I set up in February for a buddy’s home office. Office 2021 install on my dad’s laptop. A Retail Win 10 key I bought myself in 2019 that stopped working after I upgraded my mobo to an AM5 board last year. Three totally different situations, same four digits of pain.

Detail	Info
Affected products	Windows 10, Windows 11, Office 2013 through 2024
What it means	Activation server rejected the product key
Can you fix it?	Depends on why (keep reading)
Most common cause	Blocked, revoked, or wrong-edition key

Why Does 0xC004C060 Show Up?

Real quick before you jump to fixes. Figure out which bucket you are in. Otherwise you will burn an hour running the troubleshooter on a key that Microsoft nuked six months ago. Waste of time.

The key is blocked. Most common. Microsoft runs sweeps where they revoke batches of keys that got stolen, resold through shady channels, or leaked from compromised volume license pools. I read a Microsoft Q&A thread last month where a guy bought his Windows 11 Pro key off some discount site in 2023, used it fine for a year, and then one day woke up to 0xC004C060. The whole batch his key came from got flagged retroactively. Nothing he did wrong. But the key was still dead.

Wrong edition. Home key entered into a Pro install. Or the opposite. Or (this one catches people) your laptop has Home baked into the UEFI firmware, you bought a Pro upgrade, and the BIOS keeps shoving the Home key back into the activation system behind your back. Every time you try to activate, the BIOS says “but I have a Home key right here” and the whole thing falls over. Dell, HP, Lenovo machines do this constantly.

Key already used. Retail keys are one-device-at-a-time. If you or someone else put the key on another PC and did not deactivate, that is game over until you remove it from the other machine. OEM keys are worse. They are glued to the original motherboard permanently. No transfer allowed, ever.

Hardware swap. Changed your motherboard? To Microsoft’s servers, that is a whole new computer. Unless your Retail key was linked to a Microsoft account beforehand, the old digital license is gone. Gone gone. And 0xC004C060 shows up when the new hardware does not match what Microsoft has on file.

Microsoft’s servers had a moment. This is uncommon but not zero. Check Downdetector or search Twitter for “Microsoft activation” and see if other people are yelling about it. If yes, make coffee, wait until tomorrow. Not worth burning a Saturday on something that will resolve itself by Monday.

Cheap key from sketchy source. Look. $5 Windows keys on Telegram. $3 Office 2021 Pro Plus from some guy on Reddit. You know the deal. They work until they do not. Microsoft eventually catches these, blocks the whole batch, and the people who paid real money for a fake key end up here reading guides like this.

Check Your License Status Before Fixing 0xC004C060

Do this first. Takes less time than reading this paragraph. Admin CMD (the fastest way on Win 11 is right-clicking Start and picking Terminal (Admin), though on Win 10 builds before 22H2 it is still Command Prompt in the same menu). Then:

slmgr /dlv

A little popup shows up. Read the License Status line. “Licensed” means you are fine, something else is wrong. “Notification” or “Unlicensed” means activation failed. Look at Description too, it tells you Retail, OEM, or Volume. This matters a lot. An OEM key that stopped working after a motherboard swap? That is different from a Retail key from a shady seller. Different fix.

Also run slmgr /xpr. If it says “permanently activated,” the machine was valid at some point. Means 0xC004C060 showed up after the fact, probably due to hardware or server stuff. If it never says that, the key was never valid to begin with.

Side note: ShowKeyPlus on the Microsoft Store is free and way more convenient than slmgr for this. Shows the installed key, pulls the OEM key from your BIOS if one is there, and labels both with the matching Windows edition. I install it on every refurb laptop I touch. Faster than dumping slmgr output and squinting at the fields.

Fix 1: The Activation Troubleshooter

The troubleshooter carries the reputation of doing nothing. Usually deserved. For 0xC004C060 it is actually useful in maybe 40% of cases, based on the machines I have worked on. Mostly the hardware-change scenario.

1. Settings > System > Activation.
2. There should be a Troubleshoot button. If it is not there, your system already thinks it is activated and you are probably reading the wrong guide.
3. Let it do its scan. If it suggests a fix, apply it.
4. Reboot after.

Windows 10 uses a different path: Settings > Update & Security > Activation > Troubleshoot. Same end result though.

Key thing: when the troubleshooter asks “I changed hardware on this device recently,” click it. Then sign into your Microsoft account. Then pick your PC from the list. I have done this three times for motherboard swaps and it worked all three times. First time it even surprised me. Second and third time I just expected it to work. Which, I guess, is progress.

Fix 2: Kick the Software Protection Service

The service called sppsvc runs the whole licensing stack in Windows. When it crashes or gets stuck mid-task, activation silently fails. You type in a perfectly valid key and get 0xC004C060 for no good reason other than sppsvc being dead in the background.

1. Win + R, services.msc, Enter.
2. Scroll down to Software Protection. That is the display name. The internal service name is sppsvc, which you will see in registry paths or if you are looking at Process Explorer.
3. Right-click, hit Properties.
4. Running? Stop it, count to three, Start it again.
5. Stopped? Just click Start.
6. Startup type: Automatic (Delayed Start). Not plain Automatic, not Manual. The delayed start is the right one for this service.

After that, test activation. Settings approach, or just run slmgr /ato in CMD. If sppsvc was wedged, you get a success popup within a few seconds. Nothing happens, next fix.

Fix 3: Wipe the Key and Reinstall It

There is a slim but real chance Windows is holding a mangled copy of your key in the licensing cache. Registry bits get half-written during a botched install or a power loss, and the system reads garbage where your key should be. Nuke and pave fixes it.

1. CMD as admin.
2. slmgr /upk – removes the installed key
3. slmgr /cpky – wipes the key from registry so it does not come back
4. slmgr /ipk YOUR-KEY-HERE – puts your actual key back
5. slmgr /ato – tries to activate

Last command does the real work. Runs online activation against Microsoft’s servers. If it is going to work, you see a success popup within maybe 15 seconds. If it comes back with 0xC004C060 again, the key is just dead. No amount of retrying will bring it back. Jump to Fix 8.

This worked on three different machines I fought with. Took 90 seconds each time. Worth trying before you waste an afternoon on heavier fixes.

Fix 3b: Reinstall the Licensing Cache with /rilc

This one is less known and it saved me once on a machine where the slmgr /upk + /ipk sequence kept failing. The slmgr /rilc command rebuilds the licensing cache files from scratch. Think of it as SFC for the activation system. If the cache itself is corrupted beyond what /upk can fix, this is the hammer that works.

1. Admin CMD.
2. net stop sppsvc (kill the Software Protection service)
3. net start sppsvc (bring it back fresh)
4. cscript.exe slmgr.vbs /rilc (reinstall license files)
5. slmgr.vbs /rearm (reset activation state)
6. Reboot the machine. Twice actually – first reboot applies the rearm, second one lets the licensing layer settle.
7. After the second reboot, run slmgr /ato again.

Heads up on /rearm: Windows only lets you run this a limited number of times before it refuses. Usually three. Not something to run casually, but for 0xC004C060 where other stuff already failed, one rearm is fine.

This sequence is what Microsoft’s own support pages recommend for deep activation cache corruption. I have seen it work where nothing else did, and also watched it fail spectacularly on a blocked key (which just told me the key was the problem, not the cache).

Fix 4: Run SFC and DISM

Long shot but cheap to try. Corrupted system files can mess with activation in ways that do not show up anywhere else. 15 minutes of your time to rule it out.

1. CMD as admin.
2. DISM /Online /Cleanup-Image /RestoreHealth – grab a coffee, this one takes a while
3. sfc /scannow
4. Reboot. Try activating again.

On its own this will probably not fix 0xC004C060. But it clears out junk that might be interfering. On a client’s laptop last year I chased the activation error for two hours before SFC found a corrupted servicing file, fixed it, and activation went through on the next try. Would never have guessed that was the issue.

Fix 5: Update, Then Activate

Old build of Windows 11? Outdated Office? Update before you do anything else. Microsoft slips activation bug fixes into cumulative updates, and I have watched 0xC004C060 vanish purely from installing a pending KB. No commands, no tricks. Just an update.

Windows side: Settings > Windows Update > Check for updates. Grab everything, optional updates too. Reboot.

Office side: launch Word, hit File > Account > Update Options > Update Now. Grayed out? Your Office is managed by a domain or corporate policy and you need IT to push the update for you.

One thing that catches people. Under Windows Update > Advanced options, there is a toggle for “Receive updates for other Microsoft products.” Needs to be on. Otherwise Office updates never come down through Windows Update and you are stuck on whatever build you installed originally.

Fix 6: Phone Activation (slui 4)

Old trick. Still works. I have cleared 0xC004C060 with phone activation on machines where literally nothing else worked. No joke.

1. CMD as admin.
2. slui 4 and Enter.
3. Pick your country.
4. Toll-free number shows up. Dial it.
5. Automated system asks you to read like 63 digits (the Installation ID). It reads them back in groups so you can catch mistakes. Patience required.
6. System gives you a Confirmation ID. Type it into the boxes on screen.
7. Hit Activate.

Robot cannot do it? Stay on the line, it forwards you to a real human. Tell the agent you hit 0xC004C060 during activation. Have your receipt email open on a second monitor or your phone. When the key is a real Retail key and you can prove purchase, they manually force the activation from their end. Total time for my last call in January was 18 minutes, most of which was hold music.

One catch. Phone activation only works for Windows. Office needs a different path (see Fix 7).

Fix 7: Microsoft Support and Recovery Assistant (Office Only)

Microsoft distributes a free diagnostic utility called Support and Recovery Assistant, or SaRA to people who have used it more than once. Pulls directly from microsoft.com. What it does: sanity-checks your Office install, pokes the license cache, repairs corrupted components, kicks activation again. Pretty set-and-forget.

1. Grab SaRA from the Microsoft download page.
2. Launch it. Select “Office” when it asks, then the activation-related issue from the list.
3. Go make a sandwich. The scan + fix cycle takes roughly 10 minutes.

Client had Office 2021 Pro Plus throwing 0xC004C060 repeatedly. Online Repair did jack. SaRA found a cached license file at %LocalAppData%\Microsoft\Office\Licenses that had gone corrupt, cleared it, and activation went through. Would not have found that manually.

Video Walkthrough: Fixing 0xC004C060 on Office

If you prefer watching over reading, this short tutorial from Baraka enstore runs through the Office-side fix in under 4 minutes. Covers the same Online Repair and key re-entry steps I described above, so it’s a solid visual supplement.

Fix 8: Get a New Key

If you have tried everything above, the key is dead. Really dead. 0xC004C060 is not going anywhere. Options depending on where you got it:

Third-party seller? Email them the error code, ask for replacement or refund. Legit sellers replace within 24 hours. If they ghost you, stall, or get defensive – that key was bad from day one. Which is information you did not want, but now you have it.

Microsoft or authorized retailer? Microsoft support can actually pull up your key’s status in their system and reactivate it manually. Phone activation with a live agent (see Fix 6) is usually the fastest path. They can even issue you a new key if the old one got batch-blocked through no fault of yours.

Need to start over? Get a Retail key, not OEM. Retail keys transfer between computers. OEM keys are hardware-locked forever. Windows license keys and Office license keys with a replacement guarantee are worth the extra few bucks. Means if your key ever gets batch-blocked down the road, you get a working one back at no cost.

The Home-to-Pro Disaster That Triggers 0xC004C060

This one keeps happening. Every couple weeks someone emails me about it. Here is the scenario.

You bought a laptop. Home edition pre-installed. OEM Home key sitting in the UEFI firmware. You want Pro features (Remote Desktop, BitLocker, group policy editor, whatever). You buy a Pro upgrade key, punch it in through Settings. Windows says “upgrading to Pro.” Reboot. Then boom – 0xC004C060, activation failed.

What is happening behind the scenes: the BIOS is still broadcasting the original Home key to the activation system. Your Pro key gets entered, the activation process starts, the BIOS says “hold on, I have a Home key here,” and the whole thing conflicts and fails.

Fix:

1. CMD as admin.
2. slmgr /upk – yanks out whatever key is currently installed
3. slmgr /cpky – wipes it from the registry so the BIOS key does not instantly reload
4. slmgr /ipk YOUR-PRO-KEY – put in your actual purchased Pro key
5. slmgr /ato – try to activate
6. Reboot.

Still not working? There is a two-step move I have used on stubborn Dell and HP machines. First, install Microsoft’s generic Pro key to force the edition switch cleanly:

slmgr /ipk VK7JG-NPHTM-C97JM-9MPGT-3V66T

That string is the official generic KMS key for Windows 10 and Windows 11 Pro. Microsoft publishes it in their own deployment docs for IT admins doing mass installs. Running it will not activate your machine (it is just a placeholder), but it forces the Windows licensing layer to commit to Pro as the installed edition. Reboot once that completes. Then drop in your real Pro key through slmgr /ipk followed by slmgr /ato. Ugly workflow, but I have used it on a handful of Latitude 5550s and ProBook 450s where the direct approach kept bouncing back to Home.

Fixing 0xC004C060 on Microsoft Office

Office licensing is handled by its own subsystem, not sppsvc. So slmgr commands will not do much for Office activation issues. Different tools apply.

Online Repair. Head to Control Panel > Programs and Features, find Microsoft Office in the list, click Change, pick Online Repair (not Quick Repair – Quick just resets shortcuts and registry entries, it does not redownload anything). Online Repair tears down the install and rebuilds it from Microsoft’s CDN. Roughly 20 minutes depending on connection speed. Takes care of corrupted licensing files most of the time.

Re-enter the key from inside Office. Fire up Word. File > Account. There should be a “Change Product Key” link near your subscription info. Click it, enter your 25-character key. Cache gets refreshed, activation reattempts. Low-effort first step.

OSPP script. Way more detail than what the Settings UI shows. Admin CMD, then cd into the Office folder. For most 64-bit installs that is C:\Program Files\Microsoft Office\Office16. Some 32-bit Office installs sit under Program Files (x86) even on 64-bit Windows, so check both if the first path does not exist. Then:

cscript ospp.vbs /act

If activation works, you get a success message. If it fails, you get a detailed reason code, which is way more useful than what the Settings page spits out. The Settings page just says “something went wrong.” The OSPP script tells you exactly what.

Also. If you upgraded from Windows 10 to 11 and then Office stopped activating – yeah, that can trigger 0xC004C060 on Office even though Office did not change. The Win11 upgrade messes with registry keys and license cache in ways Microsoft’s servers interpret as “this is a new device.” SaRA fixes it fast. Online Repair usually too.

Every slmgr Command You Might Need

I never remember these by heart. /cpky vs /upk – which one clears the registry again? Every time. So I just keep this table handy.

Command	What It Does
slmgr /dlv	Detailed license info: type, status, activation ID
slmgr /dli	Basic license info: edition, license status
slmgr /xpr	Expiration check (or “permanently activated”)
slmgr /upk	Uninstalls the current product key
slmgr /cpky	Clears key from registry (prevents BIOS reload)
slmgr /ipk [KEY]	Installs a new product key
slmgr /ato	Triggers online activation attempt
slmgr /rilc	Reinstalls the licensing cache files (deep fix)
slmgr /rearm	Resets activation timer (limited uses)
slui 4	Opens phone activation wizard

Admin CMD only. Regular CMD does not have the perms to mess with activation. PowerShell mostly works too. Except slmgr /dlv sometimes eats its own popup in PowerShell for reasons I gave up figuring out. Just use CMD for this stuff.

Related Activation Error Codes

Heads up. Sometimes running the troubleshooter on 0xC004C060 changes the error code mid-fix. You start with 0xC004C060, apply a fix, and now Windows shows a different error. That is actually good. Different codes mean different root causes, which narrows things down.

Error Code	What It Means	How It Differs
0xC004C003	Key blocked by activation server	Same root cause, different internal flag
0xC004F210	Key does not match installed edition	Match the key to the right edition
0x803FABB8	Activation servers unavailable	Temporary. Wait a few hours
0x8007267C	DNS resolution failed	Internet connection problem
0xC004C770	Key deactivated by Microsoft	Same outcome, same fix as our error
0xC004F074	KMS host unreachable	Only Volume/KMS, not Retail

What Happens If You Just Do Not Activate?

Windows keeps working. Apps run. Games launch. Security patches still come through. You just end up with a permanent “Activate Windows” watermark stuck in the bottom right and the personalization settings locked (no wallpaper changes, no accent colors, no lock screen tweaks). Annoying? Obviously. Dealbreaker? Depends on how much you care.

Office is stricter. After the grace period expires (usually 30 days), unactivated Office drops into read-only mode. You can open docs but you cannot edit or save. For a home user that is survivable. For work? Hard no. You need this fixed.

How to Avoid This Activation Error in the Future

• Buy from Microsoft or a seller that guarantees replacements. If the price looks too much ($5 for Win 11 Pro, come on), the key is going to die eventually.
• Save your receipt. Save the email with your key. If Microsoft ever batch-blocks that key two years from now, proof of purchase is your ticket to a refund or replacement.
• Link your Retail license to a Microsoft account the moment you activate. Settings > Activation > Add a Microsoft account. Makes future hardware swaps painless.
• Right after first activation, run slmgr /dlv. Check that the description says Retail if you bought a Retail key. Not OEM. Not Volume. Retail. If it does not match, the seller sold you the wrong type and you need to raise that now before they disappear.
• Just need to install Windows on a test VM or a machine you will license later? Use generic installation keys. Microsoft publishes them in their own docs for exactly this purpose. They let you install any edition, then you activate properly later.

Frequently Asked Questions

What does error code 0xC004C060 mean?

Error 0xC004C060 means your Windows or Office product key has been flagged as invalid by Microsoft’s activation servers. The key may be blocked, revoked, already used on another device, or purchased from an unauthorized source.

Can I fix 0xC004C060 without buying a new key?

Sometimes yes. If the error is caused by a temporary server glitch, edition mismatch, or a stopped service, running the activation troubleshooter or restarting the Software Protection service can fix it. But if Microsoft has permanently blocked the key, no troubleshooting will help and you need a replacement.

Does this error affect both Windows and Office?

Yes. This activation error can appear when activating Windows 10, Windows 11, or Microsoft Office versions including Office 2013, 2016, 2019, 2021, and 2024. The underlying cause is the same: the activation server rejects the product key.

How do I check if my Windows license is OEM, Retail, or Volume?

Open Command Prompt as administrator and run slmgr /dlv. This displays your license type (Retail, OEM, or Volume), activation status, and remaining rearm count. You can also install the free ShowKeyPlus app from the Microsoft Store for a simpler view.

Why did my legitimate key get blocked?

Microsoft sometimes blocks entire key batches when they detect unauthorized distribution patterns. Even if your individual purchase was legitimate, the batch your key came from may have been flagged due to other keys in the same batch being misused. Contact your seller for a replacement or refund.

Will reinstalling Windows fix this activation error?

No. Reinstalling Windows does not fix this error because the problem is with the product key, not with Windows itself. The same blocked key will fail activation again after reinstallation. You need either a different valid key or help from Microsoft support.

Last updated: April 2026