Every Windows 10 user needs to know about Event Viewer. Windows has had an Consequence Viewer for almost a decade. Few people know nigh it. At its heart, the Upshot Viewer looks at a small scattering of logs that Windows maintains on your PC. The logs are elementary text files, written in XML format.

Although you lot may think of Windows as having one Event Log file, in fact, there are many — Administrative, Operational, Analytic, and Debug, plus awarding log files.

The Consequence Viewer logs

Every program that starts on your PC posts a notification in an Event Log, and every well-behaved program posts a notification before it stops. Every system access, security change, operating system twitch, hardware failure, and commuter hiccup all stop up in one or some other Issue Log.

The Consequence Viewer scans those text log files, aggregates them, and puts a pretty interface on a deathly slow, voluminous set of machine-generated information. Think of Event Viewer as a database reporting plan, where the underlying database is just a handful of elementary flat text files.

In theory, the Effect Logs rail "pregnant events" on your PC. In practice, the term "significant" is in the eyes of the beholder. Or developer. In the normal course of, uh, events, few people e'er demand to look at whatever of the Event Logs. But if your PC starts to plough sour, the Event Viewer may give you important insight to the source of the problem.

How to find the Result Viewer

Follow these steps:
  1. Click in the Search field in the lesser left corner of your screen. Search for Effect Viewer. Click on Event Viewer in the search results.

    The Event Viewer appears.

  2. On the left, choose Custom Views and, underneath that, Administrative Events.

    It may take a while, but eventually you see a list of notable events similar the one shown.

  3. Don't freak out.

    Even the best-kept system boasts reams of scary-looking fault letters — hundreds, if not thousands of them. That'due south normal. Run across the table for a breakup.

    Events are logged by various parts of Windows.

    Events are logged by diverse parts of Windows.

Events and what they mean
Outcome What Caused the Event
Error Pregnant problem, peradventure including loss of data
Warning Non necessarily pregnant, but might indicate that at that place'south a problem brewing
Information Just a program calling domicile to say information technology'southward okay

Other logs to check out

The Authoritative Events log isn't the just 1 yous tin can see; it's a distillation of the other result logs, with an emphasis on the kinds of things a mere human might want to see.

Other logs include the following:

  • Awarding events: Programs study on their issues.

  • Security events: They're called "audits" and show the results of a security activity. Results tin exist either successful or failed depending on the outcome, such as when a user tries to log on.

  • Setup events: This primarily refers to domain controllers, which is something you don't need to worry about.

  • Organisation events: Nigh of the errors and warnings you meet in the Authoritative Events log come from organization events. They're reports from Windows organization files about problems they've encountered. Well-nigh all of them are self-healing.

  • Forwarded events: These are sent to this calculator from other computers.

About This Article

About the book authors:

Woody Leonhard was one of the first Microsoft consulting partners and Microsoft beta testers. Leonhard has been honored with multiple Reckoner Press Awards and runs his own weblog sharing news, communication, and support tips for Windows at AskWoody.com.

This commodity tin can be found in the category:

  • Windows x ,