Windows server time going back to past because of time synchronization with the hardware clock - Microsoft Q&A (2024)

2024-01-23T13:33:59.9533333+00:00

Sign in to comment

1. 

   Danish Gul Khattak 335Reputation points

   2024-01-23T13:55:27.2033333+00:00

   It seems like the Windows Time service is synchronizing the system time with the hardware clock, causing the time to go back periodically. Since the server is not part of a domain, you can try the following steps:

   1. Disable Windows Time Service:
      • Open the Services application (services.msc) and locate the "Windows Time" service.
      • Set the startup type to "Disabled" to prevent it from starting automatically.
   2. Check Third-Party Time Sync:
      • Ensure there are no third-party applications or scripts running that might be syncing the time.
   3. Review Scheduled Tasks:
      • Examine any scheduled tasks related to time synchronization and disable or modify them.
   4. Check for System Policies:
      • Verify if there are any local group policies affecting time synchronization.
   5. Registry Settings:
      • Open the Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters.
      • Look for the "Type" DWORD and set its value to "NoSync" to prevent time synchronization.

   Remember to backup the registry and create system restore points before making any changes.

   If the issue persists, it might be advisable to involve the server vendor or IT support with access to the hardware, as they can investigate potential hardware-related problems or provide more specific guidance based on your server setup.

   1. 

      Sowjanya G 0Reputation points

      See Also

      TroubleshootingNTP < Support < Network Time Foundation's NTP Support Wiki

      2024-01-25T07:00:51.48+00:00

      Hi. Thank you so much for your response. I have a few doubts. Server time is syncing with hardware clock. So, we have to set NoSync kind of property for Hardware clock right. Why are we setting it to W32Time when it is anyways not running. Kindly provide more details. Thank you.

   2. 

      Danish Gul Khattak 335Reputation points

      2024-01-26T09:07:10.11+00:00

      The decision to set the NoSync property for the hardware clock depends on the specific requirements of your system. If you're not using W32Time for time synchronization and prefer to rely on other methods or tools, configuring NoSync may be appropriate. This prevents the Windows Time service (W32Time) from trying to synchronize the hardware clock.It's important to align your time synchronization strategy with your system's needs and ensure consistency across your network. If W32Time is not in use, adjusting its settings accordingly can help avoid unnecessary conflicts or attempts to sync with the hardware clock.

   3. 

      Danish Gul Khattak 335Reputation points

      2024-01-26T09:09:29.8666667+00:00

      The decision to set the NoSync property for the hardware clock depends on the specific requirements of your system. If you're not using W32Time for time synchronization and prefer to rely on other methods or tools, configuring NoSync may be appropriate. This prevents the Windows Time service (W32Time) from trying to synchronize the hardware clock.It's important to align your time synchronization strategy with your system's needs and ensure consistency across your network. If W32Time is not in use, adjusting its settings accordingly can help avoid unnecessary conflicts or attempts to sync with the hardware clock.

   Sign in to comment

2. 

   Daisy Zhou 22,476Reputation points • Microsoft Vendor

   2024-01-24T02:50:04.1666667+00:00

   Hello Sowjanya G,

   Thank you for posting in Q&A forum.

   I hope the information provided by Danish Gul Khattak is helpful.

   In addition, whether this server is a physical machine or virtual machine?

   If the Answer is helpful, please click "Accept Answer" and upvote it.

   1. 

      Sowjanya G 0Reputation points

      2024-01-25T07:04:36.77+00:00

      Hi Daisy. Thank you for your response. It is a physical machine. Not Virtual server. Please help me understand why we have to set NoSync for W32Time in the registry when the issue is with the Hardware clock. Kindly shed some light. Thank you.

   Sign in to comment

Sign in to answer