New
#11
I backed up the xml files so can put back if required, not going to worry over it.
I backed up the xml files so can put back if required, not going to worry over it.
@clam1952 - I copied the xml files into my downloads folder before deleting them, as the fix stated they should be "backed up". Can those copied xml files simply be copied back to the original folder after a fix is deployed? (Sorry I'm not as knowledgeable re tech stuff as others on this forum, and wasn't even sure copying them and saving them elsewhere was what was meant).
Hi cats, I followed the directions to a t on gHacks web page. Went to the folder, deleted all the views and restarted event viewer. It didn't work as all the pop ups reappeared. But I didn't give up and tried again at the directions given and lo and behold, the event viewer worked with no problems the second time. But I'm crossing my fingers. But great job at finding the link.
Thanks @clam1952. Interesting observation re your unaffected machine. I just checked the folder in my gigabyte computer (which is the only one of four that didn't have the problem) and there are no xml files in there either. The other three had some custom views relating to devices (cameras from memory - I never really looked at those views).
Good morning,
It seems that some of you have fixed the "MMC has detected an error in a snap-in" by using the link shared bycatspyjamas. I would like to give this fix a shot too but I want to make sure I really understand the proper steps.
It is my understanding that I go to C Drive > Microsoft > Event Viewer > Views. Right now in the 'Views' folder I have four entries. First is a folder called 'ApplicationViewsRootNode' which is empty. Then I have three of the XML view documents: View 0, View 1 and View 2.
I intend to copy the three views listed into a folder I will make and call it 'Event Viewer MMC fix' before I delete the same three views in the original folder.
Now for the heart of my question: Do I copy the 'ApplicationViewsRootNode' folder currently listed in the 'Views' folder and move it into my new folder with the copied three XML views and then delete it in the original folder like I did the three XML views or keep my hands off of it?
Sorry for such a detailed question but I don't want to screw up my computer.
Thanks and regards,
2harts4ever
There's still a problem with event viewer. I replaced my c drive with an image from June 3rd using MR. I ran event viewer and everything worked fine. See the attached image below.
As you can see there are 6 items listed under custom views. I'm assuming that these 6 views correspond to the 6 views listed under c:\programdata/microsoft/eventviewer/views. See below.
I re-downloaded Microsoft updates from Tuesday the 11th and ran event viewer. I get the same errors. Now if I delete this 6 views and rerun event viewer, I don't get the error messages, but I only get 1 custom view. That would be administrative events. The other five are gone. So, there still seems to be a problem with event viewer or Microsoft has decided to eliminate the 5 views in question. Any thoughts?
Howdy,
I finally took the plunge and followed the link that 'catspyjamas' shared earlier and now I am able to connect to event viewer and check out 'Administrative Events' under Custom Views.
Also, while searching for the MMC snap-in problem I discovered I have been getting ESENT Event ID 455 errors in my Event Viewer. After checking out what was causing this new entry in my Event Viewer every time I booted up I discovered I wasn't alone.
I did a little more searching and found this link which provides a quick and easy way to get rid of it. The fix is here: https://www.howto-connect.com/esent-event-id-455-error-message-in-windows-10-1903-fix/
If you are experiencing the same error you might want to check it out.
Meantime, I appreciate everyone's help in showing me how to get a working Event Viewer again.
Thanks and regards,
2harts4ever
Last edited by 2harts4ever; 14 Jun 2019 at 15:51.
Deleting the custom views as described in Brinkmann's article also worked for me. It's not necessary on Win10 PCs that get the relevant CUs if you haven't created any custom Event Viewer views, as I just verified on 3 other PCs (2 test machines, 1 road laptop).
--Ed--
KB4501375 fixed this for me.
I can see the custom views I had created once again.