Finally, right-click on the Windows 10 update, and select Hide Update to make sure you don't install it by mistake.Starting with Windows XP Service Pack 2 Microsoft offered an enhanced firewall that restricts communication to external sites.In the Service status click on the "Start" button to start the time service. A great deal of synchronization problems may be caused by network break downs, unpredicted traffic delays, unknown accuracy and public NTP servers where you don't have control over.Although public time service may be cost free, but 24/7 operation, accuracy and customer support in case of a failure is not guaranteed.If your Windows 7 or 8.1 PC is set to install recommended updates automatically (because -- more fool you -- you just wanted it to be up to date and safe) then Microsoft will cheerfully download the new OS and start the installation process for you. Windows 10 will still appear as an available update, but it won’t be automatically installed now. Look for the Recommended updates entry and make sure it’s unchecked. In Windows 8.1 you can either follow the same steps listed above, or you can go through the PC Settings app.
If the status of the Windows Time is currently not shown, then right click and choose Properties to open "Windows Time Properties (Local Computer)" window.w32time sends namely symmetric active instead of client mode packets to a NTP server.This problem has not been observed with the w32time version which has been shipped with Windows 2000, only with later versions.For details of Windows firewall port settings, click on Figure 1,2 and 3.
Especially those coming with Windows XP or Windows Server 2003, may be (by default) unable to query the time from some NTP servers. standalone server or domain controller), NTP servers may not respond to the type of queries sent by w32time.
We've provided a list of the most common causes of NTP time sync troubles.