Hotfix rollup 3095338 for the .NET Framework 4.6 RC on Windows

Prerequisites

To apply this hotfix, you must have the .NET Framework 4.6 RC 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 doesn't replace a previously released hotfix package.

Issues that this hotfix rollup fixes

Issue 1

Assume that you use a Windows Presentation Foundation (WPF) application. A WPF TreeView can spontaneously scroll to an unpredictable position after you add a new item. This issue occurs when the following conditions are true:

• The new item is the last of its parent's children.
• The parent item is the last of its parent's children.
• The new item is visible at the current scroll position.

Issue 2

In a WPF application, removing an editing control from the visual tree can leak an ImmComposition object. Doing this repeatedly can eventually cause an out-of-memory exception.

Note An "editing control" is any control that creates and uses a TextEditor object. The main examples are TextBox, RichTextBox, and FlowDocumentScrollViewer.

Issue 3

A WPF application can become deadlocked when the following conditions are true: ​

• The application raises an event whose delivery is routed through the weak-event system.
• Another thread is concurrently using the weak-event system. This causes the first thread to wait for a lock.
• When it waits, the thread's message pump receives a message that causes re-entrancy into the application's code.
• The re-entered code tries to use the weak-event system.

This is observed most frequently with the PropertyChanged event of INotifyPropertyChanged, where the re-entered code also tries to raise a PropertyChanged event.

This is fixed in the weak-event system by waiting for locks in a way that doesn't run the thread's message pump.

Issue 4

When you try to run a command on the server, it times out on the client side, but finishes on the server. In this situation, the client sends an attention packet to the server and sets itself into a timed-out state. However, it doesn't reset it as soon as it recovers from the timed-out state after the server processed the statement that the client timed out on.

This hotfix resets the state of the client when it recovers from the timed-out state.

Issue 5

In some circumstances, some files in the ASP.NET shadow cache can become corrupted during computer shutdown. This may cause unpredictable behavior or exceptions being raised by applications that use the cache.

This update fixes many issues in the RyuJIT compiler. If the application still behaves unpredictably after the installation of this update, see additional detailed troubleshooting guidance.

Additional steps:

If it's determined that RyuJIT may be involved in your issue by following the troubleshooting steps at the link, please log the issue at http://connect.microsoft.com. Include as much detail as possible in the report, and also code to reproduce the issue.

Issue 6

DxO OpticsPro 10 may crash when you navigate rapidly through the TreeView control in Windows 10 that has the .Net Framework 4.6 installed. This hotfix fixes conditions that may cause the crash.