Open Event Viewer in Windows 10: 7 Ways

Event Viewer is Windows 10’s built-in tool for viewing application, security, and system logs. You can open it in at least seven ways, from the Start menu search to the Run dialog, Command Prompt, and PowerShell. Below are all the reliable methods, plus how to use the tool once it’s open.

Why You Need Event Viewer

Event Viewer records nearly everything that happens on your PC: program crashes, driver failures, Windows updates, security logins, and even hardware errors. When something goes wrong—like a sudden reboot or a blue screen—Event Viewer is often the first place to look for the underlying cause. It organizes these records into logs, each with a timestamp and an event ID, which you can search online or use to diagnose issues yourself.

For example, if your computer shuts down unexpectedly, you’d check Windows Logs → System and look for a red error event with ID 41 (Kernel-Power), which indicates the system rebooted without a clean shutdown. Similarly, a crashing application will log an error under Windows Logs → Application with the program name and a faulting module.

Method 1: Start Menu Search (Fastest)

1. Click the Start button (or press the Windows key).
2. Type Event Viewer.
3. Click the Event Viewer app that appears, or press Enter.

This works from the lock screen too—just click the power icon, then hold Shift and click Restart to reach the advanced startup options, where you can also launch Event Viewer from the troubleshooting menu.

Method 2: Run Dialog

1. Press Windows + R to open the Run box.
2. Type eventvwr.msc and press Enter.

The .msc extension stands for Microsoft Management Console snap-in; this is the same executable that the Start menu shortcut uses. You can also type just eventvwr—Windows will find it.

Method 3: Command Prompt or PowerShell

If you prefer the command line, open Command Prompt or PowerShell and type:

eventvwr.msc

Then press Enter. This launches the graphical interface. There’s no built-in command to view logs as text directly in the console, but you can use the wevtutil tool to export logs to a file. For example:

wevtutil epl System C:\system.evtx

That exports the System log to a file you can open later in Event Viewer.

Method 4: Control Panel

1. Open Control Panel (search for it in the Start menu).
2. Set the view to Large icons or Small icons.
3. Click Administrative Tools.
4. Double-click Event Viewer.

This path is longer than the others, but it’s useful if you’re already in Control Panel for another task.

Method 5: Computer Management

1. Right-click the Start button and select Computer Management.
2. In the left pane, expand System Tools and click Event Viewer.

Computer Management is a hub for several administrative tools, including Disk Management and Device Manager. Event Viewer appears as a sub-item, so this method is handy when you’re already managing other system components.

Method 6: Task Manager

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Click File → Run new task.
3. Type eventvwr.msc and click OK.

This is a good fallback if your desktop is unresponsive but you can still open Task Manager.

Method 7: Create a Desktop Shortcut

If you use Event Viewer often, make a permanent shortcut:

1. Right-click your desktop and select New → Shortcut.
2. In the location field, type eventvwr.msc.
3. Click Next, name it “Event Viewer,� and click Finish.

Understanding the Main Window

Once open, you’ll see three panes. The left pane lists log categories:

• Custom Views – pre-filtered views, including “Administrative Eventsâ€� which shows only warnings and errors.
• Windows Logs – Application, Security, Setup, System, and Forwarded Events.
• Applications and Services Logs – more specific logs from individual programs and Windows components.

The middle pane shows events for the selected log. Each event has a level (Information, Warning, Error, Critical), a date/time, a source (like “Kernel-Power� or “Service Control Manager�), and an event ID. Double-click any event to see details, including a description and sometimes a link to online help.

Common Problems and Fixes

If Event Viewer won’t open, try these steps in order:

1. Restart your PC—this clears temporary file locks.
2. Run sfc /scannow in an elevated Command Prompt to repair system files.
3. Check if the Windows Event Log service is running: press Windows + R, type services.msc, find Windows Event Log, and ensure it’s set to Automatic and started.
4. If the tool opens but shows no logs, the log files may be corrupted. You can clear them by right-clicking the log name (e.g., System) and selecting Clear Log.

Frequently Asked Questions

Can I open Event Viewer as administrator?

Yes. Right-click the Start menu shortcut and choose Run as administrator. Most actions don’t require admin rights, but some tasks like clearing logs or viewing security logs may prompt for elevation.

Why does Event Viewer show so many errors?

Many “errors� are harmless. For example, a service that failed to start once but then recovered is logged as an error, yet the system works fine. Focus on repeated errors with the same source and ID, and check the timestamp to see if they correlate with your problem.

Can I export Event Viewer logs?

Yes. Right-click a log (like System) and choose Save All Events As. You can save as .evtx (native format), XML, or CSV. To open a saved .evtx file on another PC, use Action → Open Saved Log.

Is Event Viewer the same as Reliability Monitor?

No. Reliability Monitor is a separate tool that shows a timeline of system stability. You can open it by typing perfmon /rel in the Run dialog. It’s easier to read but less detailed than Event Viewer.

How do I find the event that caused a blue screen?

Look under Windows Logs → System for events with source BugCheck or Kernel-Power (ID 41). The BugCheck event includes the bugcheck code (like 0x0000007E) which you can search online. For more detail, use the Reliability Monitor or check the minidump files in C:\Windows\Minidump.

Does Event Viewer slow down my PC?

No. The service runs in the background and writes logs as events occur. The disk space used is minimal unless you enable verbose logging for every event, which is not recommended.

Related

• Fix Microsoft Teams Keeps Crashing: 9 Real Fixes
• Open Registry Editor: 8 Ways That Work
• Apple Card: How It Works and What to Know