Error 0xC004F06C: Fix the Clock and Activate Windows

Error 0xC004F06C appears when the volume activation service rejects your request: “The Key Management Service (KMS) determined that the request timestamp is invalid.” The cause is almost always the same: your PC’s clock is too far out of step with the activation server’s clock, and KMS only tolerates a gap of about 4 hours. The fix comes in three stages: correct the time and time zone, resynchronize the Windows Time service, then run slmgr /ato again. And if your PC is not on a company network, this code gives away a volume license key sitting where a real license should be.

What does error 0xC004F06C mean?

KMS (Key Management Service) is the activation mechanism used by companies: each computer queries an internal KMS server rather than Microsoft, and holds its activation for 180 days at a time. Every exchange is timestamped to prevent replay. If the client’s clock drifts more than 4 hours away from the KMS host’s clock — the tolerance documented by Microsoft — the timestamp is rejected: 0xC004F06C. So your key is not necessarily at fault; it is the conversation between the two machines that fails.

The usual causes of this drift:

• Wrong date, time or time zone: the wrong year, or a time zone left on another continent.
• Worn-out CMOS battery on the motherboard: the clock jumps back every time the PC is switched off.
• “Windows Time” service (w32time) stopped or pointing to a source it cannot reach.
• Windows / Linux dual boot: Linux writes UTC time to the hardware clock, and Windows reads it back as local time.
• Virtual machine or cloned image whose clock has drifted.
• Company KMS host out of sync: the whole fleet fails at the same time.
• Fake KMS server installed by a pirate activator, with inconsistent timestamps.

The fixes, from the simplest to the most drastic

1. Set the date, time and time zone exactly right

Two minutes are enough, and this settles most cases.

1. Open Settings > Time & language > Date & time.
2. Turn on Set time automatically and Set time zone automatically.
3. Check the year displayed: it is the classic trap.
4. Click Sync now, then restart.

2. Force the Windows Time service to resynchronize

If “Sync now” has no effect, open a command prompt as administrator and enter these lines:

• net stop w32time then net start w32time: restarts the time service.
• w32tm /config /manualpeerlist:”time.windows.com,0x9″ /syncfromflags:manual /reliable:yes /update: sets a reliable time source.
• w32tm /resync: forces the clock to update immediately.
• w32tm /query /status: checks the result.

On a computer joined to a domain, replace the second command with w32tm /config /syncfromflags:domhier /update: the time must come from the domain controller. Also check that no firewall is blocking UDP port 123.

3. Run activation again

Correcting the time is not enough on its own: you have to request activation again.

1. From an administrator command prompt, run slmgr /ato.
2. Check with slmgr /dlv: detailed license status and the KMS host being queried.
3. If the code comes back, run the troubleshooter: Settings > System > Activation > Troubleshoot.

Our Windows 11 activation guide details the methods for each type of license.

4. Deal with the hardware cause: CMOS battery, dual boot, virtual machine

If the time goes wrong again every time the PC is switched off, no command will change anything: the motherboard’s CR2032 battery is dead (an inexpensive part, to be replaced with the PC unplugged). On a dual boot with Linux, pick a side: either Linux writes local time to the hardware clock (timedatectl set-local-rtc 1), or Windows switches to UTC through the RealTimeIsUniversal registry value. On a virtual machine, turn time synchronization with the host back on.

5. Leave KMS mode and install a real key

Check what your machine contains with slmgr /dlv. If the description mentions VOLUME_KMSCLIENT, your Windows is running on a generic volume license key (GVLK), reserved for businesses. On a personal PC, it is almost always the trace of an “activator”: these tools emulate a local KMS server, and the slightest timestamp discrepancy brings the activation down. It is illegal, unstable and often a carrier of malware. The clean way out: wipe this configuration, then install a legitimate key.

Restart between removing the old key and installing the new one. Our Windows 11 keys are genuine and legally resold in Europe (UsedSoft ruling, CJEU C-128/11): they activate directly with Microsoft’s servers.

If nothing has worked

First scenario: the time is right, but the KMS host is still unreachable or misconfigured. The code then often turns into 0xC004F074, which reports that no KMS service is available: an infrastructure problem to be dealt with on the server side (the _vlmcs._tcp DNS record, the host’s clock).

Second scenario, a harsher one: the key is dead. A key refused by the activation servers, revoked by Microsoft or with its activation quota used up cannot be brought back. No slmgr command, no troubleshooter, no reinstall will get it working again: the decision is made on Microsoft’s servers. Two honest ways out remain. Microsoft support often sorts things out if your purchase is legitimate and documented (an invoice, a boxed key, a motherboard change on a retail license). Otherwise, a new license: a genuine Windows 11 Pro key at 9,90€ is the quicker route. Our guide to Windows activation errors covers the other codes in the family.

Frequently asked questions

How big a time gap triggers error 0xC004F06C?

The tolerance documented by Microsoft between the client and the KMS host is about 4 hours; beyond that, the timestamp is rejected. A wrong time zone is enough, even if the displayed time looks right, and so is a wrong year after a battery change.

I get 0xC004F06C on my home PC. Is that normal?

No. A personal PC activated with a retail key never goes through KMS: it contacts Microsoft’s servers directly. Seeing this code at home means Windows was installed with a generic volume license key, usually by an activator. Set the time right, then install a legitimate key with slmgr /ipk: the activation becomes permanent, with no renewal every 180 days.

Do I need to reinstall Windows to fix 0xC004F06C?

Never for this code alone: it concerns the timestamp of the activation request, not the state of the system. Correct the time, run slmgr /ato again, and if the message changes along the way — it sometimes switches to another code in the family, such as 0xC004F063 — deal with the new code. A clean install from official media (see our Windows 11 installation guide) is only justified if your system comes from a tampered image.

🔑 Our best-selling licenses right now

Microsoft Office 2024 Pro Plus€24.90 · key by email within minutesSee the offerWindows 11 Professional€9.90 · key by email within minutesSee the offerWindows 11 Home€8.90 · key by email within minutesSee the offer

Genuine Microsoft licenses · lifetime replacement guarantee · email support 24/7