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

The 0xC004F012 activation error appears when the Software Licensing Service can’t find a value in the Windows license store. Activation stops before it reaches your key.

In most cases the license store file, tokens.dat, is damaged or incomplete.

• Rebuild tokens.dat with Microsoft’s documented commands.
• Restart twice.
• Reinstall your product key and activate again.

The full text reads: “The Software Licensing Service reported that the call failed because the value for the input key was not found.”

It’s not the clearest sentence Microsoft ever wrote. The “input key” here isn’t your product key.

It’s an internal lookup key inside the licensing database. Say the code appears on a remote worker’s laptop after a big feature update.

Then the problem usually sits in a file on the disk, and the license is fine.

What 0xC004F012 stands for

In plain terms, Windows looked up a licensing entry in its local store, and the entry was missing.

Activation can’t continue without it. So the code shows up even with a valid key.

Microsoft’s consumer list of activation codes doesn’t include this one, and neither does the main IT reference table. That’s why many pages guess.

The message text and Microsoft’s own “rebuild the licensing store” article tell a consistent story. The license store on your PC is the suspect.

You can see the official wording on your own machine. Press Win+R and run this:

slui.exe 0x2a 0xC004F012

Windows opens the activation dialog with that code’s description. The trick works for any activation code, which is handy when a screenshot shows only the number.

Causes

A damaged or incomplete license store causes it most often. That often follows a feature update, an in-place upgrade or a reset that didn’t finish.

A quick word on unofficial activators. They often work by replacing or editing exactly the files this code is about.

Remove them, rebuild the store and use a genuine key. Otherwise the code tends to come back after the next update.

How to fix the 0xC004F012 activation error

A rebuild of the license store fixes it, and the whole procedure takes about ten minutes.

1. Write down your product key first. Or confirm on the Activation page that a digital license is linked to your Microsoft account.
2. Open Command Prompt as administrator: search for cmd, right-click Command Prompt and select Run as administrator.
3. Stop the Software Protection service with the first line below.
4. Go to the license store folder with the second line.
5. Rename the store file with the third line. Renaming keeps a backup, so don’t delete the file.
6. Start the service again with the fourth line.
7. Reinstall the system license files with the fifth line.
8. Restart the computer twice. The second restart matters, and Microsoft’s procedure asks for both.
9. Reinstall your key and activate, with the sixth and seventh lines.
10. Check the result with the last line. “License Status: Licensed” shows you’re done.

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
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato
slmgr /dlv

After the rebuild Windows needs the key again. With a digital license and no key, open the Activation page and select Troubleshoot.

The steps follow Microsoft’s procedure for how to rebuild the Tokens.dat file, originally KB 2736303.

The same article warns never to use the /upk switch to remove a key. Install the fresh one over the old with /ipk.

If the stop line reports that the service isn’t running, carry on with the next step. If the rename says access is denied, the service is still running. I’d run the stop line once more and wait a few seconds.

If the rebuild doesn’t help

Repair the Windows system files next, then restart and rebuild the store once more.

When both fail, an in-place repair install keeps your apps and files and replaces the licensing components.

Work in this order, as a rule.

A full reset sometimes helps too. It costs far more hours than a repair install and gives no better odds for this particular code.

Is the product key bad

No. The code is raised before Microsoft ever checks your key. So it says nothing about the key’s validity.

It points to the local license store. Once the store is rebuilt, a genuine key activates normally.

If a different code appears afterwards, that code tells you about the key.

Each has its own fix.

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

After a Windows upgrade

That’s one of the most common moments to see this code. The license store can end up half-migrated.

Rebuilding tokens.dat is usually enough, and a digital license then reactivates by itself.

Before you rebuild, give Windows one chance. Restart, connect to the internet, wait twenty minutes and check the Activation page again.

Background activation sometimes fixes a fresh upgrade with no help. If the code is still there, rebuild.

According to Microsoft, a move between the two systems on the same hardware keeps your license. The edition has to stay the same.

A Home license upgrades to Home, and Pro to Pro. A mismatch there produces other codes, not this one.

Windows Server and Office

On current server versions the fix is identical. The rebuild procedure is written for Windows Server and modern Windows alike, with the same folder path.

On a server, plan the two restarts in a maintenance window. After the rebuild, reinstall the server key and activate.

Volume-licensed Office on a client PC shares the same Software Protection service. So expect to reactivate Office after a rebuild.

For the LTSC volume editions, check the license afterwards from the program folder.

Where these steps apply

The path of the store file is the same on all of them:

%windir%\System32\spp\store\2.0

Older systems such as Windows 7 and Windows 8 use different paths and aren’t covered here.

For the bigger picture of every common code, see the Windows 11 activation errors overview.

Mistakes we see most

• Deleting the store file when a rename keeps a backup.
• Restarting once and skipping the second restart.
• Forgetting to note the product key before the rebuild.
• Using the /upk switch to remove a key.
• Buying a key for a problem in the local store.
• Leaving an “activator” tool installed.
• Trying the rename while the service still runs.
• Resetting Windows before trying a repair install.

Terms used on this page

A few cases from support

The feature update

A laptop shows the code after a big feature update. The store file gets rebuilt. After two restarts the digital license activates by itself.

The single restart

Someone rebuilds the store and restarts once. The code stays. After the second restart it’s gone.

The activator

The code returns after every update on one PC. An activator tool keeps editing the licensing files. With the tool removed and a genuine key in, it stays away.

The denied rename

One rename fails with access denied. The service is still running. A second stop command and a short wait fix that.

The office suite

Some office PC has its store rebuilt, and the volume edition of Office asks for activation. One activation command settles it.