MMC detects error in a snap-in

Howdy,

I am running a HP All-in-One 23-g017c, Windows 10 Home 64-bit Operating system.

A few hours ago I was trying to open my Event Viewer to check on something and discovered the following problem. I clicked on my Component Services like I always do. I then clicked on Event Viewer and then clicked on Custom Views and that is when I got the following message:

"MMC has detected an error in a snap-in and will unload it"

Any ideas or thoughts?

Thanks and regards,
2harts4ever

Ever since the Tuesday updates, my event viewer is displaying the same. The event viewer loads, but when you click on one of the errors, that's when all the errors pop up. I've attached three.




Not sure, but it seems to have something to do with the updating of framework .NET 4.8.

Not sure why but I had the same snap-in error

I copied the Unhandled Exception text

Code:

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.get_IsReadOnlyView()
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.UpdateReadOnly()
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.InitializeQueryNode(FileInfo fileInfo)
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.AddSubNodes(DirectoryInfo dir, EventNodeType nodeType, Boolean userQuery, String standardViewConfig)
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.AddSavedQueryNodes()
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.CreateChildNodes()
   at Microsoft.EventViewer.SnapIn.MMCEventsNode.ExpandNode()
   at Microsoft.EventViewer.SnapIn.MMCEventsNode.OnExpand(AsyncStatus status)
   at Microsoft.ManagementConsole.NodeSyncManager.ProcessRequest(NodeRequestInfo info, IRequestStatus requestStatus)
   at Microsoft.ManagementConsole.SnapIn.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
   at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
   at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

Maybe 'Event Viewer' is tired and wants to take a break. After all, the feature update 1809 had a lot of bugs.

RichardC said:

Ever since the Tuesday updates, my event viewer is displaying the same. The event viewer loads, but when you click on one of the errors, that's when all the errors pop up. I've attached three.




Not sure, but it seems to have something to do with the updating of framework .NET 4.8.

Looks like you are correct from Windows logs Application which is still working.
.
.NET Runtime event ID 1026

Code:

Application: mmc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.get_IsReadOnlyView()
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.UpdateReadOnly()
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.InitializeQueryNode(FileInfo fileInfo)
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.AddSubNodes(DirectoryInfo dir, EventNodeType nodeType, Boolean userQuery, String standardViewConfig)
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.AddSavedQueryNodes()
   at Microsoft.Windows.ManagementUI.CombinedControls.EventsNode.CreateChildNodes()
   at Microsoft.EventViewer.SnapIn.MMCEventsNode.ExpandNode()
   at Microsoft.EventViewer.SnapIn.ViewerRootNode.GetViewsRootNode()
   at Microsoft.EventViewer.SnapIn.EventViewerHomepage.FindNodeWithSameQueryOrCreate(QueryConfig qryConfig)
   at Microsoft.EventViewer.SnapIn.EventViewerHomepage.OnEventsSummaryListViewAction(EventSummaryListViewTag tag)
   at Microsoft.EventViewer.SnapIn.MMCRootNode.RootNodeNotification(Object sender, NotifyRootNodeEventArgs args)
   at Microsoft.Windows.ManagementUI.CombinedControls.EventHomeControl.FireNotifyRootNodeEvent(Object sender, NotifyRootNodeEventArgs args)
   at System.Windows.Forms.Control.OnDoubleClick(EventArgs e)
   at System.Windows.Forms.ListView.WndProc(Message& m)
   at Microsoft.Windows.ManagementUI.CombinedControls.ListViewEx.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Exception Info: System.Reflection.TargetInvocationException
   at Microsoft.ManagementConsole.Internal.SnapInMessagePumpProxy.OnThreadException(Object sender, ThreadExceptionEventArgs e)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Microsoft.ManagementConsole.Internal.SnapInMessagePumpProxy.Microsoft.ManagementConsole.Internal.ISnapInMessagePumpProxy.Run()
   at Microsoft.ManagementConsole.Internal.ISnapInMessagePumpProxy.Run()
   at Microsoft.ManagementConsole.Executive.SnapInThread.OnThreadStart()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

Hi Richard C and all,

That is exactly what I am seeing. Hopefully a fix will be coming soon because I do like to be able to use Event Viewer.

Regards,
2harts4ever

Custom Views in Event Viewer was borked on my 3 HP laptops after yesterday Windows Updates (in spite of quite a few restarts), however it was fine on my Gigabyte laptop. I saw this issue raised somewhere else on tenforums with a link to a fix on ghacks. This fix worked for me (and has remained working in spite of shut downs and restarts). It's apparently happening to both 1809 and 1903 versions of Windows 10 after yesterdays patches.

Here ya go: Windows 10: Event Viewer error after installing KB4503293 and KB4503327 - gHacks Tech News

I used MR and restored C:\ from an earlier image prior to the Tuesday downloads. Event Viewer worked fine but man was there a lot of errors all over the place.

That works! If it's a Martin Brinkman fix that's good enough for me. Curiously not getting the problem on my slow ring insider which is also on 1903 18362.175.

My only worry now is what will happen with Event Viewer when MS fixes it. No idea what effect a MS patch to fix this will have after performing the workaround on ghacks.

EDIT I notice a new comment on the thread on ghacks that someone uninstalled /reinstalled the relevent windows update and it fixed it. Perhaps the original updates that were breaking event viewer on some systems were replaced with a fixed version?