What the error means
0xC004F074 means the PC tried to activate through a Key Management Service (KMS) host and could not get a working answer from any of them. KMS is the activation method organizations use for volume-licensed Windows: instead of contacting Microsoft, each PC activates against a KMS host on the company network. Microsoft's activation error reference describes the cause as all the KMS hosts the client tries to contact returning errors.
Two groups of people see this code, for different reasons.
- Home users and small offices. Microsoft's consumer activation page says you might see it if you entered a product key for the Enterprise edition to activate Windows 11 Home or Pro. The fix there is a key that matches the edition you have, not network troubleshooting.
- Work devices and IT admins. A company laptop shows it when it cannot reach the KMS host, for example when it is away from the workplace network, or when something is wrong with the KMS host, the network path or the DNS record that points clients to it.
Common causes
- An Enterprise or volume license key on a Home or Pro installation.
- A work device that is not connected to the workplace network.
- The Software Protection service (
sppsvc) stopped on the KMS host. - TCP port 1688 blocked between the client and the KMS host.
- An incorrect or old
_VLMCSSRV record in DNS pointing to a retired KMS host. - A clock difference of more than 4 hours between client and KMS host, which shows as 0xC004F06C in the event details.
How to fix it
1. On a personal PC, enter a key that matches your edition
Open Start, Settings, System, Activation on Windows 11, or Start, Settings, Update & Security, Activation on Windows 10. Select Change product key and enter the 25-character key for the edition installed, which is usually Home or Pro. Your key is normally in the purchase confirmation email, in the device packaging, or on the Certificate of Authenticity sticker.
2. On a work device, connect to the workplace network
Microsoft's consumer page says the error appears when a work device is not connected to the workplace network. Connect and let activation retry. If it still fails while connected, contact your IT support team rather than changing keys yourself.
3. For admins: read event 12288 and check the clock
Open the Application Event Log on the client and find each event with ID 12288 for the activation attempt. The Info field shows the result code and the KMS host and port it tried. If it shows 0xC004F06C, the client and host clocks differ by more than 4 hours. KMS uses UTC, so the time zone does not matter. Resync the client:
w32tm /resync4. For admins: confirm the KMS host is running and reachable
On the KMS host, check that the sppsvc service is running and start it if it is stopped. From the client, test the activation port:
Test-NetConnection -ComputerName <KMS Host Server> -Port 1688If TcpTestSucceeded is False, port 1688 is blocked somewhere between the two and must be opened.
5. For admins: fix the KMS DNS record
In DNS Manager, open the _tcp folder under your domain and check that the _VLMCS SRV record names the current KMS host. Then check that host's A record has the right IP address. If DNS cannot be fixed straight away, Microsoft documents pointing a client at the host directly, then retrying activation from an elevated prompt:
slmgr.vbs /skms <kms_host_name>
slmgr.vbs /atoIf nothing works
On Windows 7 or Windows Server 2008 R2 clients, Microsoft notes that older KMS hosts on Windows Server 2003 or 2008 need an update before they can activate them. If your organization has no KMS host at all, Microsoft's activation reference suggests installing a Multiple Activation Key (MAK) and activating again. Home users who cannot find a matching key can buy a license from the Microsoft Store link on the Activation page.
What we checked
On 2026-11-19 we read three Microsoft pages that list 0xC004F074: the Microsoft Learn article dedicated to the code, the Learn activation error reference for IT pros, and the consumer activation errors page on support.microsoft.com. We also read Microsoft's Slmgr.vbs options page for the /skms and /ato syntax; it does not mention the code. The dedicated article covers the event logs, time sync, sppsvc, port 1688 and DNS records, and the consumer page covers mismatched Enterprise keys and work devices off the network. We did not reproduce the error.
Last checked: 2026-11-19.