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

The 0xC004F213 activation error appears when Windows looks for a license that matches this PC’s hardware and finds none. It then reports “no product key was found on your device”.

There are two direct fixes.

Most cases follow one of three events.

• A motherboard swap
• A clean install of the wrong edition
• A reset on a PC whose license was never linked to a Microsoft account

The message on the Activation page reads: “Windows reported that no product key was found on your device. Error code: 0xC004F213.”

The wording is scary, and the content is simple. Windows isn’t saying your key is fake or blocked.

It’s saying it can’t see one at all. Nothing is in the firmware, nothing in the registry, and no digital license is tied to the current hardware ID.

That’s usually fixable, as long as you still own a valid license.

What 0xC004F213 stands for

The Windows Software Licensing Service couldn’t find any product key or digital license that fits the current device.

Microsoft describes it as “no product key was found on your device” and links it to hardware changes.

A Windows license is tied to the hardware it was activated on, above all the motherboard.

Behind the scenes, activation checks three places.

Find nothing in any of the three, and you get 0xC004F213.

A key of the wrong type, or one already used, gives a different code. One example is 0xC004C008 for a key used on too many devices.

Causes

Each cause has its own fix. That’s why the table comes before the steps.

How to fix the 0xC004F213 activation error

Check the edition and license channel first. Then reactivate with the method that matches your license.

1. Sign in with an administrator account and connect to the internet. Activation can’t finish offline.
2. Open the Activation page. On Windows 11 it’s under Settings, System, Activation, and on Windows 10 under Settings, Update & Security, Activation.
3. Note the edition shown, Home or Pro, and the exact message text.
4. Open Terminal as admin and run the first line below. Write down the Name and Description lines.
5. Check the firmware for an OEM key with the second line, in an admin PowerShell.
6. After a motherboard swap with a linked license, select Troubleshoot on the Activation page and follow the hardware change route.
7. With a retail or upgrade key, select Change product key and type the 25 characters.
8. Restart, open the Activation page again and confirm it says “Windows is activated”.

slmgr /dlv
(Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKeyDescription
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato
slmgr /dli
slui 4

The Activation page also opens from the Run box with ms-settings:activation.

A description with “Core” next to an installed Pro edition points to the wrong edition. The edition section below covers that.

On the hardware change route, choose “I changed hardware on this device recently” and sign in with the linked account. Then tick “This is the device I’m using right now” and select Activate.

If the code stays or a different one appears, try the phone activation line. After that, I’d contact Microsoft support with the detailed license output ready.

The Troubleshoot button only appears while Windows isn’t activated. The troubleshooter can only reactivate a license linked to the Microsoft account you sign in with. With a local account alone, I’d never expect the old device in the list.

After a motherboard replacement

The motherboard is the anchor of the hardware ID. Swap a GPU, add RAM or replace an SSD, and Windows usually stays activated.

Replace the board, and Windows sees what is, in practice, another computer.

Microsoft’s own page on reactivating Windows after a hardware change lists the conditions.

• You must be an administrator.
• The license must be linked to your Microsoft account.
• The edition must stay the same before and after.

Three situations come up, as a rule.

An OEM license generally stays with the old board.

The wrong edition

Installing Windows 11 Pro on a PC that shipped with the Home edition leads to this code quite often. The key in the firmware only covers Home.

Windows then finds no license for the Pro edition you installed.

It happens a lot after a clean install from a USB stick. The edition list appears when setup finds no key, or when a generic installer is used.

It’s easy to tick Pro “just in case”. Windows installs it happily.

Activation then fails, because the digital license and the OEM key both say Home.

There are two ways out.

The Windows 11 Home vs Pro comparison lists what Pro adds.

• BitLocker management
• Group Policy
• Hyper-V
• Remote Desktop host

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

Finding the missing product key

There are four places to look.

The key currently installed only shows its last five characters.

(Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey
wmic path softwarelicensingservice get OA3xOriginalProductKey

Run the first line in an admin PowerShell. An empty result shows the board has no embedded key.

That’s normal for self-built PCs and for replacement boards bought at retail.

The second, older line still appears on many sites. WMIC is being phased out on current Windows 11 builds and may be missing, so I’d use the PowerShell form.

A free tool such as ShowKeyPlus reads the firmware key and the installed key together. It shows which edition each belongs to.

Digital licenses from a free Windows 7 or 8.1 upgrade often have no key you can look up. The same goes for licenses from the Microsoft Store. They live on Microsoft’s servers against the hardware ID, and I’d call a board swap with no linked account the hard case for that reason.

After a reset or reinstall

The code can show up then too. It happens when a key was never saved and the reinstall used different hardware.

It also happens when setup was told “I don’t have a product key” on a machine with no firmware key.

On the same unchanged hardware, a digital license normally reactivates by itself within a day online.

Patience matters here. A clean install on the same computer, same edition, rarely needs anything at all.

Activation runs in the background after the first internet connection. Seeing the code in the first hour after setup isn’t yet a reason to buy anything.

Restart, check that date and time are correct, and press Troubleshoot once.

If it still fails after a day on the same hardware, the license was probably never digital for this PC. Think of a key a previous owner installed on a used computer.

Enter a key you own, or contact the seller who supplied it.

Not a sign of a fake or blocked key

This code carries no piracy or blocked-key message. It tells you no license was found at all.

So F213 tells you Windows simply has nothing to check.

That distinction saves time. People sometimes buy a key straight away, when the license they already own would work after one troubleshooter run.

The reverse happens as well. Someone keeps retrying the troubleshooter on a store-bought PC with a self-fitted board.

There, the old OEM license honestly can’t move.

Other activation codes nearby

F213 is about a missing license. Most nearby codes are about a license that exists but fails a check.

Matching the code to its cause tells you what to do: look for your old license, or fix the one you entered.

The general guide to Windows 11 activation errors lists the rest.

When to contact Microsoft support

Contact support when three things are true.

• You own a valid license.
• The troubleshooter doesn’t list your device.
• Phone activation isn’t offered.

Have these ready.

• The code
• The detailed license output
• The edition
• Proof of purchase

Support can usually confirm if the license may move to the changed hardware.

The Microsoft list of Windows activation errors gives the official wording for this code. It also lists the options Microsoft itself offers.

• Buy a license from the Store.
• Enter a key used before on this device.
• Use the hardware change troubleshooter.

We added the edition check because Microsoft’s page doesn’t spell it out.

Before you call, ask one honest question: was this license really yours to move.

For every activation method side by side, the complete Windows activation guide covers product keys, digital licenses and phone activation.

Where these steps apply

The steps apply to PCs activated with a retail key, an upgrade key, a digital license or a preinstalled OEM key. Menu names follow current Windows 11.

Mistakes we see most

• Buying a key before trying the troubleshooter with a linked account.
• Running the troubleshooter with a local account.
• Installing Pro on a PC whose firmware key is for Home.
• Expecting an OEM license to follow a self-fitted board.
• Judging activation in the first hour after a clean install.
• Reading the code as proof of a fake key.
• Typing a key for another edition.
• Skipping the link to a Microsoft account before a planned board swap.

Terms used on this page

A few cases from support

The swapped board

A PC shows the code on the first boot after a board swap. The license is linked to a Microsoft account. The troubleshooter activates it within a minute.

Pro on a Home laptop

One laptop gets a clean install of Pro, and activation fails. The firmware key is for Home. A Pro key through Change product key settles it.

The first hour

The code appears right after a clean install on the same hardware. Nothing gets entered. By the next morning the PC is activated.

The auction board

An owner fits a used board from an auction site into a store-bought PC. The OEM license stayed with the old board. A fresh license activates the PC.

The local account

Someone runs the troubleshooter and sees no devices. They’re signed in with a local account. After signing in with the linked account, the old device appears.