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.
Firmware update supported status is …. The BitLocker device flags are … and the PCR bitmap is ….
The Windows Update Client Core component was successfully updated from version … to version
Event 36
WindowsUpdateClient
System log
Information
Message and fields (as Event Viewer shows them)
The Windows Update Client Core component was successfully updated from version … to version ….
The time service has not synchronized the system time for the last … seconds because none of the time service providers provided a usable time stamp.
Event 36
Time-Service
System log
Warning
Message and fields (as Event Viewer shows them)
The time service has not synchronized the system time for the last … 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 after … seconds. 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. You can control the frequency of the time source rediscovery using ClockHoldoverPeriod W32time config setting. Modify the EventLogFlags W32time config setting if you wish to disable this message.
An error occurred when transitioning from … in response to