Fix it now
Microsoft publishes 0xC004F042 as the specified Key Management Service not being usable for this product. For Office that almost always means the host was set up for an earlier release and nobody has installed the Volume License Pack and host key for the version you are now deploying. The client is fine; the work is on the host.
slmgr /dlv all
net stop sppsvc
net start sppsvc
- Look for an Office entry naming the version you are deploying. If the newest Office entry names an older release, that is the whole problem.
- Download the Office Volume License Pack for that version. Microsoft names them exactly: Office LTSC 2024 Volume License Pack, Office LTSC 2021 Volume License Pack, Office 2019 Volume License Pack, Office 2016 Volume License Pack.
- Run it on the host. It installs the pack and opens the Volume Activation Tools wizard, which asks for your KMS host key.
- Activate the host key with
slmgr /ato, orslui.exe 4for phone activation if the host has no internet access. - Restart the licensing service so the host republishes, then retry a failing client with
cscript ospp.vbs /act.
Check the host’s operating system before you download anything. Office LTSC 2024 needs a host running Windows Server 2019 or later, and a host serving several Office versions has to support KMS for each of them.
If a previously failing client now activates you are done. If not, the next section covers the four other reasons a host refuses a product.
Why it happens
A KMS host does not hold a general licence to activate Microsoft products. It holds specific entitlements expressed as host keys, each issued against an agreement covering a defined set of products, and it can only issue licences for what its keys and licence files describe. 0xC004F042 is the host answering and declining.
Office adds a moving part that Windows does not have. Before a host can serve a given Office release, the licence files for that release have to be present on it, and they arrive in a downloadable Volume License Pack rather than with Windows. Running the pack installs the files and opens the Volume Activation Tools wizard, which prompts for the matching host key. Skip it and the host answers Office requests with a refusal.
The good news in that arrangement is that the fix happens once, on one machine. You do not touch the clients. Install the pack and the key on the host you already run, restart the licensing service, and every Office client that was failing five minutes ago can activate. Microsoft also states that on a host configured for Office you install and enable only one KMS host key to activate all volume licensed versions of Office, so this is not a key per edition.
Two things do need checking before you start. The host’s operating system has to support KMS for every Office version you want it to serve, which for Office LTSC 2024 means Windows Server 2019 or later. And installing a newer licence pack does not remove the older ones, so a host can serve several Office generations side by side without anything being migrated.
The host has no licence pack for the Office version you are deploying
You have this one if slmgr /dlv all on the host lists an older Office release and nothing newer, while the failing clients run the newer one.
- Confirm the host’s operating system supports KMS for that Office version.
- Download and run the Office Volume License Pack for the version you are deploying.
- Enter the Office KMS host key when the Volume Activation Tools wizard prompts, or install it afterwards with
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX. - Activate the host:
slmgr /ato. - Restart the licensing service:
net stop sppsvcthennet start sppsvc.
Installing a newer pack does not remove the older ones. A single host serves several Office versions side by side.
The licence pack is installed but the host key was never activated
You have this one if The Office entry appears in slmgr /dlv all on the host, its status is not licensed, and no activation count is shown.
- Confirm the host can reach Microsoft’s activation endpoints on TCP 443.
- Run
slmgr /atoon the host and wait for the confirmation. - If the host has no internet access, use phone activation:
slui.exe 4, which Microsoft lists for exactly this case. - Re-run
slmgr /dlv alland confirm the Office entry now reports as licensed.
Clients are reaching a legacy host in a mixed estate
You have this one if Two hosts exist. Clients pinned to the newer one activate; clients using DNS discovery land on the older one and fail.
- On a failing client,
cscript ospp.vbs /dstatusshows which host it last used. - Confirm the diagnosis by pinning it temporarily:
cscript ospp.vbs /sethst:newkms.contoso.local. - Once confirmed, either update the legacy host with the current licence pack or remove its
_vlmcsrecord from DNS. - Return the client to automatic discovery with
cscript ospp.vbs /remhst, which also resets the port to 1688.
The client is not using the generic key for its edition
You have this one if One Office edition activates against the host and another does not, though both are the same release.
- Check what is installed:
cscript ospp.vbs /dstatusshows the product and the last five characters of the key. - Confirm the client carries the Generic Volume License Key published for that exact edition. Microsoft publishes a separate GVLK for Professional Plus and for Standard in each release.
- Remove the wrong key with
/unpkey:, install the correct one with/inpkey:, then/act.
Volume Office installs with the right GVLK by default. A wrong one usually means the build was deployed with a product ID that does not match the licence.
The licensing service was never restarted after the change
You have this one if Everything on the host looks correct and clients keep failing with the code they saw before the pack was installed.
- On the host:
net stop sppsvcthennet start sppsvc. - Confirm the host is listening on 1688 and that the Key Management Service is allowed through Windows Firewall.
- On the client,
ipconfig /flushdns, thencscript ospp.vbs /act.
Full reference
Which variant you have
| What you observe | Where the fault is |
|---|---|
| Older Office versions activate, the newest does not | The host lacks the licence pack or host key for the new release |
| Nothing Office-related activates, Windows does | No Office licence pack has ever been installed on the host |
| The Office entry exists but is not licensed | The host key was installed and never activated |
| One edition activates, another does not | The client is not carrying the GVLK for its edition |
| Nothing changed after the pack was installed | The licensing service was not restarted |
The host-side commands
| Command | What it does |
|---|---|
slmgr /dlv all |
Displays licence information for all applicable installed products, which is where the Office entry either is or is not |
slmgr /ipk <host key> |
Installs the KMS host key after confirming it is applicable |
slmgr /ato |
Activates the host key against Microsoft |
slui.exe 4 |
Phone activation, for a host with no internet access |
net stop sppsvc / net start sppsvc |
Restarts the licensing service so the host republishes |
slmgr /sdns / slmgr /cdns |
Enables or disables DNS publishing by the host. Enabled is the default |
slmgr /cdns turns publishing off. It is the opposite of what you want when clients cannot find the host, and it is an easy misreading of an option list.
Host operating system requirements
Microsoft publishes an operating system requirement per Office version, and a host serving several versions must run an operating system that supports KMS for each of them. Office LTSC 2024 requires Windows Server 2019 or later; Office LTSC 2021 requires Windows Server 2016 or later. A host that is old enough to be running an unsupported server build is a bigger problem than the activation error, and upgrading it is not something to do the same afternoon.
What one host key covers
On a KMS host configured to support volume activation of Office, you install and enable only one KMS host key to activate all volume licensed versions of Office. That is worth knowing before somebody buys a key per edition. What you cannot do is make an entitlement for an older release cover a newer one, because the host key is the entitlement in machine-readable form.
The two companion codes
0xC004F020 and 0xC004F077 have no published descriptions. Both appear in the same exchange, and both are routinely glossed with meanings the vendor has never stated. Read your own machine’s text with cscript ospp.vbs /ddescr: on the client, or slui.exe 0x2a on the host, and interpret it alongside what slmgr /dlv all shows rather than on its own.
Confirming the host before you touch a client
slmgr /dlv alllists an Office entry for the version you deploy, with a licensed status.- The Key Management Service is allowed through Windows Firewall on the host, which is how Microsoft documents opening 1688 for it.
- The licensing service has been restarted since the licence pack was installed.
- The host’s Application log shows Event ID 12294, which is what publishing to DNS successfully looks like.
- Only then retry a client, so a client failure after that means something on the client rather than on the host.
When a licence is the actual fix
No configuration change gives an old host key the right to activate a newer Office release, because the entitlement genuinely is not there. What you need is the KMS host key for the Office version you are deploying, installed on the host you already run, and one key covers all the volume licensed versions of Office that host serves. Arco supplies the Office LTSC 2024 KMS Host Key and can confirm before you buy which host key covers the editions in your estate, so you are not rebuilding activation infrastructure you already have.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F042 |
The Software Protection Service determined that the specified Key Management Service cannot be used for this product | Microsoft Learn |
0xC004F020 |
Seen in the same exchange. No published description | not published by the vendor |
0xC004F077 |
Seen in the same exchange. No published description | not published by the vendor |
Confirm the fix worked
- On the host,
slmgr /dlv alllists the Office version you deploy and reports it as licensed. - The licensing service has been restarted since the licence pack was installed.
- On a previously failing client,
cscript ospp.vbs /actcompletes without an error. cscript ospp.vbs /dstatuson that client reports a licensed status and names the host you expect.- The host’s count for that Office entry climbs as further clients check in.
Questions people ask about this
Do I need a new server for the new host key?
No, as long as the existing one runs an operating system that supports KMS for the Office version you are adding. Install the licence pack and the host key on the host you already have; the older Office versions it serves keep working.
Will a newer licence pack break my older Office clients?
No, provided you leave the existing packs and host keys in place. Each Office version is served from its own licence files on the host, so they coexist.
How many host keys do I need?
Microsoft states that on a host configured to support volume activation of Office you install and enable only one KMS host key to activate all volume licensed versions of Office. What one key cannot do is cover a release it was not issued for.
Can I avoid this by moving to Microsoft 365 Apps?
You would avoid KMS entirely, because those activate against a subscription and a signed-in identity rather than a local host. Whether it costs less is a commercial question rather than a technical one.
Is there any free way to make the old host key work?
No. This is one of the cases where the licence really is the fix. The host key is the entitlement in machine-readable form, and an entitlement for an older release does not cover a newer one.
