Download the package (x86 and x64) 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:
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 3146711 for the .NET Framework 4.5 and later versions||380035|
PrerequisitesTo apply this hotfix, you must have the .NET Framework 4.5.2, 4.5.1, or 4.5 installed.
Restart requirementYou 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 informationThis hotfix package doesn't replace a previously released hotfix package.
Issues that this hotfix rollup fixesASP.NET issue
Contention and bad performance on System.Web.BufferAllocator when you run a web application on computers that have more than 32 cores.
Fix: The contention has been eliminated by removing the global lock in System.Web.BufferAllocator.
Windows Forms issue
The Windows Forms PrintPreviewDialog UI is initialized very slowly when the following conditions are true:
- A network printer is used.
- User preferences on this printer, such as duplex settings, are modified.
In order to opt in to this optimization, the following key should be added to the app.config file, depending on the version of .NET Framework:
.NET Framework 4.5.2:
<?xml version="1.0" encoding="utf-8"?>.NET Framework 4.6 or a later version:
< appSettings >
< add key="OptimizePrintPreview" value="true" />
< /appSettings >
<?xml version="1.0" encoding="utf-8"?>If an application can run on either version of the .NET Framework, use both switches in the same file.
< AppContextSwitchOverrides value = "Switch.System.Drawing.Printing.OptimizePrintPreview=true" />
To opt out, remove the switch, or set the values to false.
ClickOnce has been updated to support TLS 1.1 and 1.2. ClickOnce will automatically detect which TLS protocol is required at runtime. There are no extra steps required in ClickOnce to enable this functionality.
Note ClickOnce continues to support TLS 1.0 for the foreseeable future, even though it is no longer considered PCI-compliant.
Article ID: 3146711 - Last Review: Apr 13, 2016 - Revision: 1