Fix it now
Microsoft documents 0x80070490 for activation as “the product key you entered did not work; check the product key and try again, or enter a different one”. The troubleshooter shows it when the entitlement it went looking for is not there, so the useful work is finding out which layer underneath is actually empty.
cscript //nologo %windir%\system32\slmgr.vbs /dli
cscript //nologo %windir%\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript //nologo %windir%\system32\slmgr.vbs /ato
- Run
winverand compare the edition with the licence description from/dli. An entitlement for the wrong edition looks like no entitlement at all. - Sign in with the Microsoft account that holds the digital licence, and confirm it at
Settings > Accounts > Your info. The troubleshooter can only see licences on the account it is running under. - Run the troubleshooter again from
Settings > System > Activation > Troubleshoot, signed in as an administrator, and take the option about recently changed hardware. - If you hold a key, install it directly rather than through the troubleshooter.
slmgrreturns a specific code where the troubleshooter returns a generic one.
If the edition is wrong, stop retrying. Change to the edition your licence covers first, and activate afterwards – Microsoft documents a Home licence with Pro installed as needing a clean install rather than a key change.
If the account or the edition was the problem, you can stop here. If neither was, the next section covers what the troubleshooter is and is not built to do.
Why it happens
There are two published readings of this code and they fit together. In its activation documentation Microsoft lists 0x80070490 with the message “the product key you entered did not work – check the product key and try again, or enter a different one”. Elsewhere the same value appears as WIN32 1168, ERROR_NOT_FOUND, element not found. The second explains the first: the troubleshooter went looking for something and it was not there, and what surfaces is a not-found result dressed as a key failure.
That is why the code tells you so little on its own. The Activation Troubleshooter is not a repair tool; Microsoft documents it as handling four specific situations – a digital licence that exists but has not been applied, a Pro digital licence with Home installed, a Home digital licence with Pro installed, and significant hardware changes. Anything outside that list it reports as a failure and refers you to the error code list.
It also has three requirements that quietly account for most empty results. You must be signed in as an administrator. The machine must have an internet connection. And the entitlement must belong to the account you are signed in with. The Troubleshoot option only appears while Windows is unactivated, so if you cannot find it, Windows already believes it is activated and you are looking at a different problem entirely.
One companion code is published and it is worth recognising. Microsoft documents 0xC004E028 as trying to activate a device that is already in the process of being activated, and states that it should activate once the first request completes. If you see that after clicking twice, the answer is to wait rather than to click again. 0x803F700F, 0x803F700C and 0xC004C700 are not published.
The digital licence is on a different account
You have this one if The troubleshooter runs and finds nothing, and the account signed into Windows is not the one used when the machine was first activated.
- Sign out and sign in with the Microsoft account that was linked at the time of the original activation.
- Confirm the account at
Settings > Accounts > Your info. A local account cannot hold a digital licence. - Re-run the troubleshooter as an administrator and choose the changed-hardware option.
- Pick the affected machine from the device list, tick “This is the device I’m using right now”, and select Activate.
A digital licence is attached to an account only if you were signed in with that account while the machine was activated. Signing in afterwards does not create the link retrospectively.
The installed edition does not match the licence
You have this one if winver reports one edition and slmgr /dli describes a licence for another.
- Decide which edition your licence actually covers before touching anything.
- Pro licence, Home installed: enter the key at
Settings > System > Activation > Change product key. Microsoft documents that as a supported upgrade. - Home licence, Pro installed: Microsoft documents that as needing a clean installation of Home, not a key change.
- After the edition matches, run
slmgr /ato.
The device cannot reach the licensing service
You have this one if 0x803F700C or 0x803F700F appears alongside, and the Store also fails to sign in or load.
- Confirm general internet access, then check the system-level proxy with
netsh winhttp show proxy. It is not the browser’s. - On a filtered network, ask for Microsoft licensing and activation endpoints to be exempted from TLS inspection rather than merely permitted. Microsoft publishes
licensing.mp.microsoft.comas the online activation endpoint. - Correct the clock with
w32tm /resync, since a skewed clock breaks the secure connection. - Retest from an unfiltered connection to confirm the diagnosis.
The entitlement belonged to hardware that no longer exists
You have this one if The machine has a new motherboard, or the key came preinstalled on a different device, and every attempt gives the same result.
- Check the machine for a firmware key before assuming there is none.
- If a firmware key exists, install it with
slmgr /ipkand activate. - If the previous licence was OEM and the board was replaced, the entitlement does not transfer and the troubleshooter cannot recover it.
- If the machine is under warranty, ask the manufacturer before buying anything.
Full reference
What the troubleshooter is documented to fix
| Situation | Documented outcome |
|---|---|
| A digital licence exists but Windows is not activated | The troubleshooter applies it |
| A Pro digital licence, Home installed | Handled as an upgrade to Pro |
| A Home digital licence, Pro installed | Requires a clean installation of Home |
| Significant hardware changes | Handled through the changed-hardware option |
| Anything else, with an error code | Not handled. Look the code up instead |
Where the fault actually sits
| What you see | What it points at |
|---|---|
| No option about changed hardware | No Microsoft account signed in, or that account has no digital licence |
slmgr /dli shows a different edition from winver |
An edition mismatch between the installation and the licence |
| 0x803F700C or 0x803F700F alongside | The device could not reach the licensing service |
| 0xC004E028 | An activation is already in progress. Let the first one finish |
| No Troubleshoot option at all | Windows already considers itself activated |
Why installing the key directly tells you more
The troubleshooter compresses several different failures into one message. cscript //nologo %windir%\system32\slmgr.vbs /ipk <key> followed by /ato returns the specific code from the licensing service, and that code is what any further diagnosis has to start from. Microsoft’s own edition-upgrade documentation uses the cscript form for exactly this reason: run bare, slmgr reports through the default script host and puts its answer in a dialog rather than on the console.
Changing the product key or the installed edition rewrites the machine’s licensing state, so take a restore point first. Never run slmgr /upk speculatively: Microsoft documents that the system enters the Unlicensed state after the next restart, so removing a working key leaves you with no way back if the replacement turns out to be wrong.
Reading the firmware for a key
On a machine that shipped with Windows preinstalled, the key normally lives in firmware. The usual query is (Get-CimInstance -ClassName SoftwareLicensingService).OA3xOriginalProductKey in PowerShell. It is worth running because it costs nothing, but note that the property is not listed in Microsoft’s published SoftwareLicensingService class reference – so treat a blank result as inconclusive rather than as proof that no key exists.
Before you decide the machine needs a licence
- Try every Microsoft account that has ever been used on the machine. Entitlements are per account, and people forget which one they used.
- Confirm you are an administrator and online. Both are documented requirements for the troubleshooter and both are easy to overlook.
- Check the edition twice, once with
winverand once withslmgr /dli. They disagree more often than you would expect. - Check the firmware for a key. A machine that shipped with Windows may still carry one after a reinstall.
- Read the code from an elevated prompt rather than from the troubleshooter. A specific code is worth more than a generic one, and it is thirty seconds’ work.
When a licence is the actual fix
If the troubleshooter finds nothing because there is nothing to find, a licence is genuinely the missing piece rather than a setting. That is the case when the machine was never activated, ran on a key belonging to another device, or held an OEM entitlement that stayed with the motherboard it shipped on. A retail Windows 11 Pro key survives a board change and can be moved to a replacement machine later, which is the difference that matters after a rebuild. Arco can supply one – and we would rather check first whether your device has a firmware key or an account-linked digital licence you can use for nothing, because both of those are commonly missed and both are free.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80070490 |
Documented for activation as “the product key you entered did not work; check the product key and try again, or enter a different one”. The same value is documented elsewhere as WIN32 1168, ERROR_NOT_FOUND – element not found | Microsoft Learn |
0x803F700F |
Seen alongside when the activation client cannot complete a request against the licensing service. No published meaning | not published by the vendor |
0x803F700C |
Seen where there is no usable path to the licensing service. No published meaning; test connectivity rather than assuming | not published by the vendor |
0xC004E028 |
You are trying to activate a device that is already in the process of being activated; it should activate once the first request completes | Microsoft Support |
0xC004C700 |
Raised in the online activation exchange. No published meaning | not published by the vendor |
Confirm the fix worked
Settings > System > Activationshows Windows as activated and states whether it used a digital licence or a product key.slmgr /dlvreports Licence Status: Licensed.winverand the licence description inslmgr /dliname the same edition.- The Troubleshoot option has disappeared from the activation page.
- Reboot and re-check, since a licence applied but not committed reverts on restart.
Questions people ask about this
Is the troubleshooter worth running at all?
Yes, for the four things Microsoft documents it for: applying a digital licence that has not been applied, the two edition mismatches, and reattaching a licence after a hardware change. For anything else it adds a layer of vagueness. Install the key directly with slmgr and read the real code.
What does 0x80070490 actually mean?
Microsoft’s activation documentation gives it as the product key you entered not working. The same value appears elsewhere in Windows as WIN32 1168, ERROR_NOT_FOUND – element not found. Both readings are published, and together they describe the situation accurately: the troubleshooter looked for an entitlement and did not find one.
Do I have to buy a new key?
Not if the machine already has an entitlement. Check the firmware for a key and check whether a digital licence exists on any account you have used. Buying is the honest answer only when the machine has no entitlement of its own, which is common after a motherboard replacement on an OEM device.
How many times can a digital licence be reattached?
Microsoft does not publish a limit, so treat any number you read as invented. What is documented is that the licence is bound to hardware and that the account link must exist before the hardware changes. Link the account while the machine is still activated, not afterwards.
Why does the same key work on another machine?
Because the key is fine and the fault is this machine’s state – most often the edition, the account, or a connection to the licensing service. Retail keys move between machines one at a time; OEM keys do not move at all.
