Windows 11 / Three Ways to Open Event Viewer and Check Recent Logs
To open Event Viewer in Windows 11, press Windows + R, enter eventvwr.msc and press Enter. You can also find it through Start search or the Start button’s right-click menu. Event Viewer displays records of Windows and app events; the number of errors or warnings alone does not establish whether a PC is faulty.
Three Ways to Open Event Viewer
In the Run dialog, press Windows + R, enter the command below, and press Enter. The expected result is that the Event Viewer window opens.
eventvwr.msc
To use the menu, choose the method that is convenient for you.
- Search for Event Viewer in the Start menu and select the app.
- Right-click the Start button and select Event Viewer.
These three paths are also described in Microsoft's Windows System Configuration Tools Guide. Depending on the display language, the app name may vary, such as Event Viewer, but the run command is the same.
Location of Windows Logs and Items to Read
Expand Windows Logs in the left tree and choose a log. Start with the action that failed and when it happened, rather than trying to interpret every log at once.
- Application: Select this to examine events recorded by apps. It can be a starting point for checking symptoms like app launch failures.
- System: Review events related to Windows components and the system. Check the time the symptom occurred along with related messages.
- Security: Contains events related to security auditing such as logon. The records you see may vary depending on account permissions and audit settings, so there is no need to change security settings just to practice reading app errors.
When you select a log, you can choose an event from the list in the center. Select an item or double-click to open it and read the following information together.
- Date and time, log name: verify that you are viewing the intended PC and log, then compare the event time with the actual symptom time.
- Source and Event ID: The source is the component that recorded the entry, and the event ID is the identifier of the event defined by that source.
- Level and Message: Check not only the level such as error or warning but also the message in the General tab and any necessary details.
Exercise: Find Application Events from the Last Hour
This exercise teaches you to view existing records. Do not deliberately break an app or change security settings to generate events. For a real issue, record the symptom time and app name first. If a filter is already in use, note its conditions before changing them.
- In Event Viewer, select Windows Logs → Application.
- Right-click the Application log and select Filter Current Log. You can also find the same function in the right-hand action pane.
- From the Logged period, select Last hour. Initially, do not restrict by a specific source, event ID, or level of error; start by narrowing the time range first.
- Click OK and check the time of the events that appear in the list. Open one entry and record the log name, source, event ID, and message.
- If there are no entries in the selected period, note the result as it is. Only widen the period and check again if necessary, and do not assume the Event Viewer is malfunctioning just because there are no records.
- After the exercise, reopen Filter Current Log, select Clear inside that dialog and select OK to reset the query conditions. If you had a pre-existing filter, restore the conditions you recorded earlier.
The expected outcome is to view a list that matches the selected time range and to be able to read the original source, ID, and message of individual events. Microsoft’s guidance for filtering app logs in the event viewer also explains how to narrow the range by the level or a recording period such as the last hour under Windows Logs → Application.
Clear inside the filter dialog resets query conditions; Clear Log deletes stored events. Use the filter reset for this exercise and keep the original events available for investigation.
Points to be careful about when interpreting errors and event IDs
If you search by event ID alone, you might confuse the same number from different sources. Microsoft’s event definition documents explain that providers define the events and identification numbers they record. It is more accurate to check the source, event ID, Windows/app version, and message together.
Do not conclude that an event is the cause merely because the recorded time is similar to the symptom. Compare whether it is a record remaining after the app closed, whether it is a repeated record right before the problem occurred, and the surrounding events. Records at the informational level can also help understand the sequence of operations, so do not hide everything and leave only errors from the start.
Events are clues for observation. Instead of stopping services in bulk or changing the registry to remove an old warning, first check whether the relevant records repeat under conditions like those of the actual failed function.
Save filtered logs and review them before sharing
If you need to deliver the original record to the person in charge, keeping the event files for the necessary range is more helpful for analysis than just writing down the number visible on the screen. First, check if there are events to save and the current filter conditions.
- Right-click the filtered application log and select Save Filtered Log File As.
- Specify a location and an easily distinguishable name. For example, you can save it in the Windows event log file format .evtx like event-viewer-practice.evtx.
- If a dialog asking for the display information language appears, select the display language needed on the target PC where the file will be opened.
- Check that the file was created in the specified folder, and separately record which logs and time ranges were exported.
Microsoft’s procedure for exporting event logs as EVTX also explains saving filtered logs and choosing the display-information language. This article uses only the shared export feature; it does not apply the server security-policy configuration in that document.
Event files may include the computer name, account names, internal paths, and message content. Before posting directly on public boards, confirm the necessary recipients and scope. It is recommended to separately retain the original file and only summarize the necessary parts in public explanations.
If the desired events are not visible
- Check if the current filter’s period, source, ID, or level is too narrow. Review the filter conditions and the selected logs separately.
- If it is not in the application log, check the system logs related to the symptoms or the log location of the corresponding app. Not all apps record all actions in Windows logs.
- Check whether you are viewing logs from a remote PC instead of the current PC. Also, match the record times to the actual times when the symptoms occurred.
- If the log cannot be opened due to permissions, verify access rights or consult the administrator. Do not arbitrarily change audit policies or log retention settings just to view records.




