This article describes hotfix rollup 3154528 for the Microsoft .NET Framework 4.6 and 4.6.1. For more information about the issues that the hotfix rollup fixes, see the "Issues that this hotfix rollup fixes" section.
Resolution
The hotfix that corresponds to KB3154528 has been superseded with the latest updates of .NET Framework, which contain all fixes that were previously included in KB3154528. It is recommended to install the latest updates of .NET Framework.
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 3154528 for the .NET Framework 4.6 and later versions |
394297 |
For more information about how to determine the .NET Framework versions, see How to: Determine which .NET Framework versions are installed.
More Information
Prerequisites
To apply this hotfix, you must have the .NET Framework 4.6 or 4.6.1 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
CLR issue
When you run the ngen install command by using a symbolic link to an assembly, NGen saves incorrect book-keeping data for the resulting native image. This makes the native image unusable.
System.Transations issue
When you use the SubordinateTransaction class in your application, the transaction may abort when promotion was attempted.
Windows Presentation Foundation issues
-
When you use a virtualizing list control (ListBox, DataGrid, ListView and so on) in your Windows Presentation Foundation (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
-
When you use a list control (ListBox, DataGrid, ListView and so on) in your WPF application, you may see an increase in the number of items fetched from the underlying collection, compared to previous version of the .NET Framework. This issue occurs when the items do not all have the same height when they are displayed. When the collection is large, this can appear to freeze the application, while WPF iterates through the entire collection.
This issue is now corrected in the case where there is no grouping or hierarchy and the control is item-scrolling (ScrollUnit="Item").
