Today, we are releasing the November 2017 Security and Quality Rollup.<\/p>\n
This release contains no new security updates. The most recent .NET security updates were shipped with the September 2017 Security and Quality Rollup<\/a>.<\/p>\n This release contains the following quality and reliability improvements.<\/p>\n Note: Additional information on these improvements is not available. The VSTS<\/a> bug number provided with each improvement is a unique ID that you can give Microsoft Customer Support<\/a>, include in StackOverflow comments<\/a>or use in web searches.<\/p>\n This guidance is for companies that want to install the minimum<\/strong> set of security updates each month. If you want security and quality updates, do not follow this guidance.<\/p>\n Guidance for this month:<\/p>\n Explanation: .NET Framework updates for Windows 10 are included with the Windows 10 LCU (which include Windows security updates), while pre-Windows 10 .NET Framework updates are separate updates (which only include quality updates this month).<\/p>\n Note: You can look at the Classification release attribute to see if a .NET Framework update falls under either \u201cSecurity Updates\u201d or \u201cUpdates\u201d category. See this month’s Windows 10 1709<\/a> and Windows 7<\/a> releases as examples.<\/p>\n The Security and Quality Rollup is available via Windows Update, Windows Server Update Services, Microsoft Update Catalog, and Docker.<\/p>\n You can get the update via the Microsoft Update Catalog. For Windows 10, .NET Framework updates are part of the Windows 10 Monthly Rollup.<\/p>\n<\/a>Quality and Reliability<\/h2>\n
<\/a>CLR<\/h4>\n
\n
<\/a>WPF<\/h4>\n
\n
<\/a>Security Compliance Guidance<\/h2>\n
\n
<\/a>Getting the Update<\/h2>\n
<\/a>Microsoft Update Catalog<\/h3>\n