Windows Event Log

Event Viewer is a component of Microsoft's Windows NT operating system that lets administrators and users view the event logs on a local or remote machine. Applications and operating-system components can use this centralized log service to report events that have taken place, such as a failure to start a component or to complete an action. In Windows Vista, Microsoft overhauled the event system.

Due to the Event Viewer's routine reporting of minor start-up and processing errors (which do not, in fact, harm or damage the computer), the software is frequently used by technical support scammers to trick the victim into thinking that their computer contains critical errors requiring immediate technical support. An example is the "Administrative Events" field under "Custom Views" which can have over a thousand errors or warnings logged over a month's time.

Overview

Windows NT has featured event logs since its release in 1993.

The Event Viewer uses event IDs to define the uniquely identifiable events that a Windows computer can encounter. For example, when a user's authentication fails, the system may generate Event ID 672.

Windows NT 4.0 added support for defining "event sources" (i.e. the application which created the event) and performing backups of logs.

Windows 2000 added the capability for applications to create their own log sources in addition to the three system-defined "System", "Application", and "Security" log-files. Windows 2000 also replaced NT4's Event Viewer with a Microsoft Management Console (MMC) snap-in.

Windows Server 2003 added the AuthzInstallSecurityEventSource() API calls so that applications could register with the security-event logs, and write security-audit entries.

Versions of Windows based on the Windows NT 6.0 kernel (Windows Vista and Windows Server 2008) no longer have a 300-megabyte limit to their total size. Prior to NT 6.0, the system opened on-disk files as memory-mapped files in kernel memory space, which used the same memory pools as other kernel components.

Event Viewer log-files with filename extension evtx typically appear in a directory such as C:\Windows\System32\winevt\Logs\

Command-line interface

Windows XP introduced set of three command-line interface tools, useful to task automation:
* eventquery.vbs – Official script to query, filter and output results based on the event logs. Discontinued after XP.
* eventcreate – a command (continued in Vista and 7) to put custom events in the logs.
* eventtriggers – a command to create event driven tasks. Discontinued after XP, replaced by the "Attach task to this event" feature.

Windows Vista

Event Viewer consists of a rewritten event tracing and logging architecture on Windows Vista. It has been rewritten around a structured XML log-format and a designated log type to allow applications to more precisely log events and to help make it easier for support technicians and developers to interpret the events.

The XML representation of the event can be viewed on the ''Details'' tab in an event's properties. It is also possible to view all potential events, their structures, registered ''event publishers'' and their configuration using the ''wevtutil'' utility, even before the events are fired.

There are a large number of different types of event logs including Administrative, Operational, Analytic, and Debug log types. Selecting the ''Application Logs'' node in the ''Scope'' pane reveals numerous new subcategorized event logs, including many labeled as diagnostic logs.

Analytic and Debug events which are high frequency are directly saved into a trace file while Admin and Operational events are infrequent enough to allow additional processing without affecting system performance, so they are delivered to the Event Log service.

Events are published asynchronously to reduce the performance impact on the ''event publishing'' application. Event attributes are also much more detailed and show EventID, Level, Task, Opcode, and Keywords properties.

Users can filter event logs by one or more criteria or by a limited XPath 1.0 expression, and custom views can be created for one or more events. Using XPath as the query language allows viewing logs related only to a certain subsystem or an issue with only a certain component, archiving select events and sending traces on the fly to support technicians.

Filtering using XPath 1.0

# Open Windows Event Log
# Expand out ''Windows Logs''
# Select the log file that is of interest (In the example below, the ''Security'' event log is used)
# Right-click on the Event Log and select ''Filter Current Log...''
# Change the selected tab from ''Filter'' to ''XML''
# Check the box to ''Edit query manually'
# Paste the query into the text box. Sample queries can be found below.

Here are examples of simple custom filters for the new Window Event Log:
# Select all events in the Security Event Log where the account name involved (TargetUserName) is "JUser"
#: * ventData[Data[@Name="TargetUserName""JUser".html" ;"title="ata[@Name="TargetUserName".html" ;"title="ventData[Data[@Name="TargetUserName"">ventData[Data[@Name="TargetUserName""JUser"">ata[@Name="TargetUserName".html" ;"title="ventData[Data[@Name="TargetUserName"">ventData[Data[@Name="TargetUserName""JUser"
# Select all events in the Security Event Log where any Data node of the EventData section is the string "JUser"
#: *[EventData[Data="JUser"
# Select all events in the Security Event Log where any Data node of the EventData section is "JUser" or "JDoe"
#: * ventData[Data="JUser" or Data="JDoe"
# Select all events in the Security Event Log where any Data node of the EventData section is "JUser" and the Event ID is "4471"
#: *[System[EventID="4471" and *[EventData[Data="JUser"
#Real-world example for a package called Goldmine which has two @Names
#: * ystem[Provider[@Name='GoldMine'_or_@Name='GMService'.html" ;"title="Name='GoldMine'_or_@Name='GMService'.html" ;"title="ystem ystem[Provider[@Name='GoldMine'_or_@Name='GMService'">Name='GoldMine'_or_@Name='GMService'.html"_;"title="ystem[Provider[@Name='GoldMine'_or_@Name='GMService'">ystem[Provider[@Name='GoldMine'_or_@Name='GMService'/Select>

Caveats:
*_There_ar
limitations
to_Microsoft's_implementation_of_XPath
*_Queries_using_XPath_1.0#String_functions.html" ;"title="rovider[@Name='GoldMine' or @Name='GMService'">ystem[Provider[@Name='GoldMine' or @Name='GMService'">Name='GoldMine'_or_@Name='GMService'.html" ;"title="ystem[Provider[@Name='GoldMine' or @Name='GMService'">ystem[Provider[@Name='GoldMine' or @Name='GMService'/Select>

Caveats:
* There ar
limitations
to Microsoft's implementation of XPath
* Queries using XPath 1.0#String functions">XPath string functions will result in error

Event subscribers

Major ''event subscribers'' include the Event Collector service and Task Scheduler 2.0. The Event Collector service can automatically forward event logs to other remote systems, running Windows Vista, Windows Server 2008 or Windows Server 2003 R2 on a configurable schedule. Event logs can also be remotely viewed from other computers or multiple event logs can be centrally logged and monitored without an agent and managed from a single computer. Events can also be directly associated with tasks, which run in the redesigned Task Scheduler and trigger automated actions when particular events take place.

See also

* List of Microsoft Windows components
* Microsoft Management Console
* Technical support scam

References

External links

* Official sources:
*
Event Viewer - Inside Show
o
Microsoft Learn
*
Events and Errors
(Windows Server 2008) o
Microsoft Learn

{{Windows commands

Windows components
Computer logging
Windows administration

HOME


Content is Copyleft
Website design, code, and AI is Copyrighted (c) 2014-2017 by Stephen Payne


Consider donating to Wikimedia



As an Amazon Associate I earn from qualifying purchases