While running thew32tm /resynccommand to sync the time of a Windows computer or server to a time source, you may get the error message “The computer did not resync because no time data was available.”
This error indicates that your computer could not synchronize to the time server because it couldn’t find any time data on the server. Usually, it happens because of improper group policy or registry configurations. you may simply set the proper settings in such cases.
However, there may also be other reasons which require more advanced solutions. In this article, we discuss this error in detail and provide you with all the necessary fixes.
Causes of “The Computer Did Not Resync Because No Time Data Was Available” Error
Here are the potential reasons for the above error on Windows:
How to Fix The Computer Did Not Resync Because No Time Data Was Available?
First,enable automatic time and time zoneon your PC. If the automatic time zone is incorrect, you need to set it manually. Then, follow the possible solutions below to resolve your issue.
One of the main reasons for this error is the improper configuration of the Group Policy Object (GPO) for Windows Time Service. To resolve such an issue, you need to manually check the policies and set them to Not Configured for all computers in the domain. To do so,
On the Domain Controller
Re-register and Restart Windows Time Service
It is also possible that some minor errors with the Windows Time Service are causing this issue. you may try re-registering the service while restarting it to resolve such errors. Here’s how you can do so:
Reconfigure Windows Time Service
Another possible method you may apply is to reconfigure the Windows Time Service to repair any significant issues with the service. You can also try configuring the service to use another time source if using the same source doesn’t resolve the error.
Additionally, trying to sync your Windows server based computer to a Network Time Protocol (NTP) server that’s not running Windows may fail. You must set up the service to use client mode in such a scenario.
To reconfigure the service,
