Fix Event Viewer Not Working on Windows 10 & 11

If Event Viewer won’t open, shows a blank window, or fails to load logs on Windows 10 or 11, the fix usually involves restarting the Windows Event Log service, repairing corrupted log files, or running System File Checker. Below are the most effective troubleshooting steps, from quick checks to deeper repairs, so you can get your event logs back.

Why Event Viewer Fails

Event Viewer depends on the Windows Event Log service (eventlog) and a set of .evtx files stored in C:\Windows\System32\winevt\Logs. When it stops working, the cause is often one of these:

• The Event Log service is stopped or disabled.
• Log files are corrupted, oversized, or have incorrect permissions.
• System files are damaged (e.g., after a failed update).
• Third-party software or a recent Windows update changed service settings.
• The Event Viewer snap-in (eventvwr.msc) is blocked by Group Policy or a corrupted profile.

Quick Fixes to Try First

Before diving into advanced repairs, try these simple steps. They resolve many common issues.

1. Restart the Event Log service: Press Win + R, type services.msc, and press Enter. Find Windows Event Log, right-click it, and select Restart. If it’s not running, set Startup type to Automatic and start it.
2. Run Event Viewer as administrator: Right-click the Start button, choose Event Viewer (Admin) or search for it, right-click, and select Run as administrator.
3. Clear the log cache: In Event Viewer, right-click a log (like Application) and choose Clear Log…. This deletes old entries, which can fix display issues.
4. Check the log file size: In Event Viewer, right-click a log, select Properties, and set a reasonable maximum size (e.g., 20 MB). Enable Overwrite events as needed.

Repair Corrupted Event Log Files

If the service starts but logs are unreadable or missing, the .evtx files may be corrupt. You can safely delete them—Windows will recreate them automatically.

1. Open an elevated Command Prompt (Run as administrator).
2. Stop the Event Log service with: net stop eventlog
3. Navigate to the logs folder: cd C:\Windows\System32\winevt\Logs
4. Delete the problematic .evtx files. For example, del Application.evtx. You can delete all files here if you don’t mind losing old logs.
5. Restart the service: net start eventlog

If the service fails to stop, you may need to boot into Safe Mode or use a recovery environment.

Run System File Checker and DISM

Corrupted system files can break Event Viewer. Use the built-in Windows tools to repair them.

1. Open Command Prompt as administrator.
2. Run sfc /scannow and wait for it to complete.
3. If SFC finds errors, run DISM /Online /Cleanup-Image /RestoreHealth and then run SFC again.

These commands take 10-20 minutes. They don’t remove personal files, but it’s wise to back up important data before a system repair.

Check Group Policy and Registry Settings

Sometimes Event Viewer is disabled by policy or its registry entries are wrong.

• Group Policy: Press Win + R, type gpedit.msc (Pro/Enterprise only). Navigate to User Configuration > Administrative Templates > Start Menu and Taskbar. Ensure Remove Run menu from Start Menu is set to Not Configured or Disabled.
• Registry: Open regedit.exe and go to HKEY_CURRENT_USER\Software\Microsoft\MMC. If there’s a Restrict_Run value, delete it. Also check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\MMC for similar restrictions.

Be careful when editing the registry—create a restore point first.

Re-register Event Viewer Components

If the snap-in itself is broken, re-register its DLL files.

1. Open Command Prompt as administrator.
2. Run these commands one by one:

   regsvr32 /i msxml6.dll
   regsvr32 /i jscript.dll
   regsvr32 /i scrrun.dll

3. Restart your PC.

This re-registers components that Event Viewer relies on. It’s safe and doesn’t affect other programs.

Use PowerShell to View Events as a Workaround

If Event Viewer still won’t open, you can still read logs via PowerShell. This is a handy alternative while you troubleshoot.

• View recent errors: Get-EventLog -LogName System -EntryType Error -Newest 10 | Format-List
• View application logs: Get-WinEvent -LogName Application -MaxEvents 20 | Format-Table TimeCreated, Id, LevelDisplayName, Message
• Export logs to CSV: Get-WinEvent -LogName System | Export-Csv C:\temp\logs.csv

These commands give you the same data without the GUI.

Frequently Asked Questions

Why is Event Viewer blank or shows nothing?

A blank Event Viewer usually means the log files are empty or the service isn’t writing new events. Check if the Windows Event Log service is running, and try clearing the log to force a refresh. If logs are genuinely empty, your system may have been recently installed or the logs were cleared.

Can I delete all .evtx files?

Yes, you can delete all .evtx files in C:\Windows\System32\winevt\Logs. Windows will recreate them when the service restarts. You’ll lose old logs, but this often fixes corruption. Make sure to stop the service first.

Event Viewer won’t open at all—what’s the quickest fix?

The quickest fix is to restart the Windows Event Log service. If that doesn’t work, run sfc /scannow and then DISM. If it’s still broken, re-register the DLL files as described above.

Is there a portable alternative to Event Viewer?

Yes, you can use PowerShell or the wevtutil command-line tool. wevtutil qe Application /c:10 /rd:true /f:text shows the last 10 application events. These tools are built into Windows and don’t require installation.

Does resetting Windows fix Event Viewer?

Resetting Windows (via Settings > Update & Security > Recovery) will restore system files and likely fix Event Viewer. It keeps your personal files if you choose that option, but you’ll need to reinstall apps. Try the less drastic fixes first.

Related

• Alexa on Samsung Smart TV: Setup Guide
• How to Choose a VPN for Streaming Access
• Cross Browser Progress Bar: Step-by-Step Guide