The fastest way to identify the writer is to record the time-zone and policy state before sign-in, immediately after sign-in, and after an RDP connection; the transition that changes tzutil /g distinguishes automatic detection from session redirection or policy/script enforcement.
1. Capture exactly when it changes
Run this from an elevated PowerShell window at each stage:
- Before connecting the VPN.
- After connecting the VPN.
- Immediately after user sign-in.
- Inside an RDP/VDI session.
- After disconnecting and checking the physical console.
$stamp = Get-Date -Format 'yyyyMMdd-HHmmss'
"Time: $(Get-Date -Format o)"
"Zone: $(tzutil /g)"
"tzautoupdate Start:"
reg query HKLM\SYSTEM\CurrentControlSet\Services\tzautoupdate /v Start
"RDP redirection policy:"
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" `
/v fEnableTimeZoneRedirection
gpresult /h "$env:PUBLIC\gp-$stamp.html"
tzutil /g reports the current Windows time-zone ID; tzutil /l lists valid IDs, and tzutil /s "<ID>" sets one manually.^1^ The gpresult report shows the Resultant Set of Policy actually enforced for the computer and signed-in user, including overlapping policies.^2^
2. Interpret the transition
Changes only after VPN connection or location refresh
Check:
reg query HKLM\SYSTEM\CurrentControlSet\Services\tzautoupdate /v Start
reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location /v Value
For Windows 10, Microsoft documents:
-
tzautoupdate\Start = 3: automatic time-zone detection enabled.
-
tzautoupdate\Start = 4: automatic detection disabled.
- Location
Value = Allow: location enabled.
- Location
Value = Deny: location disabled.^3^
Windows location can select among GPS, connected networks, cellular networks, Internet data, and user settings, so a VPN-correlated change does not by itself prove that the VPN egress IP supplied the location.^4^
For fixed-location workstations, disable automatic time-zone detection through your management baseline and deploy the intended zone explicitly:
tzutil /l
tzutil /s "Eastern Standard Time"
tzutil /g
Replace the example ID with the exact ID returned by tzutil /l. If Group Policy controls Location, changing the registry locally will not persist because policy overrides it.^3^
Changes only inside RDP/VDI
Inspect this policy:
Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection → Allow time zone redirection
When enabled, a capable client sends its local time zone to the session. When disabled or not configured, the session uses the RD Session Host time zone.^5^
That behavior is session-specific:
- With redirection disabled, new sessions inherit the server zone.
- A reconnected session retains the zone it had before disconnection.^6^
Therefore, if only the remote desktop shows the alternate zone while the workstation console remains correct, troubleshoot RDP/AVD redirection rather than tzautoupdate.
Changes exactly at sign-in, policy refresh, or reboot
Open the generated gp-*.html and inspect both computer and user settings. Also examine:
- Domain and local logon/startup scripts.
- Intune device configuration and remediation scripts.
- Scheduled tasks triggered At log on or At startup.
- Device-management or OEM agents that invoke
tzutil, Set-TimeZone, or modify TimeZoneInformation.
A repeated reset after reboot commonly indicates a higher-level configuration overwriting the local choice; removing that policy, service, or management action is required for a manual setting to persist.^7^
3. Correlate the change with event evidence
In Event Viewer → Windows Logs → System, filter around the exact transition time for:
-
Microsoft-Windows-Kernel-General
-
Microsoft-Windows-Kernel-Boot
- Windows Time-related providers
Microsoft recommends these logs when determining whether Windows or a third-party influence changed time.^8^
Treat W32Time separately from the time zone: clock synchronization and time-zone selection are different operations. If tzutil /g changes, focus on tzautoupdate, RDP redirection, policy, scripts, or management agents rather than merely changing the NTP source.
References
- tzutil
- gpresult
- Can't set time zone automatically in Windows 10
- Location API
- Policy CSP - ADMX_TerminalServer
- SetTimeZoneRedirection method of the Win32_TerminalServiceSetting class
- System clock keeps changing to the wrong time zone after every reboot - Microsoft Q&A
- Time accuracy improvements for Windows Server 2016