Users who attempt to synchronise the time on a Microsoft Windows Server computer with an external time source encounter this error. Running the ‘w32tm /resync’ command on either the domain or the client computer will sync the time.
Over the years, numerous approaches to solving this issue have been developed. In order for you to review them and hopefully find a solution, we have chosen to compile the best solutions and include them in this article.
- 1 What Leads to the Windows Error “The Computer did not Resync Because no Time Data was Available”?
- 2 Solution 1: Altering Group Policies
- 3 Solution 2: Modifying Registry Keys
- 4 Solution 3: Run the Windows Time Service Command as a Third Option
- 5 Solution 4: Restart the Windows Time Service as a Fourth Option.
- 6 If You Click Start, You Might See the Following Error Message:
What Leads to the Windows Error “The Computer did not Resync Because no Time Data was Available”?
- Some group policies pertaining to the Windows Time Service may need to be changed. A group policy could be incorrectly set.
- Windows Time Service parameter incorrectly set The issue should be fixed by altering a parameter in the registry settings for Windows Time Service.
- problems with the Windows Time Service in general – You can try starting the service again or running commands.
Solution 1: Altering Group Policies
The main approach that Microsoft experts advise is this one, and many people have used it to successfully solve their issues. Make sure you follow the instructions correctly if you are experiencing and troubleshooting the issue on a local computer as opposed to a domain controller.
Regarding a Domain Object:
- Using your keyboard’s Windows Key + R combination, launch the Run dialogue box (press these keys at the same time). The Active Directory Users and Computers Microsoft Management Console will open if you enter “dsa.msc” in the newly opened box without quotation marks and click OK.
- From the context menu, select Properties after right-clicking the container that houses the Group Policy object you wish to change.
- Select the Group Policy tab in the newly opened “Container Name” Properties window. Select Edit by clicking the object you want to change.
Regarding a Local Computer:
- Using the Windows Key + R key combination on your keyboard, you can launch the Run dialogue box. Press these keys simultaneously. To launch the Local Group Policy Editor, type “gpedit.msc” in the freshly opened box without the quotation marks and click OK.
Regardless of the kind of computer you are using, the following steps will always be the same:
- Double-click Administrative Templates under Computer Configuration on the left navigation pane of Local Group Policy Editor, then select System > Windows Time Service.
- Left-click on the Windows Time Service folder to select it, then look in the right-side section.
- Double-click the “Global Configuration Settings” policy and select the “Not Configured” radio button by checking the box.
- Click the Time Providers key after expanding the Windows Time Service folder. The Configure Windows NTP Client, Enable Windows NTP Client, and Enable Windows NTP Server keys are all located inside.
- Double-click each entry, then select Not Configured from the radio button at the top.
- Implement your changes before leaving. The modifications won’t take effect until you restart.
- Finally, restart the computer to apply the changes and verify that the error hasn’t reappeared.
Solution 2: Modifying Registry Keys
You should be able to correctly connect to the time server by editing a few specific registry keys. The host computer of the workgroup, homegroup, or any other network with a centralised host computer should go through this sequence of steps. Be cautious when manipulating the registry keys.
- Given that you are about to delete a registry key, we advise you to read this article on how to safely backup your registry to avoid further issues. However, if you follow the instructions carefully and accurately, nothing will go wrong.
- By entering “regedit” in the search field, the Start menu, or the Run dialogue box, which can be accessed by pressing the Windows Key + R key combination, the Registry Editor window will be displayed. Go to the following key in your registry by using the left pane to navigate:
- Try to find a Type entry by clicking on this key. If it isn’t already there, click the right mouse button on the right side of the window and select New > String Value to add a new String Value entry called Type. Select the Modify option from the context menu by performing a right-click on it.
- Change the value to NT5DS in the Value data section of the Edit window and then save your changes. Any security dialogues that may appear during this process should be confirmed.
- By selecting Start > Power > Restart from the Start menu, you can now manually restart your computer and see if the issue has been resolved. It’s likely that doing this will solve the issue right away.
Solution 3: Run the Windows Time Service Command as a Third Option
There is a specific command that has assisted numerous users in fixing the time sync issue. It is a more complex version of the ‘w32tm’ command that will take additional steps in order to properly connect to the ‘time.windows.com’ server. The video is below.
- Either directly in the Start menu or by tapping the search button next to it, look up “Command Prompt.” Choose “Run as administrator” from the context menu when you right-click the first result that appears at the top.
- When using an older version of Windows, users can open the Run dialogue box by pressing the Windows Logo Key plus the R key combination. To launch Command Prompt as an administrator, type “cmd” into the box and press Ctrl + Shift + Enter.
- Be sure to press the Enter key on your keyboard after copying and pasting the command as shown below.
- Verify if the ‘w32tm /resync’ command still causes the “The computer did not resync because no time data was available” issue!
Solution 4: Restart the Windows Time Service as a Fourth Option.
Restarting the service will restart the entire procedure as well, but it should fix the issue, particularly if a bug was to blame for it acting strangely. The video is below.
- By simultaneously pressing the Windows Key and R keys on your keyboard, you can launch the Run utility. Without using quotation marks, type “services.msc” in the freshly opened box and press OK to launch the Services tool.
- Find Windows Time Service on the list, right-click on it, and then choose Properties from the pop-up context menu.
- You should stop the service by clicking the Stop button in the middle of the window if it has already started (you can check this right next to the Service status message). However, launch it once more by clicking the Start
- Before you take any further action, confirm that the Startup type menu option for the service is set to Automatic in the properties window. Any dialogue boxes that may appear when changing the startup type should be confirmed.
If You Click Start, You Might See the Following Error Message:
“Windows was unable to launch the service on the local machine. The specified account for this service is different from the accounts specified for other services running in the same process, according to error 1079.
If this occurs, fix it by following the steps below.
- To open the service’s properties window, adhere to steps 1-3 from the instructions above. Click the Browse… button under the Log On tab.
- Type the name of your account in the “Enter the object name to select” entry box, click “Check Names,” and then wait for the name to become available.
- If you have set up a password, enter it when prompted in the Password box after clicking OK when you are finished. Now it ought to start without a hitch!