KMS Activation Error 0x8007007B ("DNS Name Does Not Exist")? Fix the SRV Record

Windows or Windows Server fails to activate with 0x8007007B — “DNS name does not exist.”

Why a reinstall or new key won’t help: the actual cause is that the KMS client can’t locate a KMS host in DNS. KMS clients auto-discover the host through the _VLMCS._TCP SRV record; if that record is missing (no KMS host published, or DNS issue), you get 0x8007007B. Re-entering a product key does nothing for a DNS lookup.

Fix 1: Confirm a KMS host exists and publishes SRV records

On the KMS host:

• It has an activated KMS host key and sppsvc is running.
• It auto-publishes its SRV record (default). Verify from a client:

  nslookup -type=srv _vlmcs._tcp.<your-dns-domain>

  You should see the KMS host returned. If nothing comes back, the record is missing.

Fix 2: Point the client directly at the host

If DNS discovery is the problem (or there’s no domain), bypass it:

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

This hard-codes the KMS host so no SRV lookup is needed.

Fix 3: Recreate the SRV record (host side)

If the host should auto-publish but isn’t, ensure DNS allows it (or add the _VLMCS._TCP SRV + the host’s A record manually), then on the host:

slmgr /ato

to re-register/publish.

Fix 4: No KMS infrastructure? Use a MAK

For a single machine or a tiny environment with no KMS host, a MAK key activates directly against Microsoft:

slmgr /ipk <MAK-key>
slmgr /ato

FAQ

0x8007007B vs 0xC004F074? 0x8007007B = the client can’t find a KMS host (DNS/SRV); 0xC004F074 = it found one but couldn’t contact/activate against it (port, time, service). For the latter see KMS error 0xC004F074.

Sources: Microsoft Learn — Troubleshoot volume activation error codes