I have a Windows Server 2008 R2 Enterprise SP1 machine that I log into and use to manage virtual machines running on multiple Hyper-V servers on our domain. Sometimes, when I right-click on a local or remote VM, the Hyper-V Manager will crash and display the following error message:

Screenshot of Hyper-V Manager showing the error message "MMC has detected an error in a snap-in and will unload it."

If I use the Actions menu on the lower right, it works just fine, but for some reason right-clicking causes MMC to stop working. Is there any way to fix this issue? Here are the full details of the error message.

  Stopped working

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01: mmc.exe
  Problem Signature 02: 6.1.7600.16385
  Problem Signature 03: 4a5bc808
  Problem Signature 04: Microsoft.Virtualization.Client
  Problem Signature 05:
  Problem Signature 06: 4ce7c9e3
  Problem Signature 07: 342
  Problem Signature 08: 1f
  Problem Signature 09: System.OverflowException
  OS Version:   6.1.7601.
  Locale ID:    1033

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:

Also this stack trace:


Exception has been thrown by the target of an invocation.

  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.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at System.Windows.Forms.ListView.WndProc(Message& m)
   at Microsoft.Virtualization.Client.Controls.EnhancedListView.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

3 Answers 3


Looks to be an issue with HyperV snapin crashing when running on a second monitor

You aren't going to believe this. We figured out what it was finally and it was fairly complicated :)

We found a bug with the Hyper-V MMC snap in that is very repeatable. With Win2k8R2, hook up a machine to an external monitor (I was doing this on a laptop). Then, move the MMC (server manager in this case) the external monitor. Try to right-click on any VM in Hyper-V and it will crash. As soon as you move it back to the main monitor it works fine again.

Go figure!

I can confirm these results on my system, which has 2 GPUs with 4 monitors total (See below). If i use HyperV manager on the primary display or lower half of monitors 3 and 4 then everything works, but as soon as I move it above the vertical height of the primary display and try to right click it will crash. I have been working with Microsoft Support to resolve the issue (SR number 112110960192323 ) and will follow up if a hotfix or workaround is found.

enter image description here

  • 7
    – MDMarra
    Nov 13, 2012 at 18:06
  • 1
    WHAAAAAAAAAAAAAAAAAAAAAAAAAAAT? I.... this.... Even for MS this one is impressively bad. I suppose the workaround while you're waiting for a patch is Drag the HyperV manager so it's in the lower half of the virtual display area before you right click on things?
    – voretaq7
    Nov 13, 2012 at 18:08
  • 1
    Seems to be a somewhat common issue, where the position of the context menu is calculated using the the primary display's dimensions instead of the full dimensions from multiple displays. I have seen similar errors in Java applications, where the context menu is displayed on a different display or causes the application to crash. Just one of those end cases that doesn't get tested very often.
    – Greg Bray
    Nov 13, 2012 at 18:33
  • 3
    if (monitors.moreThanOne){explode()}
    – MDMarra
    Nov 13, 2012 at 18:44
  • 1
    Oh my various Gods! Outstanding find. Nov 13, 2012 at 19:19

It seems that a rogue Windows Update is responsible for this. You can uninstall it by running wusa.exe /uninstall /kb:2686831, the reboot, then reinstall the update via automatic update and reboot again. This fix is outlined in this TechNet forum post.

If that doesn't work, I'd try uninstalling RSAT and reinstalling it.

  • Tried it, still have the same issue :-( Also since this is a 2008 R2 Server I cannot remove RSAT without removing the HyperV role.
    – Greg Bray
    Nov 8, 2012 at 21:08
  • 1
    I just saw the note on your bounty that reads: Any help on how to prevent this crash or where to report it to Microsoft? - Assuming you have a support contract with Microsoft (which I hope you do if you virtualize with Hyper-V), you can open a ticket here. If you don't have a contract, there is a pay-per-incident option as well. I've had good luck opening tickets and not paying if it's an "unpublished but known" issue, but obviously YMMV there.
    – MDMarra
    Nov 9, 2012 at 16:02
  • We have support incidents through our MSDN accounts. I submitted a ticket and will see if it is a known issue or if they can create a hotfix. Thanks for you assistance!
    – Greg Bray
    Nov 9, 2012 at 17:49

A couple of basic suggestions/questions.

  • Updates? - You list out that it has SP1 but not whether you're current on everything else.
  • Hardware? - What are you running it on and do you have the latest drivers/firmware?
  • Is it production? - Is there anything running on the server in question?
  • Reinstall the role. - Have you tried that?
  • 1
    All current windows updates are installed, and this issue has occurred on multiple systems (HP Z400 workstation, Dell servers, IBM Servers). Not production environment, but has occurred on both dedicated and shared hardware. Seem intermittent, occurs repeatedly some days, then starts working without any noticeable changes.
    – Greg Bray
    Nov 2, 2012 at 22:01
  • sounds like a bad update, but I would first remove and install the role again; hopefully you do not have any local VM's on that machine
    – scape
    Nov 7, 2012 at 18:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .