Diagnose a stopped Windows Time service with PowerShell
Inspect W32Time state, start mode, timezone, local and UTC clock values, configured source, verbose status and optional events without starting the service or changing its configuration.
Run the Windows Time diagnostic
pwsh -NoProfile -File .\Invoke-WindowsDiagnostics.ps1 `
-Time -PrivacyMode -ExportMarkdownThe combined report summarizes the current time-service context. For additional event evidence, the standalone module can include recent Time-Service warnings and errors:
pwsh -NoProfile -File .\scripts\time-sync-diagnostics.ps1 `
-IncludeTimeServiceEventsWhen this guide is useful
- The Windows clock is visibly incorrect or changes after reboot.
- A domain sign-in, certificate, browser or update problem may be related to time drift.
- The Windows Time service appears stopped and you need context before treating it as a fault.
- A support engineer asks for the configured time source and W32Time status.
What the report checks
Service state
Current W32Time status and start mode, including whether the computer is domain joined.
Clock context
Timezone plus current local and UTC values to make obvious offsets or display confusion easier to spot.
Configured source
The source reported by w32tm.exe /query /source, collected without changing peers or requesting synchronization.
Verbose status and events
Read-only status details and optional recent Time-Service warning or error events.
How to interpret a stopped Windows Time service
A stopped service is not always an error
On a non-domain computer, Windows may start the time service when needed rather than keeping it continuously active. Service state should be considered together with start mode, source, status and recent events.
Domain membership changes the expectation
Domain-joined systems normally depend on the domain time hierarchy. A stopped service or unavailable source on such a machine deserves closer review than the same state on an isolated home computer.
Check the reported source
A local hardware clock, unavailable source or unexpected provider can explain why synchronization is not occurring. The source alone is not a complete diagnosis, but it narrows the investigation.
Separate timezone errors from synchronization errors
A correct UTC clock with an incorrect timezone can look like time drift to the user. Compare both local and UTC values before assuming the synchronization service is at fault.
What the toolkit does not do
- It does not correct the clock or timezone.
- It does not configure an NTP server or domain time source.
- It does not start, stop or restart the Windows Time service.
- It does not prove that an upstream time source is accurate.
Reasonable next steps
- Compare local time, UTC time and timezone in the report.
- Check whether the computer is domain joined and whether the reported source matches the expected environment.
- Review recent Time-Service events if the source is unavailable or the clock repeatedly drifts.
- Apply any configuration change only through documented Windows or organization procedures.