Error 0xC004F074 means Windows could not complete activation through Key Management Service (KMS). Common causes are:
- The KMS host is unavailable.
- The Software Protection Platform Service (
sppsvc) on the KMS host is stopped. - Network communication to the KMS host is blocked, commonly TCP port 1688.
- DNS points clients to an incorrect or old KMS host.
- The client and KMS host system times differ too much.
- For older environments, a KMS host/client version mismatch can also cause this error.
A practical troubleshooting path is:
- Check the Application Event Log on the client
Look for activation-related events, especially Event ID 12288, and use those errors to guide the next steps. - Verify the KMS host service
On the KMS host, confirm that the Software Protection Platform Service (sppsvc) is running. If it is stopped, start it. - Test network connectivity to the KMS host on TCP 1688
From the client, run:
ReviewTest-NetConnection -ComputerName <KMS Host Server> -Port 1688TcpTestSucceeded:-
True= the port is reachable. -
False= traffic on port 1688 is blocked between the client and the KMS host.
-
- Check DNS configuration for KMS discovery
In DNS Manager:- Open the domain zone.
- Select the
_tcpfolder. - Find the
_VLMCSSRV record. - Verify it points to the correct KMS host.
- Then verify the KMS host’s Host (A) record in the domain zone.
- If the IP address is wrong or outdated, update it to the current KMS host.
- Check time synchronization
If the client time is too different from the KMS host time, activation can fail. Synchronize the client time with the KMS host by using NTP or Active Directory Domain Services. On the client, this command can resync time:
For the older KMS-unavailable scenario in the documentation, a time difference of more than 4 hours can trigger failure.w32tm /resync - Check for KMS host/client version mismatch in older systems
In environments using older KMS hosts such as Windows Server 2003 or Windows Server 2008, newer clients such as Windows 7 or Windows Server 2008 R2 may require host updates before activation succeeds. - If the device is an Azure Windows VM
Additional connectivity checks apply:- Make sure the VM is configured to use the correct Azure KMS endpoint.
- Clear any existing KMS configuration and set the Azure KMS server:
slmgr.vbs /ckms Invoke-Expression "$env:windir\system32\cscript.exe $env:windir\system32\slmgr.vbs /skms azkms.core.windows.net:1688"- Test connectivity:
Test-NetConnection azkms.core.windows.net -port 1688- If the VM uses custom DNS, make sure it can resolve
azkms.core.windows.net. - If outbound traffic is routed through Azure Firewall, add a rule to allow TCP 1688 to the KMS endpoint and verify firewall logs for denies or rule mismatches.
- Forced tunneling, network virtual appliances, or an internal load balancer can block activation traffic if outbound routing is not configured correctly.
- Retry activation
After fixing service, DNS, network, or time issues, run:slmgr /ato
If more data is needed for escalation, collect diagnostics by following Gather information by using TSS for deployment-related issues.
- Error 0xC004F074 when you try to activate Windows
- Error 0xC004F074 when you try to activate Windows
- Error 0xC004F074 when you try to activate Windows
- Troubleshoot Windows activation error codes
- Error 0xC004F074 - "No Key Management Service (KMS) could be contacted"
- Error 0xC004F074 - "No Key Management Service (KMS) could be contacted"
- Error 0xC004F074 - "No Key Management Service (KMS) could be contacted"