View products that this article applies to. Summary. This December 13, 2016, Security and Quality Rollup for .NET Framework 4.6 for Windows Vista Service Pack 2 and Windows Server 2008 Service Pack 2, and .NET Framework 4.6 and 4.6.1 for Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1 includes cumulative .NET security updates and improvements in reliability in the .NET ...

The updates are now available for installation through WSUS. Update deployment information. For deployment details for this security update, go to the following article in the Microsoft Knowledge Base:

How to obtain and install the update Method 1: Windows Update. This update is available through Windows Update. When you turn on automatic updating, this update will be downloaded and installed automatically.

How to obtain and install the update Method 1: Windows Update. This update is available through Windows Update. When you turn on automatic updating, this update will be downloaded and installed automatically.

How to obtain and install the update. Before installing this update. Prerequisite: To apply this update, you must have .NET Framework 4.5.2 installed.

- Address crashes that could occur if ilasm.exe failed to establish temporary PDB file alongside the output file. 1 Windows Presentation Foundation (WPF) Additional information about this update. The following articles contain additional information about this update as it relates to individual product versions. 5020694 ...

How to obtain and install the update Method 1: Windows Update. This update is available through Windows Update. When you turn on automatic updating, this update will be downloaded and installed automatically.

1 Common Language Runtime (CLR). More information. The following articles provide information about supported .NET Framework versions for this Windows version. This includes the month and year of release, update replacement information, and help and support information for the update.

A vulnerability in certain .NET Framework APIs that parse URLs. An attacker who successfully exploits this vulnerability could use it to bypass security logic that's intended to make sure that a user-provided URL belonged to a specific host name or a subdomain of that host name.

The updates are now available for installation through WSUS. Update deployment information. For deployment details for this security update, go to the following article in the Microsoft Knowledge Base: