0x803F7001 and 0x803F7000: No Digital Licence Found for This Device

Fix it now

Microsoft documents 0x803F7001 as a valid Windows licence not being found to activate this device, with entering a valid key or buying a digital licence as the documented actions. Before either, rule out the two things that make an existing entitlement invisible: the wrong edition installed, and the wrong account signed in.

cscript //nologo %windir%\system32\slmgr.vbs /dlv
cscript //nologo %windir%\system32\slmgr.vbs /ato

1. Run winver and note the edition. An entitlement for Home will not activate a Pro installation, and the machine reports that as no licence at all.
2. Sign in to Windows with the personal Microsoft account the device may have been linked to, then open Settings > System > Activation.
3. If a Troubleshoot option appears, run it while signed in as an administrator and take the option about recently changed hardware if it is offered.
4. If you hold a product key for this machine, install it directly: cscript //nologo %windir%\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX, then /ato.

If the device was never activated before, there is no entitlement to find. The troubleshooter will report the same thing however many times you run it, and each run costs you time rather than telling you anything new.

If the edition or the account was the problem, you can stop here. If neither was, the next section covers how a digital licence is created and what makes one unreachable.

Why it happens

A digital licence comes into existence the first time a machine activates successfully. Microsoft records that this hardware is entitled to this edition of Windows, and from then on the machine can reinstall and reactivate without anyone typing a key. That is why a clean install on a previously licensed machine usually just works, and why it fails so completely when the entitlement was never created in the first place.

Two things break the match, and only one of them is about hardware. Change enough components, particularly the system board, and the identifier no longer resolves to the stored record. The other is edition: the entitlement covers a specific one, so installing Pro on a device entitled to Home produces this error while the hardware sits untouched and the licence still exists. Microsoft’s troubleshooter documentation lists both of those edition mismatches explicitly as cases it handles.

Linking a Microsoft account adds a second way to find the entitlement, and it is the only thing that makes recovery after a hardware change possible at all. Microsoft’s guidance is that the link has to be in place before the change. Without it the licence can only be found by hardware identifier, and once the hardware moves the record becomes unreachable even though it still exists.

Only 0x803F7001 is published. The other five codes in this record are not, including 0x803F7000, which turns up in Microsoft Store licence-acquisition contexts as well as activation ones. Treat them as symptoms that arrived alongside the real error rather than as separate diagnoses.

Full reference

What the troubleshooter is documented to handle

Three requirements sit behind all of those and are the usual reason the troubleshooter reports nothing: you must be signed in as an administrator, the machine must have an internet connection, and the entitlement must be on the account you are signed in with. The Troubleshoot option only appears at all while Windows is unactivated, so if you cannot find it, Windows already considers itself activated and something else is wrong.

Is the licence recoverable?

Commands that answer the question faster than the troubleshooter

Installing a key with slmgr /ipk and activating with /ato will usually tell you more than the troubleshooter does, because it returns a specific code. The troubleshooter is built to reapply a digital licence, and everything outside that job it reports as a generic failure.

Before you conclude there is no entitlement

• Give a fresh installation some online time before deciding. Digital licences are not always applied at the first boot, and there is no published figure for how long to wait, so leave it connected rather than counting hours.
• Sign in with every personal Microsoft account that has ever been used on the machine. Entitlements are per account and people forget which one they used.
• Check the firmware for a key on a machine that shipped with Windows preinstalled.
• Check the edition once more. It is the single most common reason a licence that exists cannot be found.
• If the machine is managed by an organisation, ask whoever administers it. Activation may be handled centrally and nothing you do locally will change it.

Link the account while the machine is still activated

Once this machine is licensed, link the Microsoft account from the activation page. Microsoft’s guidance is explicit that the link must exist before the hardware changes, because it is what the troubleshooter searches afterwards. Linking after a rebuild cannot create an entitlement that was never recorded, so it is one of those small jobs that is either done in advance or not at all.

Every code this article covers

Confirm the fix worked

1. Settings > System > Activation reports Windows as active.
2. slmgr /dli reports Licence Status: Licensed.
3. The activation page names the licence type – digital licence or product key – that you expect.
4. The Microsoft account is linked on that page, so this entitlement can be recovered after a future hardware change.

Questions people ask about this