KB2750149 breaks Windows 2012 Failover Cluster Manager


  • After installing KB2750149 on one of our cluster nodes the UI would no longer function properly in the following way:

    The Failover Cluster Manager will start, I can select Nodes and it will list the nodes, once I select a Node I get an very long exception message stating that "a weak event was created and it lives on the wrong object.....".  From there a dialog pops up that never goes away and I have to end the task.

    I uninstalled KB2750149 and the UI works fine as before.

    I have no idea if the update is revealing a problem in the Failover Cluster Manager or if the update is buggy, either way please fix this.  


    • Edited by Ginno2k9 Wednesday, January 9, 2013 8:55 PM
    Wednesday, January 9, 2013 8:05 PM


  • Thank you for the post, we are aware that the hotfix KB2750149 which was just released yesterday 1/8/2013 is negatively impacting the Failover Cluster Manager snap-in.

    We are actively investigating, and we will post more information as it becomes available.  The only known workaround at this time is to uninstall the hotfix.  We are recommending you do not deploy hotfix KB2750149 on Windows Server 2012 Failover Clusters until a solution is available.

    We apologize for the inconvenience, more information to come.

    Elden Christensen
    Principal Program Manager Lead
    Windows Server Clustering Group

    Thursday, January 10, 2013 12:01 AM
  • Just saw that KB2803748 showed up on my Server 2012 cluster nodes for installation

    Installed the update (no restart needed) and Cluster Manager no longer fails.

    Update for Windows Server 2012 (KB2803748)
    Installation date: ‎1/‎22/‎2013 1:31 PM
    Installation status: Succeeded
    Update type: Important
    Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.
    More information:

    Tuesday, January 22, 2013 6:39 PM
  • I can confirm KB2803748 has appeared on WSUS and fixes the issue. No reboot needed which is a bonus.


    Thursday, January 24, 2013 9:49 AM
  • I can confirm KB2803748 has appeared on WSUS and fixes the issue. No reboot needed which is a bonus

    Can confirm too. But no reboot is needed only if no users logged-on with Failover Clustering snap-in loaded.
    Thursday, January 24, 2013 10:00 AM

All replies