Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 36 Source: Microsoft-Windows-Time-Service
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
|English: Request a translation of the event description in plain English.|
EV100557 (Configuring external time source on your Primary Domain Controller) provides details on how to configure an external time source (such as a list of servers published by ntp.org) on your domain controller using PowerShell commands:
w32tm.exe /config /manualpeerlist:”0.us.pool.ntp.org 1.us.pool.ntp.org 2.us.pool.ntp.org 3.us.pool.ntp.org” /syncfromflags:manual /reliable:YES /update
w32tm.exe /config /update
This event may be recorded if the computer is unable to access the time server for more than a day. Some Internet time servers experience outages so a home computer relying on them for time synchronization may have troubles updating the time.
For a Windows Time Service Technical Reference see T773061.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated