How to Fix Windows Activation Error 0xC004F074 (KMS Server Unavailable)

Error 0xC004F074 is the single most common KMS activation failure: the client reports that the Key Management Service is unavailable. The activation request left your machine and never reached a working KMS host. The fix depends on which of four root causes applies. The full error-code catalog with fixes for two dozen related codes is indexed at Windows activation errors.

Cause 1: No KMS Host Configured

By default, KMS clients discover the host through a DNS SRV record (_vlmcs._tcp). If your network has no such record - which is always the case outside enterprise environments - discovery fails silently. Fix it by setting the host manually from an elevated Command Prompt:

slmgr /skms your-kms-host
slmgr /ato

Cause 2: Firewall Blocking Port 1688

KMS communicates over TCP port 1688. If a firewall between client and host blocks it, activation fails with this exact error. Test reachability:

telnet your-kms-host 1688

If the connection fails, open TCP 1688 inbound on the host and outbound on the client path.

Cause 3: KMS Host Below Activation Threshold

A KMS host refuses activation requests until it reaches its minimum count: 25 unique clients for Windows client editions, 5 for Windows Server. A freshly deployed or reset host returns 0xC004F074 until enough distinct machines have contacted it. On the host itself, slmgr /dlv reports the current count.

Cause 4: Wrong or Missing GVLK

If the installed product key is a retail or MAK key rather than the edition's GVLK, the client never attempts KMS activation in the first place. Install the correct key:

slmgr /ipk W269N-WFGWX-YVC9B-4J6C9-T83GX
slmgr /ato

The full key list for every Windows and Office edition is maintained in the GVLK reference.

Verification

After applying the fix, confirm activation with slmgr /xpr (expiration date) and slmgr /dlv (full license channel detail). A healthy KMS activation shows a 180-day expiration and a registered KMS host name.