Tell me about the issue and I’ll help you find the solution you need.
Failover Cluster Management snap-in crashes after you install update 2750149 on a Windows Server 2012-based failover cluster
Content provided by Microsoft
Applies to: Windows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 EssentialsWindows Server 2012 FoundationWindows Server 2012 FoundationWindows Server 2012 StandardWindows Server 2012 StandardMore
Assume that you install update 2750149 on a Windows Server 2012-based failover cluster, and then you open the Failover Cluster Management snap-in. In this situation, the Failover Cluster Management snap-in crashes, and you receive the following error message:
A weak event was created and it lives on the wrong object, there is a very high chance this will fail, please review and make changes on your code to prevent the issue.
For more information about update 2750149, click the following article number to view the article in the Microsoft Knowledge Base:
2750149 An update is available for the .NET Framework 4.5 in Windows 8, Windows RT and Windows Server 2012
To resolve these issues, install the update on a Windows Server 2012-based cluster node or on a Windows 8-based computer that has the Remote Server Administration Tools for Windows 8 installed.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
To apply this update, you must be running Windows 8 or Windows Server 2012.
To apply this update, you do not have to make any changes to the registry.
You do not have to restart the computer after you apply this update.
Update replacement information
This update does not replace a previously released update.
The global version of this update installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 8 and Windows Server 2012 file information notes
The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
6.2.920 0.16 xxx
Windows 8 and Windows Server 2012
6.2.920 0.20 xxx
Windows 8 and Windows Server 2012
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8
For all supported x64-based versions of Windows 8 and of Windows Server 2012
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates