automatically reverting to the wrong time zone after reboot or user sign-in

Hafiz Othman 40 Reputation points
2026-11-18T04:58:34.7533333+00:00

Hey team, a few workstations keep switching back to the wrong time zone after every reboot or sign-in. Is this usually Windows auto-timezone (tzautoupdate) picking up our VPN egress IP location, or an RDP/VDI redirection or GPO logon script overwriting it?

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Domic Vo 37,655 Reputation points Independent Advisor
    2026-11-18T05:30:27.7833333+00:00

    Hello,

    This behavior can be caused by any of the three scenarios, but I would investigate Group Policy/logon scripts and RDP time zone redirection before assuming tzautoupdate is responsible. Windows automatic time zone detection relies on Windows Location Services, so a VPN egress IP alone is not sufficient evidence that the VPN is changing the time zone; check whether HKLM\SYSTEM\CurrentControlSet\Services\tzautoupdate\Start is set to 3 (enabled) or 4 (disabled), along with the location permission settings. For RDP/VDI environments, verify Allow time zone redirection under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection, and inspect HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\fEnableTimeZoneRedirection. To identify Group Policy interference, run gpresult /h C:\Temp\gpresult.html and review applied computer/user policies and logon scripts for commands such as tzutil /s, PowerShell Set-TimeZone, or registry modifications; also compare the behavior before and after sign-in to identify when the change occurs.

    I recommend testing one affected workstation with automatic time zone detection disabled and a manually assigned time zone, then checking whether the issue persists after reboot and sign-in to isolate the responsible component.

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you.

    Domic Vo.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-18T04:59:35.4+00:00

    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:

    1. Before connecting the VPN.
    2. After connecting the VPN.
    3. Immediately after user sign-in.
    4. Inside an RDP/VDI session.
    5. 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

    1. tzutil
    2. gpresult
    3. Can't set time zone automatically in Windows 10
    4. Location API
    5. Policy CSP - ADMX_TerminalServer
    6. SetTimeZoneRedirection method of the Win32_TerminalServiceSetting class
    7. System clock keeps changing to the wrong time zone after every reboot - Microsoft Q&A
    8. Time accuracy improvements for Windows Server 2016
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.