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

  1.    #1

    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:Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	111.9 KB 
ID:	236949
    • then click on the left tree "Custom Views" and an mcc.exe crash will occur reporting a IO error reading "C:\ProgramData\Microsoft\Event Viewer\Views\View_0.xml"

    To roll-back you can from an admin prompt:
    del "C:\ProgramData\Microsoft\Event Viewer\Views\View_0.xml"
      My ComputerSystem Spec

  2. Posts : 192
    Windows 10 Pro, Version 1903

    Now listed as a known issue for ALL versions of Windows 7/8/10 after June updates:

    Event Viewer may close or you may receive an error when using Custom Views
    You may receive an error and the app may stop responding or close when trying to expand, view or create Custom Views in Event Viewer. You may also receive an error using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.

    Affected platforms:

    • Client: Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise LTSC 2015; Windows 8.1; Windows 7 SP1
    • Server: Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Next steps: We are working on a resolution and will provide an update in an upcoming release.
      My ComputerSystem Spec

  3. Posts : 192
    Windows 10 Pro, Version 1903

    Now shown as mitigated; a PowerShell script workaround is provided in KB4508640: Event Viewer may close or you may receive an error when using Custom Views
      My ComputerSystem Spec

  4.    #4

    I'm happy to have found this thread... thinking I tweaked something which broke Event Viewer, I rolled back my laptop 2 days, then six days... all without success. Then I ran across this thread... Good Grief Microsoft

      My ComputerSystem Spec

  5.    #5

    This is a very obvious bug which Microsoft's parlous software QA should have spotted
      My ComputersSystem Spec

  6.    #6

    Yep, 1903 (update 18362.207) seems to have fixed this.
      My ComputerSystem Spec

  7. Posts : 600
    Windows 7 Home Premium x64

    hexaae said: View Post
    Yep, 1903 (update 18362.207) seems to have fixed this.
    that would be the KB4501375 update for v1903 - released near the end of June 2019.

    Microsoft has patched the Event Viewer (MMC.exe) crashes 'System.IO.IOException' problem for almost all Win10 versions from 1607 to 1903 with the late June 2019 updates [I got either KB4501371 (build 17763.592) or KB4509479 (build 17763.593) for v1809 which fixes the event viewer custom views problem]. However, the problem persists and remains un-patched with LTSB 2015 (v1507) and the KB4503291 June update. Looks like the event viewer "fix" for ltsb 2015 will be included in the upcoming July 2019 security update.
      My ComputersSystem Spec


Related Threads
Hi all, The mentioned Event ID's only happened after a recent windows 10 update. The detailed list is: ID 3 - Kernel-EventTracing ( I did raise the log file to 40MB from 20MB, but seems to not solve this issue) ID 4 - Kernel-EventTracing...
Hi guys, well I need to ask... I just install fresh Windows 10 - its fully original and activated software. I have latest updates and drivers... but from time to time I have BSOD and - EVERYDAY DAY I have new, nasty errors in Event Viewer. ...
so...the last few days I've been dealing with skype crashing every few days, and when I check the event viewer logs, it flags on ntdll.dll. below is attached an image of the last instance of this occurring. 60151 I ran check disk, I ran...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:23.
Find Us