[German]After installing the June 2019 cumulative updates KB4503293/KB4503327, Windows 10 users may notice that the Event Viewer no longer works when the Custom Views branch is selected. You will receive an error message. Here is a fix.
Affected are Windows 10, versions V1903 (Update KB4503293) and V1809 (Update KB4503293). If the Event Viewer is called and the Custom Views branch is selected, the display hangs. A dialog box appears with the message ‘An error was detected in a snap-in and the snap-in is removed’. Such an error usually indicates broken files. Mark Heitbrink gives the tip to empty the MMC cache in %appdata%\Microsoft\MMC. But that might not help in this case.
Furtunately the colleagues at German site deskmodder.de have described the error in more detail in this blog post. They gave the hint, that the message “The process cannot access the file ‘C:\ProgramData\Microsoft\Event Viewer\Views\View_0.xml’ because it is used by another process”. is displayed in this context. The solution proposed by colleagues is therefore quite simple. Navigate to the following folder in Explorer:
‘C:\ProgramData\Microsoft\Event Viewer\Views\
There you should find a file View_0.xml or with another consecutive number. This file must be deleted (requires administrator privileges). The MMC.exe will then recreate the View_x.xml at the next start if required and the display of the user-defined views should work again. Thanks to Matthias for the hint (and also to Max for the comment here).