Windows 10: Upgraded to 1909 and the Event viewer still crashes

Unfortunately upgrading to version 1909 did not prevent the Event viewer from crashing. The administrative view survives with a few entries, but sorting by any column it crashes . . . . and always crashes when the log is large. So, to see any log entries, I clear all the logs and reboot. I would experiment with smaller log sizes but don''t know if it's possible to reduce their current max size limit.

:)

 

Event Viewer (MCC.exe) crashes 'System.IO.IOException'

I'm afraid this is another Windows 1903 bug (current ver 1836.175) as it is reproducible on every (?) PC.

• run Event Viewer
• click 'Create Custom View' on the right panel
• create for example a filter for System, events 6005, 6006, give it a name and save it:
  
  
• then click on the left tree "Custom Views" and an mcc.exe crash will occur *Confused reporting a IO error reading "C:\ProgramData\Microsoft\Event Viewer\Views\View_0.xml"

P.S.
To roll-back you can from an admin prompt:
Code:

 

Error in Event Viewer

Hi,



Thank you for writing to Microsoft Community Forums.



As you have mentioned, you have performed a repair installation on the computer and you see Event 508, 510 and 533 in Event Viewer.



I would like to inform that if you see any critical error in Event Viewer, please share the event logs with us to help you with the appropriate troubleshooting steps. Please follow the steps mentioned below to share the event logs:

1. Press Windows + X from the keyboard, select
   Event Viewer.
   
2. Expand Windows Logs from the left pane and select
   Applications.
   
3. Click Filter Current Log from extreme right pane. Then in the new windows check the box beside
   Error and click OK.
   
4. Now, look for a critical Error in the list and note down the message/information from the
   General Tab in the lower section.
   

Please reply with the status of the issue, we will be glad to help you further.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Explorer crashing

my only suggestion for the vagueish problem description would be to check the event viewer for something a little... more information if it happens to be there..
control panel | administrative tools | event viewer check them all for the time of the crash, and try to gather data if possible so that the problem well has a chance of being solved maybe..