Windows Activation Error 0xC004F074 ("No KMS Could Be Contacted")? Fix the Real Cause

Activation fails with 0xC004F074: “The Software Licensing Service reported that the product could not be activated. No Key Management Service (KMS) could be contacted.” (often right after slmgr /ato).

Why “buy a new key” is the wrong move: content farms tell you to re-enter or buy a product key. But 0xC004F074 is a connectivity/host problem — the KMS client can’t reach a working KMS host. A new key fixes nothing. Check these, in order.

Fix 1: Confirm the KMS host is actually serving

On the KMS host server:

• The Software Protection service (sppsvc) must be Running.
• It must have an activated KMS host key and met the activation threshold (25 clients for Windows, 5 for servers).

Fix 2: Make sure TCP 1688 is reachable

KMS uses TCP 1688. From a client:

Test-NetConnection <kms-host> -Port 1688

If it fails, open TCP 1688 on the host’s firewall and anything between client and host.

Fix 3: Fix time skew

KMS activation fails if the client/host clocks differ by more than ~4 hours. On the client:

w32tm /resync

Set Set time automatically (and correct time zone) on both ends.

Fix 4: Fix DNS discovery (or point the client directly)

Clients find KMS via the _VLMCS._TCP SRV record in DNS. If that record is missing or points at a dead host:

• Confirm the host auto-publishes (or recreate the SRV + host A record), or
• Point the client straight at the host:

  slmgr /skms <kms-host>:1688
  slmgr /ato

FAQ

No KMS host at all? Then either stand one up, or switch the machine to a MAK key (slmgr /ipk <MAK> then slmgr /ato) which activates directly with Microsoft — no KMS needed.

Different code: 0x8007007B? That’s specifically the DNS/SRV-record path — see KMS error 0x8007007B.

Sources: Microsoft Learn — Error 0xC004F074 when you activate Windows