Fix it now
The Software Protection service is refusing the key you are installing. Three things account for nearly all of it: the prompt is not elevated, the prerequisite updates that teach the machine about ESU are not installed yet, or the key is not the ESU key for this device and edition.
slmgr /ipk <ESU-product-key>
slmgr /ato <ESU-activation-id>
slmgr /dlv All
- Elevation is not optional here. Microsoft states that
slmgr /ipkmust be run from an elevated Command Prompt window, and a non-elevated attempt is one of the ways a key installation fails without a useful explanation. - Install the prerequisites first if you have not: the machine must be on Windows 10 version 22H2 with KB5066791 or later, then the ESU Licensing Preparation Package KB5072653 installed after it.
- Activate the ESU product specifically by passing its activation ID to
slmgr /ato. Runningslmgr /atowith no argument activates the base licence, not the ESU one. - Read
slmgr /dlv Alland find the ESU entry rather than the Windows one. That is the line that has to say Licensed.
If the machine has no route to the internet, use the documented offline path instead: slmgr /dti to get the installation ID, obtain a confirmation ID, then slmgr /atp <confirmation-id> <activation-id>.
If the ESU licence reports as Licensed you can stop here. If not, the next section covers what the two codes are really saying and where the entitlement chain breaks.
Why it happens
Extended Security Updates are delivered as a separate licence layered on top of the Windows licence the machine already has. The device keeps its ordinary Windows activation and gains a second product, with its own key, its own activation ID and its own status line. That is why a machine can report Windows as perfectly activated and still receive nothing: the ESU product next to it is not licensed, and the update service checks that product before offering ESU content.
0xC004F050 is the Software Protection service reporting that the product key is invalid. Microsoft lists it against MAK, KMS and KMS client activation, which is a useful hint: it is a generic key rejection rather than something specific to ESU. A key can be invalid because it is genuinely the wrong key, because it is the right key for a different edition, or because the machine has no idea what product the key is for, which is what the preparation package exists to fix.
0xC004F025 has no published meaning. Microsoft does not define it anywhere, and the explanation usually attached to it, that it means access denied, is not sourced from vendor documentation. What is documented, and what makes the point without inventing anything, is that key installation requires an elevated Command Prompt. Run it elevated. If the code goes away, the elevation was the problem, and you have not had to guess what the code meant to get there.
The prompt is not elevated
You have this one if The key installation fails immediately, and the same command run from an administrative session works.
- Open Command Prompt with Run as administrator, not a standard window.
- In a remote session, confirm the session is elevated rather than assuming it inherits.
- Retry
slmgr /ipk <key>, then checkslmgr /dlv All.
This is worth ruling out first precisely because it is free and it is documented, whereas the code’s meaning is not.
The machine does not yet know what an ESU key is
You have this one if 0xC004F050, on a machine that has not had the preparation updates installed.
- Confirm the machine is on Windows 10 version 22H2.
- Install KB5066791 or later, then restart.
- Install the ESU Licensing Preparation Package KB5072653 after it, in that order.
- Retry the key installation.
Order matters. The preparation package is what makes the licensing platform recognise the ESU product, so installing it before the cumulative update leaves the chain incomplete.
The key is the wrong one for this device
You have this one if 0xC004F050 persists after the prerequisites are in place and the prompt is elevated.
- Check that the key is an ESU key rather than a Windows key. They are different products and the machine treats them as such.
- Check the edition it was issued for, and the year of coverage it grants.
- Confirm the key has not exhausted its activation count, if it is a multiple activation key.
- Obtain the correct key from whoever holds the agreement rather than reusing one from another estate.
The key installs but the ESU product is never activated
You have this one if No error at all, and updates still do not arrive.
- Run
slmgr /dlv Alland read every product, not just the first. - Activate the ESU product by its own activation ID:
slmgr /ato <ESU-activation-id>. - Where the device is offline, use
slmgr /dtiandslmgr /atpinstead. - For a large estate, use volume activation tooling to proxy-activate rather than visiting machines.
Full reference
The commands, and what each one is for
| Command | What it does |
|---|---|
slmgr /ipk <key> |
Installs a product key. Must be run from an elevated Command Prompt window |
slmgr /ato [<activation-id>] |
Activates. With an activation ID it activates that product specifically |
slmgr /dlv [<activation-id> | All] |
Detailed licence information. All lists every installed product |
slmgr /dti [<activation-id>] |
Displays the installation ID for offline activation |
slmgr /atp <confirmation-id> <activation-id> |
Activates with a confirmation ID obtained offline |
slmgr /upk [<activation-id>] |
Uninstalls a product key, which is how you remove a key installed in error |
The activation ID is what separates a working ESU deployment from a confusing one. Passing no ID means the command acts on the base Windows licence, which is already activated and will happily report success while ESU remains unlicensed. Every ESU year has its own activation ID, so the ID you use has to be the one for the coverage year you bought.
Why the machine can be activated and still get nothing
Licensing and update offering are two separate systems, and ESU makes the gap between them visible. The update service asks the licensing platform whether this device holds a valid ESU entitlement, and offers ESU content only if the answer is yes. A machine with a perfectly healthy Windows licence and no ESU product installed answers no, and the update scan completes normally with nothing to show for it.
That is why slmgr /dlv All is the command in this article that matters most. It is the only one that shows you both products at once, and the ESU line is the one that has to read Licensed.
Offline and large-estate activation
- For a single disconnected machine,
slmgr /dtiproduces an installation ID, which is exchanged for a confirmation ID, whichslmgr /atpapplies. - For an estate, volume activation tooling can proxy-activate machines that have no internet route of their own, which avoids handling installation IDs by hand.
- Whichever route you take, the activation ID for the ESU product still has to be specified. Offline activation does not remove that requirement.
- Keep a record of which machines hold which coverage year. The commonest ESU failure at renewal is nobody knowing which devices were done last time.
What to check when the key still will not install
- Confirm the build with
winver. The prerequisites are version-specific and a machine on an older version will not take the key. - Confirm the Software Protection service is running, since every command here goes through it.
- Remove a key installed in error with
slmgr /upkbefore installing another, so you are not diagnosing two products at once. - Check whether a policy or management tool is re-applying a different key after yours, which produces a failure that appears and disappears.
- On a domain-joined machine, rule out an activation policy pointing the device at a service that has nothing to do with ESU.
When a licence is the actual fix
This is one of the articles where a licence genuinely is the fix, but only after the technical causes are ruled out. If the prompt was not elevated, or the preparation updates were missing, you already have what you need and buying another key changes nothing. If the machine has no ESU entitlement at all, no command in this article will produce one: the device is out of servicing and the update service has nothing to offer it. Arco supplies Windows 10 ESU entitlements and will check first whether the machine can simply be upgraded to a supported build instead, because that route is usually cheaper and it does not expire.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F050 |
The Software Protection service reported that the product key is invalid. Microsoft lists it against MAK, KMS and KMS client activation | Microsoft Learn |
0xC004F025 |
Seen when a key installation is refused. Microsoft publishes no meaning for it, so start from the documented requirement that key installation needs an elevated Command Prompt | not published by the vendor |
Confirm the fix worked
slmgr /dlv Alllists the ESU product and reports its licence status as Licensed.- The activation ID shown against that product is the one for the coverage year you bought.
- An update scan offers ESU content, or reports the machine as up to date rather than failing.
- The base Windows licence still reports as Licensed, confirming nothing was disturbed.
Questions people ask about this
What does 0xC004F025 mean?
Microsoft does not publish a meaning for it. You will find pages asserting it is an access denied condition, which is plausible but unsourced, and acting on an unsourced meaning is how people end up changing the wrong thing. What is documented is that key installation requires an elevated Command Prompt window, so try that first. It is free, it takes ten seconds, and it resolves a good proportion of these.
Do I install the ESU key on top of the Windows key or instead of it?
On top. ESU is a separate product with its own key and activation ID, and the machine keeps its ordinary Windows licence alongside it. That is why slmgr /dlv All matters: you need to see both products, and the ESU one is the one that has to say Licensed.
I ran slmgr /ato and it said it succeeded, but no updates arrive.
Almost certainly because it activated the base Windows licence rather than the ESU product. Without an activation ID, the command acts on the default product, which was already activated. Pass the ESU activation ID explicitly and check the result with slmgr /dlv All.
Is ESU a substitute for upgrading?
No, and it is not sold as one. It delivers security updates for a defined period on a build that has left ordinary servicing, and it stops when that period ends. It is useful for buying time on hardware or software you cannot move yet. Where the machine can take a supported build, the upgrade is the better answer and it does not have a renewal date attached.
