📎 AI Summary:
The thread discusses troubleshooting and automating time synchronization issues in Windows, with the original poster experiencing recurrent clock desyncs. Contributors suggest using PowerShell commands like `Set-TimeZone`, `w32tm /resync`, and ensuring the Windows Time service is running, while corrections clarify the use of commands such as `Set-Date` instead of `Set-Time`. The main outcome is that the desync issue appears resolved after restarting, and the users share helpful command-line tips and troubleshooting insights.
The thread discusses troubleshooting and automating time synchronization issues in Windows, with the original poster experiencing recurrent clock desyncs. Contributors suggest using PowerShell commands like `Set-TimeZone`, `w32tm /resync`, and ensuring the Windows Time service is running, while corrections clarify the use of commands such as `Set-Date` instead of `Set-Time`. The main outcome is that the desync issue appears resolved after restarting, and the users share helpful command-line tips and troubleshooting insights.
Solution
Open Windows PowerShell as admin (Right-click to run as admin).
Set-Time "12:00 AM"
Set-TimeZone "Eastern Standard Time"
w32tm /resync
It has been super busy over here, as I'm sure you can imagine, given the CrowdStrike situation.
Code:
Get-TimeZone -ListAvailableThis will assist.
The issue with your time desyncing though might not be resolved by this if its happened repeatedly after setting the correct time and timezone. It could be a bad CMOS battery or some other component. Try setting it this way and see if it happens again.
Thanks for the replies. I followed your instructions to run PowerShell as an administrator.
Let's see if this works or not; I will inform you next time.
I believe the CMOS is healthy because Linux has no problem with desync issues, and the UEFI dashboard shows the correct time.
references:
- blog
Code:
PS C:\Windows\system32> Set-Time "12:00 AM"
Set-Time : The term 'Set-Time' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Set-Time "12:00 AM"
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Set-Time:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Windows\system32> Set-TimeZone "SE Asia Standard Time"
PS C:\Windows\system32> w32tm /resync
The following error occurred: The service has not been started. (0x80070426)
PS C:\Windows\system32> Net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.
PS C:\Windows\system32> w32tm /resync
Sending resync command to local computer
The command completed successfully.Let's see if this works or not; I will inform you next time.
I believe the CMOS is healthy because Linux has no problem with desync issues, and the UEFI dashboard shows the correct time.
references:
- blog
