Failover Cluster Manager affected by KB2750149

I ran into a problem with a misbehaving Failover Cluster Manager (FCM) on a Windows Server 2012 cluster after allowing Cluster Aware Updating (CAU) to update the cluster. The following updates were gracefully installed, automatically placing the nodes in maintenance mode, installing the updates and moving on to the next node:


After the cluster had been updated it was no longer possible to view the roles (Hyper-V VM’s in this case) on the cluster. Instead the following screen popped up:


Because another unpatched cluster did not have this symptom, I decided to uninstall all updates that had been installed by CAU and after a reboot all is well.

After I reported this problem, I got a quick note from the Microsoft cluster team that KB2750149 was the cause of this problem and that the current advice is to uninstall this update until further notice.

It is important to note that this is only a problem of the Failover Cluster Manager (CluAdmin.msc) snap-in. The cluster and all its roles continue to run fine, which can be verified by opening a PowerShell screen on one of the affected cluster nodes and run Get-ClusterGroup. I was also able to run FCM successfully from another cluster or a management station with the Failover Clustering management tools.

One of my contacts at Da Vinci, @Jeroenix informed me that the problem had also been reported in the Windows Server 2012 forums and had received response from Elden Cristensen, Principal Program Manager Lead in the Windows Server Clustering Group. Kudos for the fast response!

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.


Because I was working on a new cluster I decided to install all current updates. In a production environment I advise you to take a 2 to 3 week delay which can be set easily in the self-updating schedule of Cluster Aware Updating on Windows Server 2012 clusters.


Additional info:

  • This issue only impacts manageability of the cluster, and does not affect functionality
  • This issue only impacts Windows Server 2012
  • This issue only impacts Failover Cluster Manager

Leave a Reply

Your email address will not be published. Required fields are marked *

Our Sponsors

Powered by