About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A server or PC on volume licensing shows that Windows is not activated. Running slmgr /ato returns:
Error: 0xC004F074 The Software Licensing Service reported that the product could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.
Microsoft also lists a shorter form of the same code: 0xC004F074 with the description "The Key Management Server (KMS) is unavailable" (Microsoft Learn, Error 0xC004F074 when you try to activate Windows).
What you see
- The activation error above, from Settings or from
slmgr /ato. - On the client, in the Application event log, event 12288 from source Microsoft-Windows-Security-SPP, saying the client sent an activation request to the KMS host. The Info line shows the KMS host name and port 1688, and may start with a second code such as 0xC004F06C.
- On the KMS host, in the Key Management Service event log, event 12290 from Microsoft-Windows-Security-Licensing-SLC, "An activation request has been processed", when the request did reach the host.
Why it happens
Computers running volume-licensing editions of Windows are KMS clients by default. They find a KMS host on the local network through DNS and connect to it on TCP port 1688. The host publishes a DNS service (SRV) record so clients can find it without any setup (Microsoft Learn, Key Management Services (KMS) activation planning).
Microsoft's troubleshooting page gives five causes, in two groups.
The client could not reach a KMS host at all:
- The Software Protection Platform service (sppsvc) on the KMS host has stopped.
- TCP 1688 traffic is blocked between the client and the host.
- The _VLMCS SRV record in DNS points to a wrong or old KMS host, or the host's A record has the wrong IP address.
The client reached the host, but the host could not activate it (the "KMS is unavailable" form, with the request visible in both event logs):
- The host is too old for the client. Microsoft's planning page says a KMS host may need Windows updates before it can activate a newer version of Windows, and lists the minimum update for each pairing.
- The clocks differ by more than four hours. Microsoft says the 0xC004F06C code in the event Info may appear when the client's and host's system times differ by more than 4 hours. Microsoft's error code list gives its meaning: the KMS "determined that the request timestamp is invalid". The comparison uses UTC, so the time zone setting does not matter.
How to prove the cause
Work from the client towards the host.
1. Read the client's event 12288. It names the KMS host the client tried and the port. It follows that if the name is an old or retired server, the DNS record is the first suspect. If the Info line starts with 0xC004F06C, check the clocks.
2. Test the port from the client. Microsoft's example:
Test-NetConnection -ComputerName <KMS Host Server> -Port 1688
If TcpTestSucceeded is False, port 1688 is blocked between the client and the host.
3. Check the service on the host. Confirm the Software Protection Platform service (sppsvc) is running on the KMS host.
4. Check the DNS record. In the DNS management console, open the _tcp folder under your domain, find the _VLMCS SRV record and check it names the correct KMS host. Then check that host's A record has the right IP address.
5. Compare the clocks. Compare the client's and host's time in UTC, not local time.
6. Check the version pairing. Find the host's Windows version and the client's. Look up the pairing in the planning page's "KMS host required updates" table. For example, Microsoft lists KB5034765 or later for a Windows Server 2022 host to activate Windows Server 2025, and KB5003638 or later for a Windows Server 2016 host to activate Windows Server 2022 or 2019.
The fix
- Service stopped: start
sppsvcon the KMS host. - Port blocked: open TCP 1688 between client and host, then repeat the
Test-NetConnectiontest. On the host itself, Microsoft's setup page shows the built-in firewall rule being enabled, here for the Domain and Private profiles only (Microsoft Learn, Create a Key Management Services (KMS) activation host). First read the rule as it stands, without changing it, because the command below sets its profiles to exactly the ones named and would narrow a rule already set wider:
Get-NetFirewallRule -Name SPPSVC-In-TCP | Format-List Name,Enabled,Profile
Then, if it needs changing:
Set-NetFirewallRule -Name SPPSVC-In-TCP -Profile Domain,Private -Enabled True
It follows that if the host's network has been classed as Public, a rule limited to Domain and Private will not let clients in.
- Wrong DNS record: correct the
_VLMCSSRV record or the host's A record so they point to the current KMS host. If your DNS does not accept dynamic updates, Microsoft says to create the SRV record by hand: service_vlmcs, protocol_tcp, priority 0, weight 0, port 1688, host name the KMS host's full name. Microsoft also says to turn off automatic publishing on every KMS host in that case, so failed publishing events do not fill the logs. - Clock difference: synchronise the client and host from the same time source. Microsoft recommends an NTP source or Active Directory, and gives this command to resynchronise the client:
w32tm /resync
- Host too old: install the update the planning page lists for that pairing on the KMS host, or a later cumulative update. Microsoft says the listed updates are the minimum, and to install the latest available.
Then activate the client again with slmgr /ato.
How to confirm the fix
slmgr /atoon the client completes without the error.- A new event 12288 appears on the client, and a matching event 12290 appears in the host's Key Management Service log, without the 0xC004F06C code in the Info.
Test-NetConnectionto the host on port 1688 showsTcpTestSucceeded : True.
What to watch afterwards
- Renewal, not only first activation. Microsoft says KMS activations last 180 days, and clients try to renew every seven days by default. It follows that a KMS host that has been unreachable for a while may show no symptom until clients start to fall out of activation.
- Replacing or renaming the KMS host. The old SRV record is the documented cause of clients looking in the wrong place. Check DNS whenever the host changes.
- New Windows versions. Before the first server or PC on a newer version joins, check the host has the update the planning page lists.
- Clocks. A host or client whose clock drifts by hours will start failing again.
- One host only. Microsoft recommends at least two KMS hosts if you have more than 50 clients, in case one becomes unavailable.
Read next
Related articles you may want next.
- HostingLicence and activation services as day-to-day availability dependenciesHow KMS, volume activation and ISV licence endpoints affect hosted application uptime during normal operations—not only after a disaster restore.Read article
- TroubleshootingClock Drift in VMware-Hosted Windows: Trace the SourceTrace Windows domain time and VMware synchronisation events so authentication incidents and misleading timestamps can be investigated correctly.Read article
- TroubleshootingFirewall Rules Stopped After a Move? Check the ProfileServices refused after a Windows server move? Read each connection's network category, trace why domain detection failed and fix that, not the rules.Read article
Risks and limits
- The activation threshold is a separate condition. Microsoft's planning page says clients activate only once the host has counted enough recent unique computers: 25 for Windows clients, five for servers and volume editions of Office, counted over 30 days. The 0xC004F074 troubleshooting page does not list this as a cause of 0xC004F074, so it is not treated as one here. A client held back by the count shows its own code, 0xC004F038, which Microsoft's activation error code list describes as "The count reported by your Key Management Service (KMS) is insufficient" (Microsoft Learn, Troubleshoot Windows activation error codes).
- Microsoft's worked example is older. The "KMS is unavailable" section is written around Windows 7 and Windows Server 2008 R2 clients and Windows Server 2003 or 2008 hosts. The causes still apply. For current versions, use the planning page's update table.
- A KMS host on a Windows client can activate only Windows client computers, not servers, according to Microsoft. It follows that a server failing against a host running a client version of Windows needs a Windows Server host.
- The host key matters. Microsoft's setup page says the clients a host can activate depend on the host key used. Changing the host key or reactivating the host is outside this article.
Sources
- Microsoft Learn, "Error 0xC004F074 when you try to activate Windows", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/licensing-and-activation/error-0xc004f074-activate-windows
- Microsoft Learn, "Key Management Services (KMS) activation planning for Windows Server", last updated 17 March 2025: https://learn.microsoft.com/en-us/windows-server/get-started/kms-activation-planning
- Microsoft Learn, "Create a Key Management Services (KMS) activation host", last updated 14 April 2025: https://learn.microsoft.com/en-us/windows-server/get-started/kms-create-host
- Microsoft Learn, "Troubleshoot Windows activation error codes", last updated 12 February 2026: https://learn.microsoft.com/en-us/windows-server/get-started/activation-error-codes
Next step
Error 0xC004F074 means the client did not get an answer it could use from a KMS host: check the host's service, port 1688, the DNS record, the clocks and the host's updates, in that order. NetLeverage has looked after business servers since 2002. If activation still fails, talk to us through managed support with the client's event 12288 text and the KMS host's Windows version.
This article was originally published on .