Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0xC004F06C

0xC004F06C and 0x80072F8F: Clock Skew Is Blocking KMS Activation

11 min read Updated October 5, 2026 Windows Activation & Licensing

Fix it now

Microsoft publishes 0xC004F06C as the Key Management Service finding the request timestamp invalid, and its resolution is to bring the client’s clock into line with the host using NTP or Active Directory. 0x80072F8F is the same root cause seen from the security layer: the device date and time are wrong.

Run these on the failing client, in an elevated Command Prompt, in order

w32tm.exe /query /status /verbose
w32tm /resync
slmgr /ato
slmgr /dli
  1. Read the source and the last successful sync in the first command’s output before changing anything. A machine with no source is a different fix from one whose source is unreachable.
  2. If the resync fails on a domain member, check that Type under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\Parameters reads NT5DS.
  3. If it fails on a machine that is not domain-joined, set Enabled to 1 under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient, then resync again.
  4. Compare client and host in UTC, not local time. The time zone on either machine is irrelevant to what KMS measures.

w32tm /resync takes no /force parameter. The documented parameters are /computer, /nowait, /rediscover and /soft, and an unrecognised switch makes the command exit without resynchronising anything.

If activation succeeds after the clock is right, you are done. If it does not, the next section covers why the licensing stack is so sensitive to time and which of the causes you have.

Why it happens

Every KMS activation request carries a timestamp, and the host checks it. Microsoft’s published text for 0xC004F06C is that the computer could not be activated because the Key Management Service determined the request timestamp is invalid, and its resolution is a single instruction: change the system time on the client to match the KMS host, using an NTP time source or Active Directory Domain Services. There is no key problem and no entitlement question anywhere in this.

How far out is too far is documented, though not on the page for this code. Microsoft states on its 0xC004F074 page that activation can fail when the difference between the client’s system time and the KMS host’s is more than four hours. That is the number to work with, and it is measured in UTC, which is why a machine displaying the correct local time in the wrong time zone still fails.

Microsoft’s dedicated article for this code names three causes and none of them is a wrong clock as such. They are: the Windows Time service is not running, the NtpClient time provider is not enabled, and domain-joined computers are not synchronising with Active Directory Domain Services. In other words the clock being wrong is the symptom; the time service not doing its job is the cause, and that is where the fix belongs.

0x80072F8F sits alongside it. Microsoft’s activation help publishes it as the device date and time being incorrect, or the device having connection problems reaching the activation service, and points you at Settings, then Time and language, then Date and time. Three more codes travel with these two – 0x8004D102, 0xC004D30C and 0xC004B011 – and Microsoft publishes no meaning for any of them, so read them as company rather than as evidence.

The Windows Time service is not running

You have this one if w32tm.exe /query /status /verbose errors, or reports no successful sync at all.

  1. Open Services and confirm Windows Time is running. Microsoft’s own resolution for this code starts here.
  2. Start it, then run w32tm /resync.
  3. Re-read the status output and confirm a recent successful synchronisation.
  4. Retry slmgr /ato.

The NtpClient provider is disabled on a machine that is not domain-joined

You have this one if A workgroup machine or a standalone server that never corrects itself, however often you resync.

  1. Open Registry Editor and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient.
  2. Set the Enabled value to 1.
  3. Restart the Windows Time service, then run w32tm /resync.
  4. Confirm the offset has closed before retrying activation.

This is Microsoft’s documented resolution for non-domain-joined computers hitting this code, and it is the step most troubleshooting guides skip.

A domain member is not syncing from the domain hierarchy

You have this one if Several domain-joined machines drift together, and none of them is taking time from a domain controller.

  1. Check HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\Parameters and confirm the Type value reads NT5DS.
  2. If it reads anything else, the machine has been configured to take time from somewhere other than the domain.
  3. Set it back to the domain hierarchy, restart the Windows Time service, and resync.
  4. Fix the domain’s own source as well if the whole hierarchy has drifted; a member syncing correctly from a wrong source is still wrong.

A virtual machine reverted to an old snapshot

You have this one if The guest boots with a date weeks or months in the past and corrects itself only after a delay, if at all.

  1. Let the guest reach a time source before you judge it. Many correct themselves within a minute of boot.
  2. Enable time synchronisation in the hypervisor’s integration settings, or make sure the guest can reach an NTP source at boot.
  3. Run w32tm /resync, confirm the offset, then slmgr /ato.

The hardware clock will not hold

You have this one if The clock resets to the same old date after every full power cycle.

  1. Replace the motherboard battery. No software fix survives a cold boot on a machine that cannot keep time.
  2. Correct the date and time in firmware setup as well as in Windows.
  3. Re-run activation after the next full power cycle to confirm it holds.

Full reference

The time commands worth knowing

Command What it does
w32tm.exe /query /status /verbose Current source, offset, stratum and last successful sync. Microsoft’s first diagnostic for this code
w32tm /resync Tells the service to match its clock to the source as soon as possible
w32tm /resync /rediscover Redetects network status and sources before resyncing
w32tm /resync /nowait Returns immediately rather than waiting for the resync to finish
w32tm /query /peers Lists the configured time sources
slmgr /ato Retries activation once the clock is right
slmgr /dli Confirms Licence Status after the retry

w32tm /resync /force appears in a great deal of third-party troubleshooting material and is not a real command. /force is not one of the documented parameters of /resync, and w32tm validates its arguments strictly: given an unrecognised switch it reports the argument as unexpected, prints its usage block and exits without resynchronising. Every article that offers it as the fix for a clock problem is offering a command that does nothing.

The registry values Microsoft names for this code

Path Value What to set
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient Enabled 1, on computers that are not domain-joined
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\Parameters Type NT5DS, on domain-joined computers, meaning sync from the AD DS hierarchy

These two are the whole of Microsoft’s documented resolution beyond confirming the service runs. If you fix nothing else, fix these, because they are what stops the machine drifting back a week later.

Where the code is recorded

Event ID 12288 in the Application log carries the activation attempt, and the code appears in it directly. The entry names the host and port the client used, the CMID and a timestamp, so it also tells you whether the client is reaching the host it should. A machine reporting 0xC004F06C in a 12288 is reaching a host: the request arrived and was refused on its timestamp, which rules out DNS and the firewall in one line.

Time zones, UTC and what actually gets compared

  • The comparison is in UTC. A machine showing the correct wall-clock time in the wrong time zone is out by the difference between them, and KMS sees that difference.
  • So a laptop returning from another country with the time zone left behind can fail while displaying a time its user is happy with.
  • Fixing the time zone without fixing the clock, or the reverse, moves the machine but may not close the gap. Check the offset after each change.
  • Automatic time zone detection helps roaming machines and is not a substitute for a working time source.

When the clock is right and activation still fails

  1. Confirm the offset is genuinely small now, from w32tm.exe /query /status /verbose, rather than assuming the resync worked.
  2. Compare the host as well as the client. A correct client and a four-hour host produce exactly this code.
  3. Check whether the client reached a host at all, in Event ID 12288 and 12289 in the Application log.
  4. Check the host’s count and its own licence state, which are separate refusals with separate codes.
  5. If the machine is not domain-joined and never has been, confirm it has a reachable time source at all rather than a configured one.

Why this shows up on the machines it does

The population is predictable: virtual machines restored from snapshots, laptops that have been in a drawer, machines with a dead CMOS battery, and standalone servers nobody put on a time source. All four share the same profile, which is a device that spends long periods not talking to anything that would correct it. If you are seeing this on a fleet rather than a machine, the time hierarchy is the thing to fix, not the individual clocks.

There is a wider point here. Large clock skew breaks Kerberos authentication as well as activation, so a domain-joined machine that is hours out will be producing other symptoms someone else is investigating separately. Fixing the time service fixes both.

Every code this article covers

Code What it points at Source
0xC004F06C The Key Management Service determined that the request timestamp is invalid. Microsoft’s resolution is to sync the client’s clock to the host using NTP or AD DS Microsoft Learn
0x80072F8F The device date and time are incorrect, or the device cannot reach the activation service Microsoft Support
0x8004D102 Seen alongside clock-related activation failures. Microsoft publishes no meaning for it; treat it as evidence of a failed exchange rather than of a specific fault not published by the vendor
0xC004D30C Appears in the same context. No published meaning; diagnose from the time service state rather than from the digits not published by the vendor
0xC004B011 Reported in the same situations. No published meaning; check the clock and the time source as for the codes above not published by the vendor

Confirm the fix worked

  1. w32tm.exe /query /status /verbose on the client shows a recent successful sync and a small offset.
  2. Client and KMS host agree in UTC to within minutes.
  3. The Type value under W32Time\Parameters reads NT5DS on domain members, or Enabled is 1 under TimeProviders\NtpClient on machines that are not domain-joined.
  4. slmgr /ato completes, and slmgr /dli reports Licence Status: Licensed.
  5. Power the machine off completely and check the time again on the next boot, which is what catches a failing hardware clock.

Questions people ask about this

How far out does the clock have to be?

Microsoft states that a difference of more than four hours between the client and the KMS host can cause activation to fail. Smaller drifts are tolerated, which is why a machine a few minutes out activates normally.

Does the time zone matter, or only the clock?

Both, because the comparison happens in UTC. A machine showing the correct local time in the wrong time zone is out by the difference between the two zones, and that is what gets measured.

Do I need to reboot after fixing the time?

No. Correct the clock, confirm the offset has closed, and run slmgr /ato straight away.

Is w32tm /resync /force a real command?

No. /force is not one of the documented parameters of w32tm /resync; those are /computer, /nowait, /rediscover and /soft. Passing it makes w32tm reject the argument and print its usage rather than resynchronising, so anyone who ran it and saw no improvement was seeing the command do nothing.

Is this a licensing problem?

No. Your key and your entitlement are untouched and nothing needs buying. This is a time service fault, and it costs nothing but the few minutes it takes to point the machine at a source it can reach.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0xC004B001 and 0xC004B100: Activation Server Says the Licence Is Invalid Free Fix 0x8007007B and 0x800706BA: Wrong KMS Host Name or Port 1688 Blocked Free Fix 0xC004F031: Installation ID and Confirmation ID Do Not Match License Error 0xC004F041 and 0xC004F039: Your KMS Host Is Not Activated or Enabled
โ† Back to Knowledge Base