FIX: w32tm /resync Computer did not resync error

The Command Prompt displays that error message for some users when they try to sync time with the w32tm /resync command. Check out these resolutions if you need to fix that issue.

How can I fix The computer did not resync error?

1. Reconfigure Windows Time Service Group Policy objects

1. To do that, launch Run with the Windows key + R keyboard shortcut.
2. Open Group Policy Editor by entering gpedit.msc in Run and clicking OK.
   
3. Click Computer Configuration to expand it.
4. Then double-click Administrative Templates on the left of the window.
5. Select System and Windows Time Service, which includes a Global Configuration Settings policy.
   
6. Double-click Global Configuration Settings policy to open further options for it.
7. Select the Not Configured radio button on the window that opens.
8. Click OK to confirm.
9. Then select Time Providers on the left of the window.
   
10. Double-click Configure Windows NTP Client, Enable Windows NTP Client, and Enable Windows
11. NTP Server to open those setting windows.
12. Then select the Not Configured options for Configure Windows NTP Client, Enable Windows NTP Client, and Enable Windows NTP Server.
13. Click the Apply buttons on the windows to save changes.
14. Thereafter, you’ll need to restart Windows for changes to come into effect.

Microsoft’s official resolution for The computer did not resync error is to reconfigure Windows Time Service Group Policy objects to Not Configured.

2. Edit the registry

1. Open Run’s Open text box.
   
2. Type regedit the Open box, and click the OK button.
3. Open this registry key:
   • HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/W32Time/Parameters

4. Double-click the Type string to open the window in the snapshot below.
5. If the Type string isn’t there, right-click an empty space on the right of the window and select New, then select String Value. Enter Type in the text box for the new string.
6. Clear the Value data box. Then enter NT5DS in the Value data box.
7. Click the OK button.
8. Thereafter, restart Windows.

3. Run an extended Windows Time (w32tm) command

1. An extended w32tm command might fix The computer did not resync error. Open the search tool with the Windows key + S hotkey.
2. Enter the keyword cmd to search for Command Prompt.
3. Right-click Command Prompt and select Run as administrator to open an elevated Prompt.
4. Type this lengthy command into the Prompt’s window:

   w32tm /config /manualpeerlist:time.windows.com,0x1/syncfromflags:manual/reliable:yes /update

5. Press the Enter key to initiate the command.

So, that’s how you can fix The computer did not resync error so Windows syncs with time server. Those remedies will probably be enough to fix the issue for the majority of users.

However, there might be other resolutions; and users who have fixed the same issue with other methods are welcome to share them below.

FAQ: Learn more about Windows Sync

• What can cause the computer did not resync error?

The main cause for such an error is when your PC’s time doesn’t sync with that of your NTP server.

• How do I notice this error?

This error will usually be displayed in an open Command Prompt or PowerShell window.

• How do I fix the Windows Sync issue for multiple PCs?

One way to fix this issue on multiple PCs without wasting time is to simply use a Group Policy to edit the Time Service.

Still having issues? Fix them with this tool:

This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix
PC issues and remove viruses now in 3 easy steps:

1. Download this PC Repair Tool rated Great on TrustPilot.com (download starts on this page)
2. Click Start Scan to find Windows issues that could be causing PC problems.
3. Click Repair All to fix issues with Patented Technologies (Exclusive Discount for our readers).

• Restoro has been downloaded by 0 readers this month.

Editor’s Note: This article was originally published in March 2020 and was revamped and updated in January 2021 for freshness, accuracy, and comprehensiveness.