How to Check Event Logs in Windows 11

To check event logs in Windows 11, right-click the Start button, select Event Viewer, expand Windows Logs in the left pane and select System or Application. Double-click any entry to read what happened, when it happened and which part of Windows reported it.

These steps apply to Windows 11 Home and Pro (versions 24H2 and 25H2). You can read most logs from a standard account, but you may need an administrator account to see the Security log.

Ways to Open Event Viewer

  • Start button menu: Right-click Start (or press the Windows logo key + X) and select Event Viewer.
  • Search: Select Start, type Event Viewer and select the app in the results.
  • Run box: Press the Windows logo key + R, type eventvwr.msc and press Enter. Typing eventvwr in Command Prompt also works.

Event Viewer opens with three panes: a tree of logs on the left, the list of events in the middle and an Actions pane on the right.

Path in Event Viewer: Windows Logs, then System.
Illustration: the path to the System log in Windows 11 Event Viewer.

Check a Windows Log

  1. Open Event Viewer using any of the methods above.
  2. In the left pane, select the arrow next to Windows Logs to expand it. You see Application, Security, Setup, System and Forwarded Events.
  3. Select System. The middle pane fills with events, newest first, with columns for Level, Date and Time, Source, Event ID and Task Category.
  4. Select an event. Its description appears on the General tab below the list.
  5. Double-click the event to open it in its own window, where you can copy the details or switch to the Details tab.

Start with the System log for crashes, restarts, driver and hardware problems. Check the Application log when a program crashes or won’t open.

What Each Log Records

Log What it records
Application Events from installed programs, such as app crashes and errors
Security Sign-ins, failed sign-in attempts and other audited security events (see how to check login history in Windows 11)
Setup Windows setup and update installation events
System Windows components, drivers, services, startups and shutdowns
Forwarded Events Events sent from other computers, usually empty on a home PC

Below Windows Logs, the Applications and Services Logs folder holds more detailed logs for individual Windows features and some apps. You rarely need these for everyday troubleshooting.

Advertisements

Understand Event Levels

  • Critical: A serious failure, such as Windows restarting without shutting down cleanly.
  • Error: Something failed, such as a service that didn’t start or a program that crashed.
  • Warning: Something might cause a problem later, such as low disk space.
  • Information: A normal action finished, such as a service starting.

The Security log uses Audit Success and Audit Failure instead. Errors and warnings show up even on a healthy PC, so focus on events that appear around the time your problem happened.

Filter the Log to Show Only Errors

A busy log can hold tens of thousands of entries. A filter cuts it down to the ones that matter.

  1. Select the log you want, such as System.
  2. Select Filter Current Log in the Actions pane. The Filter Current Log window opens.
  3. In the Logged menu, choose a time period such as Last 24 hours. Choose Custom range to set your own start and end time.
  4. Under Event level, check Critical and Error.
  5. To look for one event, type its number in the Event IDs box. Separate several numbers with commas, or use a range such as 4624-4634.
  6. Select OK. The list now shows only matching events.

To see everything again, select Clear Filter in the Actions pane. Microsoft’s page on filtering displayed events in Event Viewer lists every field in this window. A filter works on one log at a time. To search several logs at once, save it as a custom view, covered below.

Read an Event and Find Out What It Means

Every event has a Source (the part of Windows or the app that wrote it) and an Event ID (a number for that type of event). The same ID can mean different things from different sources, so search for both together, for example “Kernel-Power 41”.

A few events come up often when a PC restarts on its own. Event ID 41 from Kernel-Power means Windows restarted without shutting down cleanly, and Event ID 6008 from EventLog records that the previous shutdown was unexpected. Neither one names the cause by itself, so look at the events logged a few minutes before them.

If the problem is a blue screen, combine what you find here with our guide to fixing the blue screen of death in Windows 11.

Save a Filter as a Custom View

If you check the same events often, save your filter so it’s one click away.

  1. Select Create Custom View in the Actions pane.
  2. Choose the time period and event levels, then select By log and check every log you want to include, such as System and Application.
  3. Select OK, type a name and select OK again.

Your view appears under Custom Views at the top of the left pane. Windows also includes a built-in view there named Administrative Events that gathers critical events, errors and warnings from the main logs.

Use Reliability Monitor for a Simpler Timeline

Reliability Monitor reads many of the same records and shows them as a day-by-day chart. Each day gets a stability score from 1 to 10, with icons for app failures, Windows failures and warnings. It’s often the quickest way to see when a problem started.

  1. Open Control Panel and select Security and Maintenance.
  2. Expand Maintenance.
  3. Select View reliability history. The chart opens with a details table below it.

Select a day to see what failed. For some entries, a View technical details link shows more information. Our guide to checking crash logs in Windows 11 shows how to use both tools together.

Event Viewer and Reliability Monitor answer different questions, so it helps to know which one to open first.

Comparison of Event Viewer and Reliability Monitor in Windows 11.
Illustration: when to open Event Viewer and when to open Reliability Monitor.

Check Event Logs With PowerShell

If you prefer a command line, PowerShell can read the same logs. To see the 20 newest events in the System log, run:

Get-WinEvent -LogName System -MaxEvents 20

To list only errors from the System log, run:

Get-WinEvent -FilterHashtable @{ LogName=’System’; Level=2 }

Level 1 is Critical, 2 is Error and 3 is Warning. If PowerShell reports that it can’t retrieve information about a log, run PowerShell as an administrator and try again. Microsoft’s Get-WinEvent reference has more filter options.

Save or Share a Log

A support technician may ask for a copy of a log. Right-click the log in the left pane and select Save All Events As. If you’ve applied a filter, select Save Filtered Log File As in the Actions pane to save only those events. The .evtx format opens in Event Viewer on another PC, and you can also choose a text or CSV file. Once you’ve found the right log, the walk-through on how to use Event Viewer in Windows 11 shows how to filter it and save custom views.

Troubleshooting

The Security log won’t open

Sign in with an administrator account, or right-click Event Viewer in the Start search results and select Run as administrator.

The list is too long to make sense of

Note the time your problem happened, then filter for Critical and Error events in a short window around it. A one-hour range usually leaves only a handful of entries.

Older events are missing

Each log has a size limit, and Windows overwrites the oldest events when it’s full. Right-click the log, select Properties and raise the Maximum log size to keep more history.

Event Viewer is slow to load

Large logs take time to read. Give it a minute, or open a custom view instead of a full log.

Questions

Do errors in Event Viewer mean something is wrong with my PC?

Not on their own. Windows and apps log errors routinely, and many of them never cause a visible problem. An error is worth looking into when it repeats often or lines up with a crash, freeze or failed restart.

Can I clear the event logs?

Yes. Select a log and choose Clear Log in the Actions pane. Event Viewer offers to save a copy first. Clearing removes the history you’d need to trace a problem, so only do it to start a clean record before you test a fix.

Do event logs survive a restart or crash?

Yes. Windows writes the logs to files on your drive, so you can check them after the PC restarts. That’s what makes them useful after a sudden shutdown.

Will Event Viewer fix the problem for me?

No. It only records events. Use the source and event ID to find the cause, then fix it with the right tool, such as a driver update or a system file scan.

Next, if your logs point to a crash, use our guide on finding out why your computer crashed on Windows 11 to narrow down the cause.

Advertisements