A fresh Windows server often starts in UTC or the time zone of the image it was built from. Set it to the zone you work in so logs, scheduled tasks and file timestamps make sense at a glance.
Check the current time zone
Get-TimeZoneFind the right ID
Windows uses names such as GMT Standard Time (London), W. Europe Standard Time (Amsterdam, Berlin), Eastern Standard Time (New York), Singapore Standard Time and Tokyo Standard Time. Search the full list:
Get-TimeZone -ListAvailable | Where-Object DisplayName -like "*Sydney*"Set it
In PowerShell as Administrator:
Set-TimeZone -Id "W. Europe Standard Time"Or with the graphical tools: Settings → Time & language → Date & time, turn off Set time zone automatically if shown, and choose your zone. The older timedate.cpl dialog works on every version.
Note: Changing the time zone does not change the clock itself, only how it is displayed. Programs that were running may keep showing the old zone until you restart them.
Make sure the clock is accurate
Windows keeps the clock in sync with an internet time server. Check the last sync and force one:
w32tm /query /status
w32tm /resyncIf /resync says the service is not started, run Start-Service w32time first.
A note for traders
MetaTrader shows your broker's server time in Market Watch, which is set by the broker and does not follow the Windows time zone. Pick whichever Windows zone is easiest for you to read logs in; it will not change your charts or how your EAs see time through the trade server.
Troubleshooting
- Clock is minutes off: run the
w32tm /resynccommand above. A wrong clock can also break HTTPS and sign-ins. - Scheduled task runs an hour late: check daylight saving settings in the time zone and the task's trigger time.
