- The NTP client syncs its time with the manually specified NTP server.
- The NTP client uses SpecialPollInterval as a polling interval.
- The time offset between the NTP client and the NTP server is greater than the LargePhaseOffset as configured in the NTP client.
To have us configure Windows Time to use the MinPollInterval/MaxPollInterval as the polling interval for you, go to the "Here's an easy fix" section. If you prefer to configure Windows Time to use the MinPollInterval/MaxPollInterval as the polling interval yourself, go to the "Let me fix it myself" section.
Note If you set Windows Time Service's settings by Group Policy or Local Group Policy, this "Easy fix" method does not work and you have to delete policy settings.
Here's an easy fixTo configure Windows Time to use the MinPollInterval/MaxPollInterval as the polling interval, click the Download button. In the File Download dialog box, click Run or Open, and then follow the steps in the easy fix wizard.
- This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
- If you’re not on the computer that has the problem, save the easy fix solution to a flash drive or a CD, and then run it on the computer that has the problem.
For Windows 10, Windows 8.1, Windows Server 2012 R2, Windows 8, and Windows Server 2012
For Windows 7, Windows Vista, Windows Server 2008 and Windows Server 2008 R2
To avoid this issue, the registry key should apply conditional expression as follows:
If the value of the NtpServer entry in this subkey contains 0x1, Windows Time uses SpecialPollInterval as the polling interval. Otherwise, Windows Time uses MinPollInterval/MaxPollInterval. For additional Information about the Windows Time Service and registry values, visit the following Microsoft Web site:
Article ID: 2638243 - Last Review: Mar 8, 2016 - Revision: 1