How to Sync Windows 7, 10, and 11 Clock with an Accurate NTP Server

Antonio NEMCD Author

Published Jun 6, 2015 · Updated Nov 14, 2026 · 3 min

I ran into a handy site called ntp-servers.net – it immediately shows the exact drift between reference atomic time on an NTP server and your own computer’s clock.

In short: if the default time.windows.com falls behind or throws “An error occurred while Windows was synchronizing”, switch Windows 7, 10, or 11 to a nearby pool.ntp.org cluster (such as europe.pool.ntp.org or us.pool.ntp.org) via timedate.cpl or a single elevated PowerShell w32tm command.

Out of the box my PC synced with time.windows.com, and even right after pressing “Update now” the clock still trailed reference time by about 5 seconds. As soon as I pointed Windows at the European pool.ntp.org pool (europe.pool.ntp.org), the drift dropped to milliseconds.

Changing the Time Server via GUI in Windows 7, 10, and 11

The classic Internet Time dialog works the exact same way across all three versions – in Windows 10 and 11, launching it with Run is much faster than digging through Settings:

1. Open Date and Time: in Windows 7, click the taskbar clock -> “Change date and time settings”. In Windows 10 or 11, press Win + R, type timedate.cpl, and press Enter.
2. Switch to Internet Time: open the “Internet Time” tab -> click “Change settings…”.
3. Enter the server: type europe.pool.ntp.org (or your regional pool), click “Update now”, and hit OK.

Once saved, Windows keeps polling that pool automatically on schedule. Reload a reference clock page like ntp-servers.net afterwards to verify the offset.

Best Public NTP Servers to Use

Microsoft’s default server is often congested, so public Anycast or regional round-robin pools are usually far more reliable:

• europe.pool.ntp.org / north-america.pool.ntp.org: balanced continental pools with automatic routing.
• ua.pool.ntp.org / pl.pool.ntp.org / uk.pool.ntp.org: country-level pools for minimal network latency.
• time.cloudflare.com: fast global Anycast NTP endpoint operated by Cloudflare.
• time.google.com: Google’s public NTP service (uses “leap smearing” on leap seconds, so avoid mixing it with standard non-smeared NTP servers on the same system).

If the GUI Fails: Fixing Sync with PowerShell (w32tm)

Over the years, readers often noted that clicking “Update now” fails with an error or timeout. Most of the time the culprit is a stopped w32time service, blocked outbound UDP port 123, or stale peer state. Running PowerShell as Administrator resets and forces sync cleanly:

$ntp = "europe.pool.ntp.org,0x8"
w32tm /config /manualpeerlist:"$ntp" /syncfromflags:manual /update
Restart-Service w32time
w32tm /resync

The ,0x8 flag puts Windows Time into standard NTP client mode, avoiding common handshake quirks with public servers. Check which source is active and current offset anytime with:

w32tm /query /status

If you need dozens of office workstations synced against one internal server on your LAN, check out my guide on setting up a local NTP server on FreeBSD. On a home PC, swapping in pool.ntp.org takes under a minute and fixes clock drift for good.