Domain workstation system clock gradually drifting post-login despite successful W32Time sync

Oliver Taylor 0 Reputation points
2026-11-20T16:51:57.6933333+00:00

Seeking help from the Community!

Several domain-joined workstations are showing a gradual system clock drift shortly after users sign in, even though w32tm /resync succeeds on boot and w32tm /query /status initially points to our primary Domain Controller. Over the course of a few hours, the local clock slips out of sync far enough to trigger Kerberos authentication errors and MFA/SSO token rejections.

Before I start overriding W32Time polling intervals via GPO or pushing scheduled resync tasks across the fleet, I want to pinpoint what's pulling the clock off-track after logon. Should I start by checking whether Hyper-V / VMware Time Synchronization integration services are fighting domain NT5DS sync on virtualized/VDI endpoints, or auditing W32Time event logs (Time-Service Event IDs 35/37/50) alongside MaxPosPhaseCorrection / SpecialPollInterval registry settings and CMOS/hardware timer drift? Let me know what you guys usually check first when domain time sync won't hold steady during an active user session.

Appreciate your response!

Oliver Taylor.

Windows for business | Windows 365 Enterprise
0 comments No comments

1 answer

Sort by: Most helpful
  1. Harry Phan 36,850 Reputation points Independent Advisor
    2026-11-20T17:22:43.9233333+00:00

    Hello Oliver,

    I would first investigate potential conflicts between domain time synchronization and hypervisor time integration, especially on virtualized or VDI endpoints.

    Check whether Hyper-V or VMware Time Synchronization is continuously adjusting the guest clock while Windows Time Service uses the domain hierarchy (NT5DS). Next, review the Microsoft-Windows-Time-Service/Operational event log, particularly Events 35, 37, and 50, and compare the time source before and after logon using w32tm /query /source and w32tm /query /status.

    You can also run w32tm /monitor to compare time across domain controllers and inspect the W32Time configuration for unexpected GPO overrides. Avoid changing polling intervals until the actual time source conflict is identified.

    If the issue also occurs on physical workstations, investigate BIOS/UEFI firmware, hardware timers, and possible CMOS battery issues.

    Best regards,

    Harry P.

    Was this answer helpful?

    0 comments No comments

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.