Fix it now
These two codes say different things and only one is about your ESU key. 0xC004C020 is the activation server reporting that a Multiple Activation Key has exceeded its limit. 0xC004F074 is a KMS client error – no Key Management Service could be contacted – which on an ESU device usually means the base Windows licence is failing, not the ESU one.
slmgr /dlv
slmgr /ipk <ESU MAK>
slmgr /ato <Activation ID>
- Read the
slmgr /dlvoutput before changing anything. It shows every licence on the machine, so you can see whether the failure belongs to the ESU product or to the base Windows licence. - Confirm the prerequisites. Microsoft documents Windows 10 version 22H2 with KB5066791 or later installed, and then the ESU Licensing Preparation Package, KB5072653, installed after it.
- Install the key and activate with the Activation ID. This is the step most people get wrong: ESU is a separate product, and a bare
slmgr /atoacts on the base Windows licence, which can appear to succeed while the ESU licence is untouched. - Confirm with
slmgr /dlvthat an ESU licence now appears alongside the Windows licence with a licensed status. - If 0xC004C020 comes back, the key has no activations left. Microsoft’s published solution is to request more activations through the Microsoft Licensing Activation Centers rather than to keep retrying.
- For a machine with no internet path, use the documented offline route:
slmgr /dti <Activation ID>to get the installation ID, thenslmgr /atp <Confirmation ID> <Activation ID>.
Microsoft publishes one Activation ID per ESU year: Year 1 is f520e45e-7413-4a34-a497-d2765967d094, Year 2 is 1043add5-23b1-4afb-9a0f-64343c8f3f8d, Year 3 is 83d49986-add3-41d7-ba33-87c7bfb5c0fb.
If slmgr /dlv shows the ESU licence as licensed and updates install, you are done. If not, the next section separates the entitlement problem from the activation path problem.
Why it happens
Extended Security Updates are a separate licensed product that sits alongside the Windows licence on the machine. That single fact explains most of the confusion here. The device has two licences, they activate independently, and a command that acts on one tells you nothing about the other. When the ESU key will not take, the first job is establishing which licence is actually failing.
0xC004C020 is unambiguous and belongs to the ESU key: the activation server reported that the Multiple Activation Key has exceeded its limit. Microsoft’s published cause is that a MAK can, by design, only be activated a limited number of times, and its published solution is to request more activations by contacting the Microsoft Licensing Activation Centers. That is worth knowing, because the intuitive response – buy a second key – is not the documented one.
0xC004F074 is a different animal. Microsoft classes it as a KMS client error and publishes it as the Software Protection Service reporting that the computer could not be activated because no Key Management Service could be contacted. Its documented cause is that all the KMS hosts the client tried returned errors, and its documented solution is to read Event ID 12288 in the Application log and troubleshoot KMS and DNS. On a machine being prepared for ESU, that is normally the base Windows licence looking for a KMS host it cannot reach – a leftover slmgr /skms in an image, or a decommissioned host – rather than anything about the ESU key at all.
Microsoft documents ESU activation with a MAK: install the key with /ipk, activate with /ato and the Activation ID for the year you bought. The Activation ID is not optional decoration. Without it, /ato acts on the default licence, which is why an activation can report success while slmgr /dlv still shows no ESU licence and the machine still gets no updates.
0xC004C031 appears in this article’s code list because people encounter it, and no acceptable source publishes a meaning for it. Searching Microsoft’s documentation returns nothing. Treat it as a rejection from the activation service, look at what slmgr /dlv reports about the key and the product it belongs to, and do not accept any confident definition you find for it elsewhere.
The key has used all its activations
You have this one if 0xC004C020 returns immediately on every device you try, including ones that have never activated before.
- Count the devices you have activated against the entitlement. Rebuilt machines consume activations too, which is the usual reason a pool empties earlier than expected.
- Stop retrying. The code will keep returning while the machines stay unpatched.
- Request more activations through the Microsoft Licensing Activation Centers, which is Microsoft’s published solution for this code.
- Keep a record of which devices consumed activations, particularly any rebuilt during testing.
Activation was run without the Activation ID
You have this one if slmgr /ato reports success and slmgr /dlv still shows no ESU licence, or updates are still refused.
- Run
slmgr /atowith the Activation ID for the ESU year you hold, not on its own. - Check
slmgr /dlvafterwards for an ESU entry with a licensed status alongside the Windows licence. - If the ESU licence is absent entirely, reinstall the key with
slmgr /ipkand repeat with the Activation ID.
The base licence is chasing a KMS host
You have this one if 0xC004F074, and slmgr /dlv names a Key Management Service machine, often one set years ago in an image.
- Read Event ID 12288 in the Application log, which is Microsoft’s published starting point for this code; it records each activation attempt.
- Clear a pinned host with
slmgr /ckmsif the machine should be using DNS discovery or is not a KMS client at all. - Fix the base Windows activation before worrying about ESU, because a machine whose Windows licence cannot activate is not in a state to be diagnosed for anything else.
- Then install the ESU key and activate it with its Activation ID.
The device cannot reach the activation service
You have this one if 0xC004F074 or a timeout on machines with no direct internet path, or behind a proxy that inspects traffic.
- Check the proxy the system account uses:
netsh winhttp show proxy. It is not the browser’s. - Have the published activation endpoints allowed through, including
activation.sls.microsoft.com,activation-v2.sls.microsoft.com,validation.sls.microsoft.com,validation-v2.sls.microsoft.com,crl.microsoft.com,login.live.comand thelicensing,purchaseanddisplaycataloghosts undermp.microsoft.com. - For genuinely isolated machines use the documented offline route with
slmgr /dtiandslmgr /atp. - Retry and read the result rather than assuming it worked.
The prerequisites are not in place
You have this one if The key will not install, or installs and then refuses to activate, on a machine that is behind on updates.
- Confirm the build with
winver. Microsoft documents Windows 10 version 22H2 for this programme. - Install KB5066791 or a later cumulative update, restarting as required.
- Install the ESU Licensing Preparation Package, KB5072653, after it. The order is documented and matters.
- Install the key and activate again with the Activation ID.
Windows 10 Long Term Servicing releases, LTSB and LTSC, have their own lifecycles and are not covered by this ESU programme.
Full reference
The commands, and what each is for
| Command | What it does |
|---|---|
slmgr /dlv |
Detailed licence information for every licence on the machine, including ESU |
slmgr /ipk <ESU MAK> |
Installs the ESU product key |
slmgr /ato <Activation ID> |
Activates that specific product online |
slmgr /dti <Activation ID> |
Returns the installation ID for offline activation |
slmgr /atp <Confirmation ID> <Activation ID> |
Applies a confirmation ID obtained offline |
slmgr /ckms |
Clears a pinned KMS host and restores DNS discovery |
The Activation IDs Microsoft publishes
| ESU programme | Activation ID |
|---|---|
| Win10 ESU Year 1 | f520e45e-7413-4a34-a497-d2765967d094 |
| Win10 ESU Year 2 | 1043add5-23b1-4afb-9a0f-64343c8f3f8d |
| Win10 ESU Year 3 | 83d49986-add3-41d7-ba33-87c7bfb5c0fb |
Use the one matching the year you have bought. ESU is sold by year, and the Activation ID is how the machine knows which entitlement it is activating.
Telling the two failures apart
| What you see | What it means |
|---|---|
| 0xC004C020 immediately on activation | The key’s activation pool is exhausted |
0xC004F074 and slmgr /dlv names a KMS host |
The client is asking a KMS host for something, and not reaching it |
| 0xC004F074 on an isolated machine | Nothing reachable to activate against; use the offline route |
| The key will not install at all | Prerequisites missing, or the key does not match the product |
| Activation succeeds but updates are still refused | Check the build is 22H2 and the preparation package is installed |
What ESU does and does not cover
Microsoft describes the programme as enabling PCs to keep receiving critical and important security updates through an annual subscription after support ends. It explicitly does not include new features, customer-requested non-security updates, design change requests, or general technical support – support is limited to licence activation, installation, and regressions of the ESU updates themselves. It runs for up to three years after the end of support date of 14 October 2025, and devices must be running Windows 10 version 22H2. Long Term Servicing releases are not covered.
Where the entitlement can come from
- Volume licensing, with a minimum purchase of one licence, priced per device per year and rising each consecutive year for up to three years.
- Cloud and virtualisation services at no additional cost, including Windows 365, Azure Virtual Desktop, Azure virtual machines, Azure Dedicated Host, Azure VMware Solution, Azure Local and Azure Stack.
- A consumer enrolment route for individuals rather than organisations.
- Check which of these you are actually on before troubleshooting a key: a device covered through a cloud service does not need the MAK route at all.
When a licence is the actual fix
This is one of the few Windows errors where a purchase genuinely is part of the fix, so it is worth being precise about which purchase. 0xC004C020 means the key you hold has been activated as many times as it is allowed. Microsoft’s published answer is to request more activations through the Microsoft Licensing Activation Centers, and that should be your first move rather than buying a second key – the entitlement you already own may simply need its activation limit raised. Where you genuinely have more devices than entitlement, additional Windows 10 ESU coverage is what keeps those machines receiving security updates; it is sold per device per year through volume licensing with a minimum of one licence, and the price rises each consecutive year for up to three years, which is a deliberate signal about how long this is meant to be a bridge. Before buying anything, check two things: whether the machines are already covered through a cloud or virtualisation service, where ESU is included at no additional cost, and whether the failing device could simply be moved to Windows 11 instead, which ends the problem rather than deferring it. And be sure the code you have is 0xC004C020 – if it is 0xC004F074, no purchase helps, because that one is a KMS path problem.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004C020 |
The activation server reported that the Multiple Activation Key has exceeded its limit; Microsoft’s solution is to request more activations | Microsoft Learn |
0xC004F074 |
The Software Protection Service reported that the computer could not be activated: no Key Management Service could be contacted. Microsoft classes it as a KMS client error | Microsoft Learn |
0xC004C031 |
Seen when the activation service rejects a key; no acceptable source publishes a meaning, so read what slmgr /dlv reports about the key rather than the code | not published by the vendor |
Confirm the fix worked
slmgr /dlvshows an ESU licence alongside the Windows licence, with a licensed status.- The base Windows licence also reports licensed, with no stale KMS host named.
- Windows Update offers security updates and they install.
winverconfirms the machine is still on Windows 10 version 22H2.- You have recorded which devices consumed activations, so the next 0xC004C020 is explainable rather than a surprise.
Questions people ask about this
Why did activation appear to succeed but nothing changed?
Almost certainly because slmgr /ato was run without the Activation ID. ESU is a separate product; a bare /ato acts on the base Windows licence and can report success while the ESU licence was never touched. Run it with the published Activation ID for your ESU year and check slmgr /dlv afterwards.
Does 0xC004F074 mean my ESU key is bad?
No. It is a KMS client error meaning no Key Management Service could be contacted. On an ESU device it usually means the base Windows licence is looking for a KMS host it cannot reach. Fix that first; the ESU key is a separate question.
Can I use one ESU key across a whole estate?
Within its activation limit, yes – it is a Multiple Activation Key. Once the limit is reached you get 0xC004C020, and Microsoft’s published answer is to request more activations rather than to source another key.
Does ESU keep the machine supported in general?
No, and this is worth saying to whoever is paying for it. Microsoft publishes ESU as critical and important security updates only. It excludes new features, non-security updates, design change requests and general technical support; support covers licence activation, installation and regressions in the ESU updates themselves.
What does 0xC004C031 mean?
Nothing that any acceptable source publishes. Read what slmgr /dlv says about the key and the product it belongs to, confirm the prerequisites and the edition, and treat any definitive-sounding explanation you find elsewhere with suspicion.
