0x803FA071: Digital Licence Has Hit Its Unlock Limit at Microsoft

Fix it now

Microsoft documents 0x803FA071, with 0xC004C008 and 0xC004C770, as the product key having been used on more devices than the licence terms allow. Its documented actions are to buy a separate key for each device, or to contact support for an exception where the trigger was a hardware change. Work out which of those you are before spending anything.

cscript //nologo %windir%\system32\slmgr.vbs /dli

1. Count the distinct machines this key has activated. Reimaging one computer repeatedly is not the same as using it on several.
2. Read the channel in the /dli output. A retail key covers one device at a time; a volume MAK carries a defined pool of activations sized to the agreement it came from.
3. If the trigger was a hardware change on a single machine rather than a genuine second device, contact Microsoft support about an exception before you buy anything. That route is documented for this code.
4. If it is a volume MAK, ask whoever administers the agreement how many activations remain before assuming the key is finished.

Stop attempting activation on further machines while you work this out. Repeated failures achieve nothing and can add a second, unrelated error on top.

If an exception or a spare activation covers it, you can stop here. If there are genuinely more computers than licences, the next section covers how many you actually need.

Why it happens

Each activation request carries a hardware identifier, and when a key activates a machine that identifier is recorded against the key. If the same machine reinstalls Windows later it presents the same identifier and re-uses its existing activation rather than spending a new one, which is why rebuilding a single computer repeatedly does not exhaust anything. Different computers present different identifiers, and each one costs an activation.

Microsoft’s consumer error list is unusually direct about this code. It groups 0x803FA071 with 0xC004C008 and 0xC004C770, states that the product key has been used on more devices than the Microsoft Software Licence Terms allow, and gives two actions: buy a separate product key for each device, or contact support to ask about an exception if the problem followed a hardware change. That second action is worth taking seriously, because it is free and it is the documented route for the most common honest cause.

The other two codes in this record are not published, so no meaning can be given for them. What can be said is that they appear in the same part of the licensing flow, and that the diagnosis is the same either way: count the machines, read the channel, and compare that with what you bought.

Full reference

The documented limits, and which key type they apply to

Two things follow from that table. First, the specific numbers Microsoft publishes are for KMS host keys – ten activations across six computers – and not for retail keys or MAKs, whose limits are set by the agreement rather than published. Second, three of the four codes have a documented remedy that is a phone call to Microsoft rather than a purchase. Check which code you actually have before you decide you are short of licences.

How many licences a deployment needs

Where a deployment is large enough for this table to matter, read your own agreement rather than a general rule. Volume agreements differ from each other and from retail terms, and the licensing question is decided by the paperwork rather than by the activation service.

Before you conclude you are short

• Count machines, not installations. Ten rebuilds of one computer is one activation.
• Read the channel. Retail, OEM, MAK and KMS keys behave differently and the advice for each is different.
• Check whether the failing machine is one you have changed hardware on. That is the case with a documented free route.
• Ask the agreement administrator for the remaining count on a MAK before treating it as exhausted.
• Check whether any machine on the list has been decommissioned. Reclaiming activations is supported by some agreements.

Whether removing a key frees an activation

slmgr /upk stops a machine using a licence, and running it on a computer you are retiring is the right thing to do. Whether the count held at Microsoft is released as a result is not something Microsoft publishes, so do not plan a deployment around it. Treat it as good housekeeping rather than as a way to recover a licence, and size your order against the machines you are actually running.

Every code this article covers

Confirm the fix worked

1. slmgr /dli on each newly licensed machine shows a distinct partial key where you expect one.
2. Licence Status reads Licensed on every machine that was previously failing.
3. slmgr /xpr reports permanent activation on each of them.
4. Your licence count matches your machine count, and the invoices are filed with it.

Questions people ask about this