Use the Windows Event Viewer to troubleshoot problems by following the steps: 1. Open the "System" or "Applications" under "Windows Log" to filter the "Error" or "Serious" level to quickly locate the problem; 2. View the event ID and source fields, and combine it with network search to obtain solutions, such as Event ID 41 represents a power problem, and 6006/6008 represents a system startup and shutdown; 3. Create a custom view to set filter conditions to save, so that it is convenient to view specific logs directly next time.
Windows Event Viewer is a very useful tool, but many people have just opened it and don't know how to actually use it. In fact, it can help you check system problems, view software errors, and even track suspicious activities.

Find what you want to check: Browse the log
Event Viewer divides information into three categories by default: system logs, security logs and application logs.
The most common view of ordinary users is the "system" and "applications" under "Windows Log". For example, if a program crashes frequently, you can first click "Application" to see if there are any red error markings.
It is recommended to filter from the "event level", such as clicking "Error" or "Serious", so that you can quickly skip a lot of irrelevant information. You can also right-click a log and select "Event Properties", which will display a more detailed description and event ID. This information is very helpful for troubleshooting problems.

Understand the event ID and source: Don't miss the key details
Each event has a corresponding event ID and "Source" field. For example:
- Event ID 41 is usually related to power problems;
- Event ID 6006/6008 indicates the start and end of the event log service, that is, the time when the system starts and closes;
- Source tells you which component or program triggered this event.
If you encounter a specific error, you can use the source of the event ID as a keyword to search, and you can often find solutions to other people's problems.

Setting up custom views: only look at what you need
If it's too troublesome to flip it manually every time, you can use the Create Custom View feature to filter specific log types or event IDs. The steps are as follows:
- Click "Create Custom View" on the left
- Select log level (such as errors, warnings)
- You can enter a specific event ID or source
- After saving the name, it will appear under "Custom View"
After doing this, you only need to click on the next time to see the records of your concern, which is especially suitable for people who often need to troubleshoot specific problems.
Basically that's it. At first, you may feel that there is too much information, but as long as you know where to find and how to screen, Event Viewer is actually quite practical.
The above is the detailed content of how to use Event Viewer. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

When encountering the "Windowscan'taccesssharedfolderonnetwork", you can usually solve the problem through the following steps: 1. Turn on the network discovery and file sharing function and turn off password protection; 2. Make sure that the target computer is enabled to share and set the correct permissions; 3. Check the firewall rules and service status to ensure that it allows shared access; 4. Use the credential manager to add network credentials for long-term and stable connection.

When you encounter Windows stuck in the "GettingWindowsready, Don't turnoff your computer" interface, you should first confirm whether it is really stuck; 1. Observe whether the hard disk indicator light is flashing, 2. Check whether the fan sound has changed, 3. Wait at least 30 to 60 minutes to ensure that the system has enough time to complete the update operation.

When the Windows clipboard history is not working, you can check the following steps: 1. Confirm that the clipboard history function is enabled, the path is "Settings>System>Clipboard", and if it is not enabled, Win V will not respond; 2. Check whether the copy content type is limited, such as large images, special formats or file paths may not be saved; 3. Ensure that the system version supports it, Windows 101809 and above, and some enterprise versions or LTSC do not support it; 4. Try to restart the ClipboardUserService service or end the clipups.exe process; 5. Clear the clipboard cache or reset the settings, close and then turn on the "Clipboard History" or run the "echooff|clip" command to clean up the cache

To run programs as administrator, you can use Windows' own functions: 1. Right-click the menu to select "Run as administrator", which is suitable for temporary privilege hike scenarios; 2. Create a shortcut and check "Run as administrator" to achieve automatic privilege hike start; 3. Use the task scheduler to configure automated tasks, suitable for running programs that require permissions on a scheduled or background basis, pay attention to setting details such as path changes and permission checks.

When you encounter the prompt "Windowscannotfind'ms-settings:'", the system settings page usually cannot open normally. The solution is as follows: 1. Check the integrity of the system file and run the sfc/scannow and DISM/Online/Cleanup-Image/RestoreHealth commands as administrator; 2. Reset the default protocol handler and confirm that the default application of ms-settings is "Settings" in "Default Application By Protocol"; 3. Check whether the registry key HKEY_CLASSES_ROOT\ms-settings exists and is complete, and import the registry backup of the normal system if necessary; 4. Use the system

Wait for a few minutes and try to call out the task manager to confirm whether it is fake death; 2. Force shutdown to enter the recovery environment twice, use safe mode to uninstall the driver, turn off automatic login, and check and kill viruses; 3. Use other administrator accounts or new accounts to determine whether the user configuration file is damaged; 4. Uninstall or roll back the hardware driver, especially the graphics card driver, unplug the peripherals to troubleshoot hardware conflicts; 5. Use the sfc and DISM commands to repair the system files, and if it is invalid, back up the data and reinstall the system. When Windows is stuck in the welcome interface, you should first eliminate the false death situation, then check the user configuration, driver and system file integrity in turn, and finally consider reinstalling the system.

The error "This operation has been cancelled because of restrictions on the computer" is usually caused by permissions or policy restrictions. Solutions include: 1. Check whether to use an administrator account, and if not, switch or change the account type; 2. Run the program as an administrator, or set a shortcut to always run as an administrator; 3. Check Group Policy restrictions, set suspicious policies to "not configured" or "disabled", but be careful that there is no Group Policy Editor for the Home Edition; 4. If registry editing is disabled, you can re-enable it by creating a .reg file; 5. Troubleshoot third-party software interference, temporarily close the security software or management startup items. Trying the above methods in order usually solves the problem.

Don't rush to reinstall the system when the computer is stuck in the Windows restart interface. You can try the following methods first: 1. Force shutdown and then restart. Apply to the situation where the update is stuck. Repeat two or three times or can skip the lag; 2. Enter the safe mode to check, select Start repair or system restore through troubleshooting. If you can enter safe mode, it may be a driver or software conflict; 3. Use the command prompt to repair the system files, enter the three commands sfc and dism in the recovery environment to repair the damaged files; 4. Check the recently installed hardware or driver, unplug the non-essential devices or uninstall the new driver to eliminate incompatibility issues. In most cases, the above steps can solve the phenomenon of restart lag. If it really doesn’t work, consider reinstalling the system and paying attention to backing up data in advance.
