Fix it now
Microsoft documents 0xC004F014 as SL_E_PKEY_NOT_INSTALLED, the product key not being available, with no product keys installed on the system as the cause. There is nothing broken to repair. The machine needs a key, from firmware, from an account-linked digital licence, or typed in.
cscript //nologo %windir%\system32\slmgr.vbs /dlv
cscript //nologo %windir%\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript //nologo %windir%\system32\slmgr.vbs /ato
- Check for a firmware licence before typing anything. In PowerShell:
(Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey. A blank result means there is none, which is a normal answer on a self-built machine. - If that is blank, sign in with the Microsoft account that may hold a digital licence for this hardware and open
Settings > System > Activation. - If a digital licence is reported, use Troubleshoot from that page while signed in as an administrator, and choose the option about recently changed hardware if it is offered.
- If neither route produces a licence, enter the key you own at
Settings > System > Activation > Change product key, or install it with the commands above.
The OA3xOriginalProductKey property is not in Microsoft’s published SoftwareLicensingService class reference. The query works on Windows 8 and later and costs nothing to run, but treat it as a convenience rather than a documented interface.
If a key is found and applied, you can stop here. If you expected one of the two free routes to work and it did not, the next section explains where each of them comes from.
Why it happens
This is the simplest activation error there is. Not a wrong key, not a blocked key: no key. Microsoft’s software licensing API reference names the code SL_E_PKEY_NOT_INSTALLED and describes it as the product key not being available, and the volume activation tables give the cause as no product keys installed on the system, with installing one as the remedy. There is nothing to troubleshoot in the usual sense.
A key normally arrives by one of two routes. A machine sold with Windows preinstalled carries its licence in firmware, in a table the manufacturer writes during production, and setup reads it automatically – which is why reinstalling on a branded laptop usually activates without anyone typing anything. A machine built from parts has no such table, and neither does one rebuilt around a bare replacement board.
The second route is a digital licence held on Microsoft’s side against the hardware, and optionally against a Microsoft account. That is what reactivates a machine which was licensed once and then reinstalled. It only works if the entitlement was created in the first place, which means the machine must have activated successfully at some point before the rebuild. If it never did, there is nothing to find and the troubleshooter will keep saying so.
The machine has no firmware licence and never had one
You have this one if The PowerShell query returns blank, and the computer was built from parts or is running a bare replacement board.
- Run the query from an elevated PowerShell prompt, to be sure it is returning nothing rather than failing.
- Check the invoice for the machine or the board to see whether Windows was ever supplied with it.
- If it was not, supply a key of your own and activate.
A blank result is a normal answer, not an error. Plenty of perfectly good machines have no firmware licence.
A digital licence exists but under a different account
You have this one if The machine was activated before the rebuild, but the activation page shows nothing while you are signed in with a local or work account.
- Sign in with the personal Microsoft account that was used on the machine previously.
- Open
Settings > System > Activationand check whether a digital licence is now reported. - Run Troubleshoot from that page as an administrator, and take the changed-hardware option if it appears.
A work or school account and a personal Microsoft account are separate identities. A licence held by one is invisible to the other, and Microsoft states the troubleshooter works only with the connected account.
The installed edition is not the edition that was licensed
You have this one if The firmware or digital licence covers Home and Pro is installed, or the other way around.
- Check what is installed with
winver. - Compare it with what the licence covers, from the original machine specification or the firmware key.
- Microsoft documents a Pro entitlement on a Home installation as a supported upgrade through the key or the Store, and a Home entitlement under a Pro installation as needing a clean install.
Setup installed a generic key that does not license anything
You have this one if Installation completed without asking for a key, and the machine reports an edition but no activation.
- Remove the placeholder:
slmgr /upk, thenslmgr /cpky. - Install your real key:
cscript //nologo %windir%\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX. - Activate with
slmgr /ato.
Generic keys exist so setup can pick an edition without licensing it. Refusing to activate is exactly what they are supposed to do.
Full reference
The codes Microsoft publishes for a missing key
| Code | Documented meaning | Where you see it |
|---|---|---|
0xC004F014 |
SL_E_PKEY_NOT_INSTALLED: the product key is not available | slmgr and volume activation output |
0xC004F213 |
Windows reported that no product key was found on your device | The Settings activation page |
0x800704CF |
A valid Windows licence for the device was not found | The Settings activation page |
0xC004F211 |
Windows reported that the hardware of your device has changed | After a board replacement, where a licence existed before |
Those last three are the consumer-facing wordings of the same situation, and if the machine showed you one of them rather than 0xC004F014, you are in the right place. The distinction that matters is between the first three, which mean nothing is installed, and 0xC004F211, which means a licence exists and no longer matches the hardware. That one has a route back through the activation troubleshooter; the others do not.
Reading the firmware licence
The usual query is (Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey in PowerShell, or wmic path SoftwareLicensingService get OA3xOriginalProductKey on older builds. It is worth running because it costs nothing and settles the question in a second. Be aware that the property is not listed in Microsoft’s published SoftwareLicensingService class reference, so it is a widely used convenience rather than a documented interface, and a blank result should be read as “no firmware key found” rather than as proof of anything.
What to check before deciding the machine is unlicensed
- Confirm the edition with
winver. An entitlement for one edition looks like no entitlement at all from the other. - Confirm you are signed in as an administrator. Microsoft documents that the Troubleshoot option on the activation page requires it.
- Confirm the machine has internet access. Activation and the troubleshooter both need it.
- Try each Microsoft account that has ever been used on the machine, not just the current one. Entitlements are per account.
- Check the invoice for the machine or the board. Plenty of bare boards and barebones systems are sold without Windows, and this error is the expected result.
Commands worth knowing
| Command | What it does | Needs elevation |
|---|---|---|
slmgr /dlv |
Detailed licence state, including whether a key is installed at all | No |
slmgr /dli |
Edition, channel and partial key | No |
slmgr /ipk <key> |
Installs a key, validating that it applies to the installed OS | Yes |
slmgr /ato |
Attempts activation now | Yes for online activation |
slmgr /upk |
Uninstalls the key. Unlicensed after the next restart | Yes |
slmgr /cpky |
Removes the key from the registry so it cannot be read back | Yes |
Linking the account, for next time
Once the machine is activated, link the Microsoft account from the activation page if it is not linked already. Microsoft’s reactivation guidance is explicit that this must be done before hardware changes, because the link is what the troubleshooter searches afterwards. It takes a minute now and is the difference between a five-minute reactivation and a new licence the next time a board fails.
When a licence is the actual fix
If there is no key in firmware, no digital licence on Microsoft’s side and no key on an invoice anywhere, the machine has simply never been licensed. That is normal on a self-built PC and on a machine rebuilt around a bare replacement board, and no repair tool resolves it because nothing is broken. Arco supplies Windows 11 Home retail keys for exactly this situation, and can confirm whether the edition installed is Home or Pro before you order so the key matches what is already on the disk. Run the firmware query and check the activation page under every account first – both are free routes and both are commonly missed.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F014 |
SL_E_PKEY_NOT_INSTALLED: the product key is not available. The documented cause is that no product keys are installed on the system | Microsoft Learn |
0xC004E017 |
Raised when a licensing request is made with nothing usable behind it. No published meaning | not published by the vendor |
0xC004E018 |
A related licensing failure where the entitlement the request needs is absent. No published meaning | not published by the vendor |
0xC004E009 |
Seen where the licensing state is incomplete, so the product cannot be treated as licensed. No published meaning | not published by the vendor |
Confirm the fix worked
slmgr /dlishows a partial product key where it previously showed none.- Licence Status reads Licensed.
Settings > System > Activationreports Windows as active and names the licence type.- The Microsoft account is linked on that page, so the entitlement can be recovered after a future hardware change.
Questions people ask about this
I reinstalled and it activated last time. Why not now?
Either the hardware changed enough that the digital licence no longer matches, or you are signed in with a different account, or the edition you installed is not the one that was licensed. Check the edition first with winver; it is the quickest of the three to rule out.
Can I recover a key from the old installation?
If the old system drive is still readable, a typed key may be recoverable from it. A licence that only ever existed as a digital entitlement never had a typed key at all and cannot be extracted. The firmware query is worth running either way.
Is a blank firmware key result a fault?
No. It is the normal answer for a self-built machine, a bare replacement board, and most machines that never shipped with Windows. Note that the property behind that query is not in Microsoft’s published class reference, so read a blank result as inconclusive rather than as proof.
Does the free upgrade entitlement still apply?
Machines that were upgraded from an older Windows and activated at the time hold a digital licence for that hardware. If the hardware has not changed, that entitlement should still be found. If the board has been replaced, it will not be.
Do I really have to buy a licence for a home PC?
If the machine has never been licensed, yes. Windows keeps running unactivated with a watermark and locked personalisation, so nothing breaks, but a machine in regular use should be licensed. Check the firmware key and the account-linked entitlement first, because both are free and both are commonly overlooked.
