| Event Viewer Log | |
|---|---|
 | |
 Event Viewer in Windows 10 | |
| Developer | Microsoft |
| Operating system | Microsoft Windows |
| Service name | Windows Event log (eventlog) |
| Type | Utility software |
Event Viewer is a component ofMicrosoft'sWindows NToperating system that lets administrators and users view theevent logs, typically file extensions.evt and.evtx, 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. InWindows Vista, Microsoft overhauled the event system.[1]
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 bytechnical support scammers to trick the victim into thinking that their computer contains critical errors requiring immediate technical support.[2] 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.
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'sauthentication 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 aMicrosoft Management Console (MMC)snap-in.
Windows Server 2003 added theAuthzInstallSecurityEventSource() API calls so that applications could register with the security-event logs, and write security-audit entries.[3]
Versions of Windows based on the Windows NT 6.0 kernel (Windows Vista andWindows Server 2008) no longer have a 300-megabyte limit to their total size. Prior to NT 6.0, the system opened on-disk files asmemory-mapped files in kernel memory space, which used the same memory pools as other kernel components.
Event Viewer log-files withfilename extensionevtx typically appear in a directory such asC:\Windows\System32\winevt\Logs\
| eventquery.vbs, eventcreate, eventtriggers | |
|---|---|
| Developer | Microsoft |
| Initial release | October 25, 2001; 24 years ago (2001-10-25) |
| Operating system | Microsoft Windows |
| Type | Command |
| License | Proprietarycommercial software |
| Website | docs |
Windows XP introduced a set of threecommand-line interface tools, useful to task automation:
eventquery.vbs – Official script to query, filter and output results based on the event logs.[4] Discontinued after XP.eventcreate – a command (continued in Vista and 7) to put custom events in the logs.[5]eventtriggers – a command to create event driven tasks.[6] Discontinued after XP, replaced by the "Attach task to this event" feature, that is, from within the list of events,Right-Click on a single event and select from the pop-up menu.Event Viewer consists of a rewrittenevent tracing and logging architecture on Windows Vista.[1] It has been rewritten around a structuredXML 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 theDetails tab in an event's properties. It is also possible to view all potential events, their structures, registeredevent publishers and their configuration using thewevtutil 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 theApplication Logs node in theScope 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 theevent 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 limitedXPath 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.
Here are examples of simple custom filters for the new Window Event Log:
| Task | Filter |
|---|---|
| Select all events in the Security Event Log where the account name involved (TargetUserName) is "JUser" | <QueryList><Query Path="Security"><Select Path="Security">*[EventData[Data[@Name="TargetUserName"]="JUser"]]</Select></Query></QueryList> |
| Select all events in the Security Event Log where any Data node of the EventData section is the string "JUser" | <QueryList><Query Path="Security"><Select Path="Security">*[EventData[Data="JUser"]]</Select></Query></QueryList> |
| Select all events in the Security Event Log where any Data node of the EventData section is "JUser" or "JDoe" | <QueryList><Query Path="Security"><Select Path="Security">*[EventData[Data="JUser" or Data="JDoe"]]</Select></Query></QueryList> |
| Select all events in the Security Event Log where any Data node of the EventData section is "JUser" and the Event ID is "4471" | <QueryList><Query Path="Security"><Select Path="Security">*[System[EventID="4471"]] and *[EventData[Data="JUser"]]</Select></Query></QueryList> |
| Real-world example for a package called Goldmine which has two @Names | <QueryList><Query Path="Application"><Select Path="Application">*[System[Provider[@Name='GoldMine' or @Name='GMService']]]</Select></Query></QueryList> |
Caveats:
Majorevent subscribers include the Event Collector service andTask Scheduler 2.0. The Event Collector service can automatically forward event logs to other remote systems, runningWindows Vista,Windows Server 2008 orWindows 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 redesignedTask Scheduler and trigger automated actions when particular events take place.
