Microsoft activation error codes, decoded and fixed in the right order

Activation failures look cryptic but fall into four families: key state, network path, system clock and edition mismatch. Identify the family and the fix is deterministic.

Illustration of a Windows activation error dialog with repair tools

The four error families

Grouping codes stops you from applying a key fix to a network problem.

  • Key state (0xC004C060, 0xC004C003): key blocked, already in use or revoked
  • Edition mismatch (0xC004F210, 0x4004F00C): key does not match the installed SKU or channel
  • Transport (0x80072F8F, 0x8007232B): TLS, DNS, proxy or an incorrect system clock
  • Service (0xC004F074, 0xC004F038): no KMS host reachable or insufficient KMS count

0xC004C060 — key already in use or blocked

The activation server recognises the key but refuses this device. Either the key is genuinely in use elsewhere, or it was flagged after a volume-key abuse report.

  • Confirm the licence channel: slmgr /dli shows the description and partial key
  • Run the Settings › Activation troubleshooter and select your previous device
  • If you bought the key from a reseller, ask them to release the prior activation or issue a replacement
  • Phone activation (slui 4) works for genuine retail keys after a hardware change

0x4004F00C — Office deactivated loop

Office 2021/2024 shows a repeating "product deactivated" prompt, most often after a motherboard change, a tenant sign-out or a stale credential in Windows Credential Manager.

  • Remove all Office credentials in Credential Manager, then sign in again
  • Run an Office Quick Repair, then an Online Repair if the loop persists
  • Clear the licence cache: cscript ospp.vbs /dstatus then ospp.vbs /unpkey:<last5>
  • Re-enter the product key and run ospp.vbs /act

0x80072F8F and 0x8007232B — the transport family

These almost never indicate a bad key. 0x80072F8F is a TLS failure, nearly always a wrong system date or a missing root certificate. 0x8007232B is a DNS failure: the client cannot find a KMS host record.

  • Set time automatically and re-sync: w32tm /resync
  • For MAK activation on Server, install the MAK explicitly instead of the default KMS client key
  • Behind a proxy, allow activation endpoints on 443 and bypass TLS inspection for them
  • Confirm the machine can resolve the _vlmcs._tcp SRV record if KMS is expected

Frequently asked questions

How do I fix Windows activation error 0x80072F8F?
Correct the system clock and time zone, run w32tm /resync, then retry activation. The code is a TLS handshake failure and an incorrect date is the most common cause, followed by a proxy that intercepts TLS to Microsoft's activation endpoints.
What causes Office 2024 error 0x4004F00C?
A stale licence token, usually after a hardware change or an account sign-out. Clear Office credentials in Credential Manager, run an Online Repair, then re-enter and reactivate the key with ospp.vbs.
Is error 0xC004C060 always a fake key?
No. It means the server will not activate this device with that key. Genuine keys hit it after hardware changes or when a previous activation was never released. A blocked key returns it permanently — a reputable seller will replace it.
Which command shows my current licence status?
For Windows, slmgr /dlv gives the full licence detail including channel and partial key. For Office, run cscript ospp.vbs /dstatus from the Office program folder.

Keep reading on this subject

Elsewhere on LicenseVault

Next articleOffice 2024 perpetual vs Microsoft 365: the five-year cost, worked out