{"id":10575,"date":"2017-05-26T09:37:13","date_gmt":"2017-05-26T16:37:13","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/dotnet\/?p=10575"},"modified":"2021-09-30T10:10:14","modified_gmt":"2021-09-30T17:10:14","slug":"net-framework-may-2017-cumulative-quality-update-for-windows-10","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/net-framework-may-2017-cumulative-quality-update-for-windows-10\/","title":{"rendered":".NET Framework May 2017 Cumulative Quality Update for Windows 10"},"content":{"rendered":"

We just released a new Cumulative Quality Update for the .NET Framework. This update is specific to Windows 10 Creators Update.<\/p>\n

Previously released security and quality updates are included in this release.<\/p>\n

These quality updates will be made available to other .NET Framework and Windows version combinations in Q3 2017.\u00a0You can read the .NET Framework Monthly Rollups Explained<\/a> to learn more about how the .NET Framework is updated.<\/p>\n

<\/a>Security<\/h2>\n

This release contains the security improvements included in the NET Framework May 2017 Security and Quality Rollup<\/a>.<\/p>\n

<\/a>Quality and Reliability<\/h2>\n

The following improvements are included in this release.<\/p>\n

<\/a>Common Language Runtime<\/h3>\n

Issue 426799<\/strong><\/p>\n

Some applications using the managed C++ memcpy intrinsic could execute incorrectly. The JIT compiler when optimizing code that contains a C++ memcpy intrinsic could generate incorrect code.<\/p>\n

Issue 426795<\/strong><\/p>\n

Some applications terminate with an A\/V in clrjit.dll.The JIT compiler when optimizing a block of unreachable code could hit a A\/V which results in the unexpected early termination of the application.<\/p>\n

<\/a>Windows Presentation Framework<\/h3>\n

Issue 373366<\/strong><\/p>\n

If two WPF applications that target Side by Side (SxS) .NET versions (3.5 and 4.X) are loaded in the same process issues can occur on touch\/stylus enabled machines. A common example of this is loading VSTO add-ins written in WPF. This is due to an issue with choosing the correct PenIMC.dll version for each application. This fix allows WPF to properly differentiate between both DLLs and function correctly.<\/p>\n

<\/a>Getting the Update<\/h2>\n

The May 2017 Cumulative Quality Update is available via Windows Update, Windows Server Update Services and Microsoft Update Catalog.<\/p>\n

<\/a>Docker Images<\/h3>\n

The Windows ServerCore<\/a> and .NET Framework<\/a> images have not been updated for this release.<\/p>\n

<\/a>Downloading KBs from Microsoft Update Catalog<\/h3>\n

You can download patches from the table below. See .NET Framework Monthly Rollups Explained<\/a> for an explanation on how to use this table to download patches from Microsoft Update Catalog.<\/p>\n\n\n\n\n\n<\/tr>\n\n
Product Version<\/th>\nCumulative Quality Update KB<\/th>\n<\/tr>\n<\/thead>\n
Windows 10 Creators Update<\/strong><\/td>\nCatalog<\/a>\n4020102<\/a><\/strong><\/td>\n<\/tr>\n
.NET Framework 4.7<\/td>\n4020102<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/a>Previous Monthly Rollups<\/h3>\n

The last few .NET Framework Monthly Rollups are listed below for your convenience:<\/p>\n