Introduction

This article describes hotfix rollup 2828841 that is available for the Microsoft .NET Framework 4.5. For more information about the issues that the hotfix resolves, see the "More information" section.

This hotfix rollup is available for the following operating systems:

Windows 7 Service Pack 1 (SP1)

Windows Server 2008 R2 SP1

Windows Server 2008 Service Pack 2 (SP2)

Windows Vista SP2

More information

Hotfix Information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this hotfix, you must have the .NET Framework 4.5 installed.

Restart requirement

You have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this hotfix.

Hotfix replacement information

This hotfix package does not replace a previously released hotfix package.

File information

The global 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.

Issues that this hotfix rollup resolves

Issue 1

Symptoms

On a touch device, if a window of a Windows Presentation Foundation (WPF) application is changed to a disabled state while at least one of your fingers is touching the window, the touch input freezes.

Note When this issue occurs, the application ignores any later touch input. This issue may occur when you touch a button to start a modal window, such as when you are using the Window.ShowDialog method. If you touch the button by using two fingers, one finger may still be touching the main window when it is disabled.

Resolution

This hotfix corrects the handling of touch input for disabled windows. This makes sure that touch input continues to be processed.

Issue 2

Symptoms

Consider the following scenario:

You are working on a .NET Framework 4.5-based workflow project in Microsoft Visual Studio 2012.

The workflow project satisfies the following conditions:

You have the System.Activities.Presentation.dll assembly in the project reference.

You have created at least one custom activity, and you have added at least two instances of a custom activity in a workflow.

You try to perform one of the following actions:

Right-click the workflow designer design surface.

Press F9 to set a breakpoint on an activity.

Search in files, and then double-click the search results to locate the corresponding activity.

In this scenario, an error dialog that contains the following information appears:

Issue 3

Symptoms

After you upgrade a server from the Microsoft .NET Framework 4 to the .NET Framework 4.5, some applications may throw Out-Of-Memory (OOM) errors. This issue is more likely to occur for applications that cache large data sets, such as applications that perform live video streaming.

Cause

This issue occurs because the .NET Framework 4.5 includes optimizations to the 64-bit version of the .NET Framework garbage collector that enable it to function more accurately in low-memory situations. This results in a change in garbage collection behavior that involves large data sets and potential OOM errors.

Resolution

After you apply the hotfix, the garbage collection optimizations are adjusted to account for large data sets.

Issue 4

Symptoms

Consider the following scenario:

You are using the .NET Framework 4.5 version of the System.Xml assembly.

You try to compile a very complex XSLT sheet.

You compile the XSLT sheet on a separate thread that contains a big stack that handles the complexity of compiling the XSLT sheet.

In this scenario, an XsltException exception occurs, and you receive the following error message:

The stylesheet is too complex.

Issue 5

Symptoms

When you call some methods of the System.Diagnostics.Eventing.Reader.EventRecord class in a .NET Framework 4.5-based application (for example, you call the FormatDescription() method), the application may return a NULL value.

Note This issue may occur only when an exact locale or region is not installed on your computer.

Cause

This issue occurs because of an incorrect language fallback behavior.

Issue 6

Symptoms

When you send many concurrent requests that have the same SessionId to an ASP.NET 4.5 web application, some requests may freeze at the RequestAcquireState stage unexpectedly.

Resolution

After you apply the hotfix, the hotfix makes sure that the EndRequest event will always trigger.

Issue 7

Symptoms

There is an ExternalDataExchange interface that uses multiple CorrelationParameterAttribute entries in order to match external events with multiple instances of the same workflow definition.

At least one of the parameters of the CorrelationParameterAttribute entries is a different type.

In this scenario, when a workflow instance is reloaded from persistence, an argumentException exception occurs. Additionally, you receive an error message that resembles the following:

Object must be of type <Type Name>

Notes:

The issue occurs in the 3.0, 3.5, 4.0, and 4.5 versions of Windows Workflow Foundation.

"Type Name" in the error message is one of the correlation parameter types.

Cause

The issue occurs because of a dependency on member reflection ordering by the workflow runtime.

Issue 8

Symptoms

You have a .NET Framework 4.5-based application that opens Windows Communication Foundation (WCF) ServiceHost instances and closes them asynchronously by using the ServiceHost.BeginClose() method. If a channel used by the ServiceHost instances cannot be closed within the configured time-out limit during peak load periods, the application may exit unexpectedly.

Resolution

After you apply the hotfix, the ServiceHost.BeginClose() method logic is changed to catch and handle all exceptions during an asynchronous close. If a TimeoutException exception occurs, the exception will now be traced, and the application will not exit.