This article describes hotfix rollup 3154521 for the Microsoft .NET Framework 4.5.2 and 4.5.1. For more information about the issues that the hotfix rollup fixes, see the "Issues that this hotfix rollup fixes" section.
The following files are available for download from the Microsoft Download Center:
Download the x86 package now.
Download the x64 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.
Note To verify the hotfix update version, check the value of the Release keyword to determine the installed version. To be forward-compatible, you can check for a value that's greater than or equal to the value that's listed in the following table.
Hotfix rollup version
Value of the Release DWORD
Hotfix rollup 3154521 for the .NET Framework 4.5 and later versions
For more information about how to determine the .NET Framework versions, see How to: Determine Which .NET Framework Versions Are Installed.
To apply this hotfix, you must have the .NET Framework 4.5.2, or 4.5.1 installed.
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
Windows Presentation Foundation issues
Issue 1: When you use a virtualizing list control (ListBox, DataGrid, ListView and so on) in your WPF application, you may encounter an ArgumentException exception. And you receive the following error message when you add a new item to the underlying collection.
Height must be non-negative
Issue 2: WPF applications that perform work on the UI thread in response to touch move events may experience poor performance and delayed interaction with the UI. This was caused by a flood of move messages being posted to the WPF internal stylus queue.
To fix this, moves are now appropriately coalesced when the UI thread is unable to process them immediately. This throttles the number of touch move events and provides a more responsive UI interaction. These coalesced points can be obtained through calling TouchEventArgs.GetIntermediateTouchPoints as needed.