

Welcome to ham-interfaces.com
How to Keep Your PC Clock Accurate for FT8 and Digital Modes
​Why Precise Time Matters
Digital modes such as FT8, JS8Call, and WSPR rely on tightly synchronized time slots. If your PC’s clock drifts by more than a couple of seconds, you may miss decodes, transmit outside the expected window, or introduce logging errors. Maintaining accurate UTC alignment is essential for reliable weak‑signal digital operation.
​
Windows includes a built‑in time synchronization service (Windows Time / W32Time) that uses Network Time Protocol (NTP) servers to keep the system clock aligned. However, on a typical standalone PC, its default behaviour synchronizes time only infrequently (often on the order of days), which is insufficient for time‑critical digital modes.
This guide shows how to configure Windows to synchronize time hourly using standard, reliable NTP servers—without installing third‑party software—ensuring your station remains accurately synchronized for digital mode operation.
​
​
Step-by-Step: Configure Hourly NTP Sync on Windows
​​
Step 1: Enable Internet Time Sync
This guide applies to both Windows 10 and Windows 11. The layout may vary slightly between versions, but the settings and PowerShell commands are the same.​
​
-
Open Settings > Time & Language > Date & Time
-
Ensure the following options are enabled:
- Set time automatically
- Set time zone automatically -
Scroll down to Synchronize your clock and click Sync now
This confirms that Windows is actively synchronizing system time and that the Windows Time service (W32Time) is functioning correctly.
​
By default, standalone Windows systems synchronize time using Microsoft’s public NTP service, time.windows.com. In the next step, we’ll configure additional NTP servers to improve reliability and prepare Windows for more frequent synchronization.
​​​​​
​
Step 2: Set Hourly Sync Interval via PowerShell
By default, standalone Windows systems synchronize time only infrequently (typically once every 7 days). For digital modes such as FT8, this is not precise enough—PC clocks can drift several seconds over that period, leading to missed decodes or mistimed transmissions.
​
To improve accuracy, we’ll configure Windows to synchronize time once per hour using its built‑in Windows Time service (W32Time). This provides regular, predictable corrections without installing any third‑party software.
Don’t worry if you’re not familiar with PowerShell—this step is simple and only requires copying and pasting a command.
​
Open PowerShell as Administrator​​​
-
Press Windows + X
-
Select Windows PowerShell (Admin) or Terminal (Admin)
(The name varies slightly depending on Windows version.) -
When prompted, click Yes to accept the User Account Control (UAC) prompt
A blue PowerShell window similar to the one below will open.

Next, we’ll copy and paste six PowerShell commands into the PowerShell window. Each command performs a specific task; they are safe to run and can be entered one at a time.
​
1. Set how often Windows checks the time.
This command tells Windows to synchronise its clock once every hour, providing regular and predictable time updates suitable for digital modes.
​
Copy the entire command below, paste it into the PowerShell window, and press Enter:
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient" -Name "SpecialPollInterval" -Value 3600
​​​
2. Configure which internet time servers Windows uses
This command tells Windows exactly which NTP servers to use and prevents it from automatically switching back to default or domain‑provided time sources. Multiple servers are specified for reliability in case one is temporarily unreachable.
Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"
​
w32tm /config /manualpeerlist:"pool.ntp.org,0x9 time.cloudflare.com,0x9 time.google.com,0x9 time.windows.com,0x9" /syncfromflags:MANUAL /update
3. Restarts the Windows Time service.
This forces Windows to reload and apply the new configuration immediately.
Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"
Restart-Service w32time
​
4. Force an immediate time resynchronisation
This command tells Windows to rediscover its configured NTP servers and synchronise the clock right now, rather than waiting for the next scheduled check.
​
Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"
​
w32tm /resync /rediscover
5. Display the current time synchronisation status
This shows whether Windows is synchronised, which server is being used, and the current clock offset.
​
Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"
​
w32tm /query /status
​
6. Check real‑time clock accuracy
This performs a short live comparison between your PC clock and an external NTP server, showing the time offset in milliseconds.
Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"
​
w32tm /stripchart /computer:time.cloudflare.com /samples:5 /dataonly
​​
​
In Powershell, you should now see something like this:

Windows Time Synchronisation - w32tm /query /status explanation
Using the above Power Shell Commands, The Windows Time service has been successfully reconfigured and is operating normally. The output from w32tm /query /status confirms correct behaviour. The following explains the metrics displayed and how they should be interpreted:
Leap Indicator
Indicates whether any leap‑second adjustments are pending. A value showing no warning confirms the time source is valid and operating normally.
​
Stratum
Shows the level of the time source in the NTP hierarchy. A low stratum value (such as a secondary reference) indicates synchronisation with a reliable upstream time server that is close to an authoritative source.
​
Precision
Represents the resolution of the system clock hardware. This is a fixed characteristic of the system and does not indicate time accuracy or a fault condition.
​
Root Delay
Measures the network round‑trip delay between the system and the upstream time source. Low values indicate good network connectivity and minimal latency.
​
Root Dispersion
Root dispersion is an internal Windows Time confidence metric. It represents Windows’ maximum estimated uncertainty in the configured time source and does not indicate the actual clock error.
Following configuration changes, service restarts, or time‑source updates (such as running the PowerShell commands above), this value may initially appear high and can be in the order of several seconds. This is expected behaviour.
As the system clock becomes progressively disciplined through repeated, successful synchronisations, Windows increases its confidence in the time source and the root dispersion value will automatically decrease over time. No manual intervention is required.
​
Reference ID
An internal identifier for the active time source. This confirms the system is synchronising with an external NTP server.
​
Last Successful Sync Time
Shows the most recent successful time synchronisation and confirms that the Windows Time service is actively operating.
​
Source
Identifies the current NTP server being used. This confirms the system is synchronising with the configured manual time sources and is not reverting to default providers.
​
Poll Interval
Indicates how frequently Windows checks its time source. This value may adjust dynamically while the clock stabilises and is expected behaviour.
​
Real‑time accuracy verification (The Key Measurement)
The primary indicator of time accuracy is the output from w32tm /stripchart. This command provides a direct, real‑time measurement of the actual difference between the local system clock and a trusted NTP reference, while compensating for normal network latency.
The five‑sample stripchart results show how much the PC clock varies from the reference time at that moment. In normal operation, these values are typically in the order of tens to a few hundreds of milliseconds and should remain stable and consistent across samples. Stability and consistency are more important than the exact numeric value and confirm that the system clock is accurate and correctly synchronising.
While root dispersion reflects Windows’ internal confidence level and improves gradually over time, the stripchart output represents the true, observable clock offset. For this reason, w32tm /stripchart should be used as the definitive verification of time accuracy, even if internal confidence metrics are still converging.