This March 2017 Preview of the Quality Rollup for Windows Server 2012 includes cumulative improvements in reliability in the .NET Framework 4.6 and 4.6.1. We recommend that you apply this quality rollup as part of your regular maintenance routines. Before you install this update, see the "Prerequisites" and "Restart requirement" sections.
- For SQL
Exceptions may be thrown in SqlClient during prelogin handshake processing or during MARS communication when a received TDS packet's size is smaller than expected. Prelogin handshake errors will manifest as an OverflowException, and MARS errors will manifest as a generic "Physical connection is not usable" SqlException.
- For WPF
A WPF application with a virtualizing list control (ListBox, DataGrid, TreeView, etc.) can encounter an ArgumentNullException when you scroll to an item whose size has substantially decreased since the last time it was re-virtualized.
- For ASP.NET
In the following scenarios, ASP.NET may duplicate the cookie in a response header:
- Before the request cookie is loaded, a response cookie is added.
- A response cookie is added, and then a native module sets a response cookie.
- For CLR
When you use RSACng (or another class which directly or indirectly uses RSACng) to perform encryption by using RSAEncryptionPadding.Pkcs1 when the private key is stored on a smartcard (or other hardware security module), you experience the following exception:
System.Security.Cryptography.CryptographicException: The parameter is incorrect at: System.Security.Cryptography.NCryptNative.DecryptData[T](SafeNCryptKeyHandle key, Byte data, T& paddingInfo, AsymmetricPaddingMode paddingMode, NCryptDecryptor`1 decryptor)
For Windows Server 2012
This update is available by manual download only.
To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
To apply this update, you must have the .NET Framework 4.6 or 4.6.1 installed.
You have to restart the computer after you apply this update if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this update.
This article applies to the following:
- Microsoft .NET Framework 4.6 and 4.6.1 when used with:
- Windows Server 2012
Article ID: 3216971 - Last Review: 4 Apr 2017 - Revision: 6