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

With the 0xC004C060 activation error, Microsoft’s activation server turned the product key down. We quote it: “You entered a product key that can’t be used to activate Windows.” It appears on Windows and on Office alike. Sometimes the key is fine and the PC changed.

Sometimes the key is finished. We start with the license check, then follow the fix that matches.

1. Check the license: the slmgr license report shows the channel and the last characters of the key.
2. Hardware changed? Run the activation troubleshooter and pick the hardware-change option.
3. Key in the wrong edition? Match the key to the installed edition.
4. Key used up or blocked? Contact the seller with the error code.
5. Office? Change the key under File, Account.

Behind that message sits one simple event. The activation server received your key and checked it against its database. Then it marked the key as one that can’t activate this copy.

The knowledge base article for this code calls such a key “no longer valid”. Their words. It doesn’t say why, and that’s the annoying part.

One thing is settled, though. The trouble is with the key, or with how Windows presents it. It isn’t a broken Windows service by default.

This code turns up on all kinds of machines. A brand-new Windows 11 box. An Office install on an older laptop. A desktop that got a new motherboard. Different stories, same message.

Before you start: a short checklist

• An internet connection that works. Activation is online.
• The email with your key, open in another window.
• An administrator account on the PC.
• The edition you installed. It’s under Settings, System, About.
• Time for a reboot or two.

The paths differ a little between the two Windows generations. This table saves some hunting.

Why the 0xC004C060 activation error shows up

Six causes cover nearly every case you’re likely to meet. Find yours first, because the fix depends on it. Otherwise you spend an hour on the troubleshooter with a key that was dead before you started.

The key is blocked

The most common one. Microsoft runs sweeps and revokes whole batches of keys. Stolen ones, keys resold through shady channels, keys leaked from volume license pools.

A blocked key can work for a long time first. People activate, use the PC for a year, and then wake up to this code. The batch got flagged after the fact. They did nothing wrong, and the key is dead anyway.

The key is for another edition

A Home key typed into a Pro install. Or the other way round. The server won’t match them.

There’s a sneakier version on laptops. Home sits in the UEFI firmware from the factory. You buy a Pro upgrade, and the firmware keeps handing its Home key back to the activation system. Plenty of factory laptops ship exactly like that.

The key is already in use

Retail keys work on one device at a time. Still active on another PC? Then it won’t activate here until it’s removed there.

OEM keys are stricter. They stay with the original motherboard for good. No transfer, ever.

The hardware changed

A new motherboard looks like a new computer to Microsoft’s servers. The old digital license doesn’t follow by itself. A Retail license linked to a Microsoft account can be moved. One that was never linked is much harder to rescue.

Microsoft’s servers are having a moment

Uncommon, but it happens. Check Downdetector, or search social media for “Microsoft activation”. Lots of people complaining at once? Make coffee and try tomorrow. We wouldn’t burn a Saturday on an outage.

The key came from a sketchy seller

Five-dollar keys in a chat group. Office keys from a stranger on a forum. They work until they don’t. Microsoft catches up with the batch, blocks it, and the buyers end up reading pages like this one.

Which bucket you’re in

Match what happened to you with the left column.

Check the license status first

Do this before any fix. It takes less time than reading this paragraph. Open an admin Command Prompt. On Windows 11, right-click Start and pick Terminal as admin. On Windows 10 the same menu offers Windows PowerShell as admin, and that works too.

Then run this:

slmgr /dlv

A small window pops up. Two lines in it matter.

An OEM key that died after a motherboard swap needs a different fix than a Retail key from a bad seller. That’s why this window comes first.

Run a second command while you’re there:

slmgr /xpr

Does it say the machine is permanently activated? Then the license was valid at some point, and the code came later. Hardware or server trouble is the likely story. Never says that? Then the key was never accepted.

ShowKeyPlus, the easier view

ShowKeyPlus is free in the Microsoft Store. It shows the installed key and pulls the OEM key from the firmware when there’s one. Both get labeled with the matching Windows edition. On refurbished laptops we’d open it before anything else.

OEM, Retail, Volume: why the channel matters

The Description line in the license window names the license channel. Each channel behaves differently when this code appears.

Retail is the forgiving one. Remove the key from the old PC, and it can activate the new one. Linked to a Microsoft account, it survives a motherboard swap.

OEM is the strict one. The license lives and dies with the original board. Replace the board, and you need a new key.

Volume keys don’t belong on a home PC at all. A cheap key that shows up as Volume was resold out of a company’s pool. Those batches get blocked sooner or later.

How to fix the 0xC004C060 activation error

Work down the list and stop when activation goes through. The details for each step follow below.

1. Run the activation troubleshooter and pick the hardware-change option.
2. Restart the Software Protection service.
3. Remove the product key and install it again.
4. Reinstall the system license files.
5. Repair system files with DISM and SFC.
6. Install every pending Windows and Office update.
7. Activate offline through the Product Activation portal.
8. For Office, run the Get Help troubleshooter.
9. Ask the seller for a replacement key.

Not every fix suits every cause. This table pairs them up.

And this is what each one costs you in time.

Fix 1: the activation troubleshooter

The troubleshooter has a reputation for doing nothing. Usually deserved. For this code it does help, mostly after a hardware change. It restores digital licenses. It can’t revive a blocked key.

1. Open Settings, then System, then Activation.
2. Click Troubleshoot. No such button? Then Windows already considers itself activated.
3. Let the scan run. Apply the fix it suggests.
4. Choose “I changed hardware on this device recently” when it’s offered.
5. Sign in with the Microsoft account linked to your license.
6. Pick this PC from the list and confirm.
7. Reboot.

Windows 10 keeps it elsewhere. Settings, Update & Security, Activation, Troubleshoot. Same result.

For motherboard swaps this is typically the fix that works most often. The condition is the Microsoft account link. Without it there’s nothing for the troubleshooter to restore.

Fix 2: restart the Software Protection service

One service runs the whole licensing stack. Its display name is Software Protection. Inside Windows it’s called sppsvc. When it hangs, activation fails silently. A perfectly good key gets this code for no reason beyond a stuck service.

1. Press Win + R, type services.msc and press Enter.
2. Scroll down to Software Protection.
3. Right-click it and open Properties.
4. Running? Stop it, count to three, start it again.
5. Stopped? Click Start.
6. Set the startup type to Automatic with delayed start. Not plain Automatic, not Manual.

Then test activation, in Settings or with this command:

slmgr /ato

If the service was wedged, a success message appears within seconds. Nothing? Next fix.

Fix 3: remove the key and install it again

Windows may be holding a mangled copy of your key. A botched install or a power cut can leave half-written data in the licensing store. The system then reads garbage where the key should be. Clearing it and typing it fresh fixes that.

Four commands, in an admin Command Prompt:

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

The last line does the real work. If it’s going to succeed, you’ll see the message in about 15 seconds. Same code again? Then the server is rejecting the key itself. No command changes that, and we’d jump to Fix 9.

The whole thing takes about 90 seconds. It’s worth trying before the heavier fixes.

Fix 4: reinstall the system license files

Less known, and occasionally the one that saves the day. The /rilc switch reinstalls the Windows system license files. Microsoft documents it for exactly that. Think of it as SFC for the activation system.

Use it when Fix 3 keeps failing and you suspect the cache, not the key.

Restart the service first:

net stop sppsvc
net start sppsvc

Reinstall the license files, then reset the activation state:

cscript.exe slmgr.vbs /rilc
slmgr.vbs /rearm

Reboot. Twice, actually. The first reboot applies the rearm, and the second lets the licensing layer settle. Then try again:

slmgr /ato

Windows lets you rearm only a limited number of times. The license details window shows how many are left. We wouldn’t run it casually, but one rearm at this stage is fine.

It repairs the cache and never a blocked key. When it fails on a healthy system, that tells you something too. The key is the problem.

Fix 5: repair system files with DISM and SFC

A long shot, but cheap. Corrupted system files can break activation in ways that show up nowhere else. About 15 minutes rules it out.

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

The first command takes a while. Reboot when both are done, then try to activate. Alone this rarely clears the code. It does remove junk that might interfere, and we’d rather know that before the offline route.

When does it matter? SFC reports that it found corrupt files and repaired them. That’s the signal. Try activation again right after the reboot, before anything else.

Fix 6: update, then activate

An old Windows build? An outdated Office? Update first. Microsoft ships activation fixes inside cumulative updates. This code can vanish after one pending update, with no commands at all.

• Windows. Settings, Windows Update, Check for updates. Take everything, optional updates included. Reboot.
• Office. Open Word. File, Account, Update Options, Update Now.

Is Update Now grayed out? Then a domain or company policy manages that Office, and IT has to push the update.

One toggle catches people. Under Windows Update, Advanced options, switch on “Receive updates for other Microsoft products”. Without it, Office updates never arrive through Windows Update.

Fix 7: phone activation, now the Product Activation portal

The old phone route has moved. Microsoft took telephone activation online, to the Product Activation portal. Same idea as before. Installation ID in, Confirmation ID out. Good for a genuine key that online activation keeps refusing. Or a PC with no internet at all.

First, the Installation ID. Admin Command Prompt:

slmgr /dti

A long string of digits. Copy it into Notepad. Then the portal, from any device with a browser:

aka.ms/aoh

1. Solve the CAPTCHA.
2. Pick Proceed to Sign In. A personal Microsoft account works, so does a work or school one.
3. Choose Activate a Microsoft Product.
4. Select the product and its version.
5. Paste the Installation ID and read back the Confirmation ID.

Back on the PC, with the Confirmation ID in place of the X’s:

slmgr /atp XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX

Worried about the sign-in? Don’t be. Logging in doesn’t tie your account to the license. Retail, OEM and Volume keys all go through the same Activate a Microsoft Product button.

Office has its own pair of switches in ospp.vbs. Run them from the Office folder, admin prompt again.

cscript ospp.vbs /dinstid
cscript ospp.vbs /actcid:CONFIRMATIONID

First line prints the ID. Second one takes the answer. The portal itself is covered in the support article Activate Microsoft perpetual products using the Product Activation portal. A key that’s truly blocked fails here too. Then Fix 9 is the one left.

Fix 8: the Get Help troubleshooter, for Office

The old Microsoft Support and Recovery Assistant is gone. Microsoft removed its command-line version, SaRAcmd, on March 10, 2026. The replacement is GetHelpCmd.exe. The consumer Office troubleshooters now run inside the Get Help app that ships with Windows.

1. Open the Get Help app from the Start menu.
2. Search for “Office activation” and start the troubleshooter it offers.
3. Sign in with the account tied to your Office license.
4. Let it run. The scan and fix cycle takes roughly 10 minutes.

IT admins who scripted SaRAcmd need the new command-line tool for unattended runs.

One thing the old assistant used to catch was a corrupt cached license file. You can clear that by hand today. The folder is here:

%LocalAppData%\Microsoft\Office\Licenses

Close every Office app. Rename the Licenses folder. Open Word and sign in again.

Fix 9: get a working key

Everything above failed? Then the key is dead. What you do next depends on where the key came from.

• A third-party seller. Email them the code and ask for a replacement. A decent seller replaces the key without a fuss. One that stalls or goes quiet has told you what you needed to know.
• Microsoft itself. Their support can look up the key’s status and reactivate it. No phone line now. The Product Activation portal can hand you over to a live chat if your case qualifies, and they can issue a new key when the old one was batch-blocked through no fault of yours.
• Starting over. Get a Retail key, not OEM. Retail keys move between computers. OEM keys stay with the hardware for good.

That’s also where we come in. Our Windows license keys and Office license keys are genuine and emailed instantly after payment. If a key doesn’t activate, we help you fix it or send a replacement. We’d take that over a few dollars saved on an anonymous marketplace.

After a motherboard swap, step by step

This is one of the most common stories behind the code. The order of moves matters.

1. Check the channel with the license details command. Retail or OEM?
2. Retail, and linked to a Microsoft account: run the troubleshooter and choose the hardware-change option.
3. Retail, never linked: the Product Activation portal, receipt at hand. Our phone activation guide walks through it.
4. OEM: the license stayed with the old board. A new key is the way forward.

People often skip step one and spend an evening on commands. With an OEM license none of them can work. The license isn’t damaged. It simply belongs to hardware you no longer have.

Planning a board upgrade and not there yet? Link the license to your Microsoft account today. It takes a minute in Settings, under Activation.

The Home-to-Pro upgrade that keeps failing

The setup looks like this. The laptop shipped with Home. An OEM Home key sits in the UEFI firmware. You want Pro for Remote Desktop, BitLocker or the Group Policy editor.

So you buy a Windows Pro key and type it into Settings. Windows says it’s upgrading. Reboot. Then the code, and activation failed.

Behind the scenes the firmware is still presenting the original Home key. Your Pro key goes in, the firmware offers its own, and the two conflict.

Clear the installed key and put the Pro key in by hand:

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

The second line matters most here. It wipes the key from the registry, so the firmware key doesn’t reload at once. Reboot afterwards.

The two-step move for stubborn laptops

Still bouncing back to Home? Install the generic Pro installation key first. It forces the edition switch cleanly.

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

That string is the generic Pro setup key for both current Windows versions. It’s a generic installation key: it installs, it doesn’t activate. Nothing more. It’s a placeholder that makes the licensing layer commit to Pro.

It isn’t a KMS key, by the way. The Pro KMS client key on Microsoft Learn is a different one:

W269N-WFGWX-YVC9B-4J6C9-T83GX

Reboot once the generic key is in. Then install your real Pro key and activate. An ugly workflow, and it works on business laptops where the direct route keeps failing.

The 0xC004C060 Office activation error

Office 2013 and newer share the Software Protection service with Windows. But slmgr manages only the Windows key. So Office gets its own tools, and we’d try them in this order.

Re-enter the key inside Office

Open Word. Go to File, then Account. Near the product information there’s a Change Product Key link. Click it and type your 25 characters. The cache refreshes and activation runs again.

It’s the low-effort first step, and it costs a minute.

Online Repair

Open Control Panel, then Programs and Features. Find Microsoft Office in the list and click Change. Pick Online Repair, not Quick Repair.

Quick Repair only resets shortcuts and registry entries. Online Repair tears the install down and rebuilds it from Microsoft’s servers. Roughly 20 minutes, depending on the connection. It clears corrupted licensing files most of the time.

The OSPP script

It gives far more detail than any settings page. Open an admin Command Prompt and change to the Office folder. On most 64-bit installs:

cd "C:\Program Files\Microsoft Office\Office16"

Some 32-bit installs sit here instead, even on 64-bit Windows:

cd "C:\Program Files (x86)\Microsoft Office\Office16"

Then run the activation:

cscript ospp.vbs /act

Success gives you a success message. Failure gives you a detailed reason code. The settings page only says something went wrong. This script says what.

After a Windows upgrade

Sometimes Office stops activating right after a move from Windows 10 to 11. Office itself didn’t change. The upgrade touches registry keys and the license cache. Microsoft’s servers can read that as a new device. The Get Help troubleshooter fixes it fast. Online Repair usually does too.

On a work or school PC

Different rules apply there. The key usually belongs to the organization, and the channel shows Volume. Activation runs through the company’s setup.

So don’t run the key commands on such a machine. You could remove a key you can’t put back. Tell IT which code you see and when it started. That’s the whole job on your side.

Reinstalling Windows won’t fix the 0xC004C060 activation error

It’s the first thing many people try. A clean install, a fresh start, the same key. And the same code, because the problem travels with the key.

The server doesn’t care how clean the install is. It checks the key and the hardware. A blocked key fails on a fresh system exactly as it failed on the old one.

So save yourself the afternoon. Reinstall only when the system itself is broken, and we’d confirm that with Fix 5 first.

The 0xC004C060 activation error isn’t a virus

A common question. It isn’t one. The code comes from Microsoft’s activation servers. A licensing message about the product key, and nothing else.

Nothing on the PC is damaged. Nobody broke in. Windows or Office simply stays unactivated until a valid key is accepted.

What to send the seller

A good message gets a fast answer. Put these in one email.

• The order number.
• The exact code, and a screenshot of the message.
• The edition you installed. Home or Pro, and which Windows.
• The channel from the license details window.
• What you already tried. The troubleshooter, a key reinstall, the Product Activation portal.

With that in hand, support can tell a blocked key from an edition mix-up in one reply. Without it, you trade emails for two days.

Bought from us? Write to support@hypestkey.com with the same five things. We check the key and either get it activated with you or replace it.

The short path, if you’re in a hurry

Three moves settle most cases.

1. Run the license details command and read the channel.
2. Hardware changed? The troubleshooter. Otherwise remove the key and install it again.
3. Same code after that? Write to whoever sold you the key.

Everything else on this page is for the cases that don’t fit. There are fewer of those than the length of this guide suggests.

The 0xC004C060 activation error on Windows 11, Windows 10 and Office

We’d treat the 0xC004C060 Windows 11 activation error exactly like the Windows 10 one. Same fixes, same order.

Office installations activated through a Microsoft account don’t use ospp.vbs at all. We list every other activation code in our Windows 11 activation errors guide, each with its own fix.

Every slmgr command in one table

We never remember these by heart. Which one clears the registry again? So we keep this table handy. More switches are in our slmgr commands list.

Admin Command Prompt only. A regular one doesn’t have the rights to touch activation. PowerShell mostly works too. The license details popup sometimes fails to appear there, so we’d stay with Command Prompt.

Codes related to the 0xC004C060 activation error

Sometimes a fix changes the code. You start with one, apply something, and Windows shows another. That’s good news. A different code points to a narrower cause.

What happens if you never activate

Windows keeps running. Apps run, games launch, and Windows 11 still gets security updates. You get a permanent “Activate Windows” watermark in the corner. And the personalization settings stay locked. No wallpaper changes, no accent colors, no lock screen tweaks.

Annoying, obviously. A dealbreaker? Depends how much you care.

Office is stricter. After the grace period, usually 30 days, it drops into reduced functionality mode. You can open and view files. You can’t edit or save them. At home that’s survivable, and at work we’d call it a hard no.

Keeping the 0xC004C060 activation error away next time

• Buy from Microsoft, or from a seller that replaces keys. A price that looks too good usually ends here.
• Save the receipt and the email with the key. If the key is ever batch-blocked, proof of purchase gets you a replacement.
• Link a Retail license to a Microsoft account right after activating. Settings, Activation, Add a Microsoft account. Hardware swaps get painless.
• Check the license details straight after the first activation. Bought Retail? The description should say Retail, not OEM and not Volume. A mismatch is something to raise with the seller at once.
• Only installing on a test VM, or a PC you’ll license later? Use generic installation keys. They exist for exactly this kind of setup. They install any edition, and you activate properly later.

Which fix for which situation

We’d keep the order email with the key at hand: if the error leads to Microsoft support, they can ask for proof of purchase.

Quick answers

Related guides

• 0xC0EA000A Activation Error
• 0xC004F009 Activation Error