.NET Framework April 2017 Security and Quality Rollup



Update (2017/05/15): Added Windows 10 entries to KB table.

Update (2017/05/09): Known issue information added for the release.

Update (2017/04/20): Known issue information added for the release.

Today, we are releasing a new Security and Quality Rollup and Security Only Update for the .NET Framework. You can read the April 2017 Security Updates Release Notes to learn about all changes being released today.

Known issue with the release: “Privilege not held” error with PowerShell “stop-computer” command: Workaround after April 2017 security updates from CVE-2017-0160.


Microsoft Common Vulnerabilities and Exposures CVE17-0160

A remote code execution vulnerability exists when the Microsoft .NET Framework fails to properly validate input before loading libraries. An attacker who successfully exploited this vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. To exploit the vulnerability, an attacker would first need to access the local system with the ability to execute a malicious application. The security update addresses the vulnerability by correcting how .NET validates input on library load.

Note: You can also search for the security update at Security TechCenter. Search for “CVE” 17-0160.

Quality and Reliability

There are no quality and reliability changes this month.

Getting the Update

The Security and Quality Rollup is available via Windows Update, Windows Server Update Services and Microsoft Update Catalog. The Security Only Update is available via Windows Server Update Services and Microsoft Update Catalog. The Windows 10 updates are integrated with the Windows 10 Monthly Update, available via Windows Update.

Docker Images

The Windows ServerCoreIIS.NET Framework, and ASP.NET Docker images have been updated to include the Monthly Rollup. Pulling the latest image will update your local Docker image cache.

Downloading KBs from Microsoft Update Catalog

See the table below to learn about version applicability and more detailed release-specific information. See .NET Framework Monthly Rollups Explained for an explanation on how to use this table to download patches from Microsoft Update Catalog.

Product VersionSecurity and Quality Rollup KBSecurity Rollup KB
Windows 10 Creators UpdateCatalog 4015583N/A
.NET Framework 4.74015583
.NET Framework 3.54015583
Windows 10 Anniversary Update Windows Server 2016Catalog 4015217N/A
.NET Framework 4.6.24015217
.NET Framework 3.54015217
Windows 10 1511Catalog 4015219N/A
.NET Framework 4.6.14015219
.NET Framework 3.54015219
Windows 10 1507Catalog 4015221N/A
.NET Framework 4.64015221
.NET Framework 3.54015221
Windows 8.1 Windows Server 2012 R2Catalog 4014983Catalog 4014987
.NET Framework 4.6.240145464014550
.NET Framework 4.6, 4.6.140145514014556
.NET Framework 4.5.240145554014562
.NET Framework 3.540145674014574
Windows Server 2012Catalog 4014982Catalog 4014986
.NET Framework 4.6.240145454014549
.NET Framework 4.6, 4.6.140145484014560
.NET Framework 4.5.240145574014564
.NET Framework 3.540145634014572
Windows 7 Windows Server 2008 R2Catalog 4014981Catalog 4014985
.NET Framework 4.6.240145474014552
.NET Framework 4.6, 4.6.140145534014558
.NET Framework 4.5.240145594014566
.NET Framework 3.5.140145654014573
Windows Vista Windows Server 2008Catalog 4014984Catalog 4014988
.NET Framework 4.640145534014558
.NET Framework 4.5.240145594014566
.NET Framework 2.040145614014571

See .NET Framework Deployment tables for detailed deployment information on the release.

Known Issues

The April 2017 Monthly Update contained a bug that caused the PowerShell Stop-Computer command to stop correctly functioning. This bug has since been fixed. You can get the fix in the following ways:

Using Windows 10

Using an earlier version of Windows

  • Wait for the next .NET Framework monthly update, which will include this fix. This approach is recommended if you are not experiencing this problem.
  • Install the specific fix for this issue, listed below.
Windows Version.NET VersionKB Number
Windows 8.1 Windows Server 2012 R2.NET Framework 4.6.24020499
Windows 8.1 Windows Server 2012 R2.NET Framework 4.6 and 4.6.14020502
Windows 8.1 Windows Server 2012 R2.NET Framework 4.5.24020505
Windows 8.1 Windows Server 2012 R2.NET Framework 3.54020514
Windows Server 2012.NET Framework 4.6.24020498
Windows Server 2012.NET Framework 4.6 and 4.6.14020501
Windows Server 2012.NET Framework 4.5.24020506
Windows Server 2012.NET Framework 3.54020512
Windows 7 Windows Server 2008 R2.NET Framework 4.6.24020500
Windows 7 Windows Server 2008 R2.NET Framework 4.6 and 4.6.14020503
Windows 7 Windows Server 2008 R2.NET Framework 4.5.24020507
Windows 7 Windows Server 2008 R2.NET Framework 3.5.14020513
Windows Server 2008.NET Framework 4.64020503
Windows Server 2008.NET Framework 4.5.24020507
Windows Server 2008.NET Framework 2.0 Service Pack 24020511

Note that the .NET Framework 4.7 contains the fix. If you are using Windows 10 Creators Update, you will still need to install the May 2017 Update to get this fix.

Previous Monthly Rollups

The last couple .NET Framework Rollup updates are listed below for your convenience:

Note: Previously released security and quality updates are included in today’s release.

More Information

You can read the .NET Framework Monthly Rollups Explained to learn more about how the .NET Framework is updated.


Comments are closed. Login to edit/delete your existing comments