NTP Sync Failed: Quick Fixes for Windows Time Errors

Quick Fix (30 seconds) — Check the Basics

Before anything else, check if your internet works. Open a browser and load a site. If that's dead, fix your connection first — NTP needs a live network. Also, look at your date. If it's off by years (like 2005 or 2099), Windows stubbornly refuses to sync. Manually set it close to real time — within a few minutes. Then try the sync again.

Run this from Command Prompt as Admin (right-click, Run as Administrator):

w32tm /resync

If you get "The computer did not resync because no time data was available" or error 0x80070426, move to the next fix. Don't bother with restarting the service yet — that rarely works alone.

Moderate Fix (5 minutes) — Reset Windows Time Service

The culprit here is almost always a corrupted time service state. NTP gets stuck after a bad sync or a network drop. Here's how to reset it properly, not just a restart.

1. Open Command Prompt as Admin again.
2. Stop the time service:
   net stop w32time
3. Unregister and re-register the service:
   w32tm /unregister
w32tm /register
4. Start it back:
   net start w32time
5. Set a reliable NTP server. Microsoft's default pool (time.windows.com) works fine, but I've had better luck with Google or Cloudflare. Use one of these:
   w32tm /config /manualpeerlist:"time.google.com" /syncfromflags:manual /reliable:yes /update
6. Force sync again:
   w32tm /resync

If this works, you're done. If not — and the error persists — your registry is probably borked or a firewall is blocking NTP (port 123 UDP). Check your firewall rules. Windows Defender usually allows it, but corporate VPNs or third-party firewalls often don't. Temporarily disable your firewall to test — if sync works, you found the problem.

Advanced Fix (15+ minutes) — Registry Cleanup and Full Reset

Still failing? This gets into the weeds. Windows stores time configuration in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time. Corrupted keys here cause permanent sync failures, even after service resets.

Before touching the registry, back it up. Export the entire W32Time key. Then proceed:

1. Open Regedit as Admin (regedit from Run dialog).
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters.
3. Delete the Type value if it's not NTP. Set it to NTP if missing.
4. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config.
5. Check AnnounceFlags — it should be 5 (decimal). If it's anything else, change it. This tells Windows to act as a reliable time source internally.
6. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer.
7. Set Enabled to 0 (unless you're running a time server, which you're not).
8. Close Regedit, then run these commands in Admin CMD:
   net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /config /manualpeerlist:"time.google.com" /syncfromflags:manual /reliable:yes /update
w32tm /resync

If you still get errors, check the System Event Log under Event Viewer > Windows Logs > System. Filter by source W32Time. The logs will tell you exactly why sync fails — like "NTP client failed to reach server" or "time provider error." Common causes include:

• DNS can't resolve the NTP server — try using an IP instead (e.g. 216.239.35.0 for Google).
• Port 123 UDP blocked by corporate proxy or VPN. Check with telnet time.google.com 123 — if it fails, it's a firewall issue. You'll need to contact your network admin.
• Time service is disabled in services.msc — check it's set to Automatic.

One last thing: if you're on a domain, the domain controller controls time sync. Local NTP settings won't work — the DC forces its own. In that case, run w32tm /query /status to see the source — it'll be your DC. If the DC's time is wrong, fix that from the domain admin side. But for standalone machines, the steps above fix 95% of NTP sync failures.