Article ID: 2600217 - View products that this article applies to.
Expand all | Collapse all

On This Page

Introduction

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.

RESOLUTION

Update information

The following files are available for download from the Microsoft Download Center:

Collapse this imageExpand this image
Download
Download the Reliability Update 2 for the Microsoft .NET Framework 4 package now.

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.

Prerequisites

To 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:
227091 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 requirement

After you apply this update, you must restart the computer if any affected files are locked or are being used.

Update replacement information

This update replaces the following hotfixes:
2628838 FIX: Memory leak when you use the FileSystemWatcher class in a .NET Framework 4.0-based application
2600088 A hotfix is available for the ASP.NET browser definition files in the Microsoft .NET Framework 4.0

Issues that this update resolves

This update resolves the following issues.

Click here to view or hide detailed information

Issue 1

Consider the following scenario:
  • You use Windows Internet Explorer 10 to access a Microsoft ASP.NET-based webpage.
  • The webpage starts a postback operation.
In this scenario, the postback operation fails, and you receive the following error message:
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 2

Consider the following scenario:
  • You create an ASP.NET-based webpage that has the MaintainScrollPositionOnPostBack attribute set to True.
  • You use Mozilla Firefox 4.0 or a later version of Mozilla Firefox to open the webpage.
  • The webpage starts a postback operation.
In this scenario, the scroll position of the webpage is not maintained after the postback operation is complete.

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 3

A 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 4

Consider the following scenario:
  • A user sets up an Internet Information Services (IIS) user-mode caching policy to cache the responses for requests that contain a certain file name extension in IIS Manager output caching.
  • A request for a resource with the previously-configured extension is received by IIS Manager output caching.
  • A custom module sets a cookie on the response. Then, the response is cached by IIS Manager output caching.
  • Another request from a different user is received by IIS Manager output caching, and the original cached response together with the cookie is sent out to the different user.
In this scenario, the response with the same cookie is sent out to different requestors unexpectedly.

Issue 5

Symptoms

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.

Cause

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 6

Consider the following scenario:
  • You install and then enable the PowerPivot for Excel add-in application on a computer that has the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) or the Microsoft .NET Framework 2.0 Service Pack 2 (SP2) installed.
  • You try to start Microsoft Excel 2010.
In this scenario, the splash screen intermittently stays open longer than usual when you receive the following message in Excel 2010:
Loading Add-ins (<x> of <y>) PowerPivot for Excel


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 7

The 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 information

The 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

Properties

Article ID: 2600217 - Last Review: June 11, 2012 - Revision: 4.0
APPLIES TO
  • Microsoft .NET Framework 4
Keywords: 
kbqfe kbfix atdownload kbsurveynew kbexpertiseadvanced kbcip KB2600217

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com