How to Resolve Event Viewer Not Working in Windows 10 and 11

Windows Event Viewer logs all system activities and errors, enabling users to identify the cause of problems and troubleshoot them in time. However, several Windows 10 and 11 users reported the Event Viewer not working for reasons such as system file corruption, memory problems, etc.

This article, therefore, provides simplified steps for resolving the issue so you don’t miss important system health, performance, and security information.

What is the Event Viewer, and why is it not working?

There are various types of events: information, warning, error, and Security log. Irrespective, they all perform these functions in the Windows Event Viewer apart from the custom view access to PC activities:

• Allows access and manage system events logs, errors, and other system information.
• Helps in troubleshooting system problems.
• Provides real-time monitoring of the system’s health and performance.
• The Event Viewer also helps users to monitor and analyze system security in case of security breaches.

In addition, you are likely to encounter some of these errors: Event Log service is unavailable. Verify that the service is running; Access denied. You do not have sufficient privileges to access the event log; Error 1079. etc.

Now that you know what the Event Viewer does and some potential reasons why it may not work as outlined above, let’s proceed to the fixes.

What causes the Event Viewer not to work?

Some common and prominent issues that cause problems in Event Viewer are:

• Problems with Event Viewer services – If services such as Event Log, Task Scheduler, and Windows Event Calendar are not working, it can affect the Event categories. However, restarting the services should restore functionality.
• Event ID troubleshooting – You should be aware of standard Event IDs like 6008 (unexpected shutdown), 7031 (service termination), and 10016 (DCOM permissions issue) as they provide valuable information for troubleshooting system errors and identifying underlying causes.
• Permission issues with Event Viewer – Access permission problems can prevent Event Viewer from functioning correctly. To resolve them, grant necessary permissions through the Local Security Policy or control panel.
• System file corruption – If the log files become corrupted, it may fail to open or display events correctly. Hence, this will result in the Event Viewer’s malfunction.
• Hardware failures – Issues like faulty storage devices, can negatively impact Event Viewer’s performance.

How do I fix Event Viewer not working?

Before anything else, kindly try these preliminary checks:

• Perform a clean boot to identify any software conflicts that could cause the error event.
• Run the Windows memory diagnostic tool to inspect for any hardware issues.
• Perform a Windows update to fix critical events.
• Clear the old log files in Event Viewer to free up space for new events to be logged.
• Ensure to run the Check Disk Utility to fix any disk errors prompting this issue.
• Consider booting into Safe mode to isolate the Event Viewer app. 
• Consider running SFC and DISM scans to rule out the possibility of system file corruption.

If they fail to curb the issue, try the following tweaks.

1. Restart the Windows Event Log service

1. Press the Windows + R keys to open Run. Type services.msc in the command dialog box and press Enter.
2. Right-click on Windows Event Log service and select Restart.
3. Now, close the Services snap-in window and relaunch Event Viewer to see if the issue is fixed.

Some users claim they could fix the Event Viewer not working issue by merely restarting the Windows Event Log service.

2. Create a new user account

1. Press the Windows + I keys to open the Settings app.
2. Navigate to Accounts and click Other users.
3. Then, click on Add account.
4. In the Microsoft account window, click on I don’t have this person’s sign-in information and follow the on-screen instructions to create a new user account.

Once you’ve created a new user account, sign in with the credentials and check if the issue persists.

3. Review log security settings

1. Open File Explorer and navigate to this path: C:\Windows\System32\winevt\Logs
2. Right-click on the folder and select Properties.
3. Go to the Security tab. Check permissions for necessary users/groups.
4. If the required permissions are missing, click on Edit, then click on Add in the Permissions window to add users/groups.
5. Now, configure appropriate permissions for added users/groups.
6. Click on Apply and OK to save the changes.

If your File Explorer is not opening, check out our detailed guide.

4. Use the Windows Registry to grant full permission

1. Open the Registry Editor and navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog
2. Right-click the EventLog key and select Permissions.
3. Grant Full Control permissions to Administrators and SYSTEM.
4. Click Apply and then OK to save the changes.
5. Close the Registry Editor and restart your PC.

If you have issues with the Registry Editor, you can fix them here.

Read more about this topic

• Libgdk-win32-2.0-0.dll Not Found: 7 Ways to Fix It
• 6 Ways to Fix Bdvid32.dll Not Found
• 6 Ways to Fix the AWL.DLL Missing Error
• 6 Ways to Fix the Macdll.dll Missing Error

5. Overwrite old log files

1. Open Event Viewer by searching for it in the Windows Start menu.
2. Navigate to the desired log category (Windows Logs or Applications and Services Logs) and select Properties.
3. In the Properties window, under the General tab, you will find the Log size, and adjust the overwriting options.
4. Set maximum log size or retention days if needed.
5. Click OK to save the changes.
6. Repeat for other log categories as desired.

By modifying the log settings, you can configure how logs overwrite events when they reach maximum size. Hence, protecting important events from getting lost due to log size limitations. 

As stated earlier, it is essential to troubleshoot the issue to ensure consistency in events logging quickly. Although there may be several causes for this problem, following our guide should ease the troubleshooting process.

If you need a third-party event log analyzer tool that provides free and advanced analysis, select from our best options.

Also, please leave your questions or suggestions in the comments section below.