Skip to content

Event ID 133: NtpClient was unable to set a domain peer to use a time source because of an unexpected error

Windows Event ID Lookup: What Windows event IDs mean: 4625, 4624, 4740, 6008, 41, 7045, 1102 and 3,000 more, with Windows' own message text, the fields and what to check.

Look up a Windows event ID from Event Viewer, a SIEM alert or a log export: what it means, the fields it records, and what to check. Many IDs are used by more than one source (event 41 is both a Kernel-Power crash and a boot error), so every definition is shown, the one people usually mean first. The message text is Windows' own, read from the event providers of Windows 10.0.26200.0, 2026-10-28; the notes are ours, based on Microsoft's security auditing reference.

Try: 4625, 4624, 4740, 6008, 41, 1074, 7045, 1102, 4104, 1149

NtpClient was unable to set a domain peer to use a time source because of an unexpected error.

Event 133
Time-Service
System log
Warning
Message and fields (as Event Viewer shows them)
NtpClient was unable to set a domain peer to use a time source because of an unexpected error.  NtpClient will try again in … minutes and double the reattempt interval thereafter. The error was: …

Task Scheduler failed to start task …" in TaskEngine "…" for user "…".

Event 133
TaskScheduler
TaskScheduler/Operational log
Error
Message and fields (as Event Viewer shows them)
Task Scheduler failed to start task …" in TaskEngine "…"  for user "…". User Action: Reduce the number of tasks running in the specified user context.