Article ID: 2600217 - View products that this article applies to.
Reliability Update 2 for the Microsoft .NET Framework 4 is available to fix some stability, reliability, and performance issues in the .NET Framework 4.
This update includes the update packages that are listed in the "Update replacement information" section.
This update package also resolves some issues that were not documented in a previously released Microsoft Knowledge Base (KB) article. For more information about these issues, see the "Issues that this update resolves" section.
Update informationThe following files are available for download from the Microsoft Download Center:
Download the Reliability Update 2 for the Microsoft .NET Framework 4 package now.
Collapse this imageExpand this image
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft 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.
(https://support.microsoft.com/kb/119591/ )How to obtain Microsoft support files from online services
PrerequisitesTo apply this update, you must have the .NET Framework 4 or the Microsoft .NET Framework 4 Client Profile installed.
To install this update, you must have Windows Installer 3.1 or a later version installed. To obtain the latest version of Windows Installer, visit the following Microsoft website:
Download Windows Installer 4.5 redistributable
Command-line switches for this update
For more information about the various command-line switches that are supported by this update, visit the following Microsoft website:
(https://support.microsoft.com/kb/227091/EN-US/ )Command-Line Switches for the Microsoft Windows Installer Tool
For more information about Windows Installer, visit the following MSDN website:
General information about Windows Installer
Restart requirementAfter you apply this update, you must restart the computer if any affected files are locked or are being used.
Update replacement informationThis update replaces the following hotfixes:
(https://support.microsoft.com/kb/2628838/ )FIX: Memory leak when you use the FileSystemWatcher class in a .NET Framework 4.0-based application
(https://support.microsoft.com/kb/2600088/ )A hotfix is available for the ASP.NET browser definition files in the Microsoft .NET Framework 4.0
Issues that this update resolvesThis update resolves the following issues.
Click here to view or hide detailed information
Issue 1Consider the following scenario:
Script Error encountered", "'__doPostBack' is undefined
Note The webpage can start a postback operation in various ways. For example, the webpage can use a LinkButton control to start a postback operation.
Issue 2Consider the following scenario:
Note The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Issue 3A Watson error occurs in the System.Web.Configuration class in a .NET Framework 4-based ASP.NET website because of a race condition in which the InitStandaloneConfig function is called two times by two different threads. When this issue occurs, the website crashes. Additionally, you receive the following access violation error message after the Watson error occurs:
Exception Code - System.AccessViolationException
Issue 4Consider the following scenario:
When you use the FileSystemWatcher class in a .NET Framework 4-based application to watch for changes in a specified directory, a memory leak occurs.
This issue occurs because of an error in the FileSystemWatcher class. When a FileSystemWatcher object is created, the FileSystemWatcher class uses the GCHandle class to create a pinned garbage collector handle. The handle is 8 kilobytes (KB) and uses the byte data format. However, the FileSystemWatcher object never frees the garbage collector handle.
Issue 6Consider the following scenario:
Note<x> is a placeholder that represents where in the loading sequence that PowerPivot is displayed among the Excel add-in applications. <y> is a placeholder that represents the total number of add-in applications in Excel.
Issue 7The servicing of .NET Framework 4.0 assemblies may cause a race condition. This behavior causes processes that are running managed code against the .NET Framework 4.0 common language runtime (CLR) to enter an inconsistent state. Additionally, the processes may stop unexpectedly. After you install this update, entries are added to the CLR unification list to make the list transitively closed. This prevents any related race conditions.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Click here to view or hide detailed information
Article ID: 2600217 - Last Review: June 11, 2012 - Revision: 4.0