Last Updated 9/7/2018: Documented missing WPF updates

Today, we are releasing the August 2018 Preview of Quality Rollup.

Quality and Reliability

This release contains the following quality and reliability improvements.

ASP.NET

• Resolves an issue where an ASP.NET web application is continuously running under high load on high-end web server(40+ CPU cores), it may suffer high thread contention which can cause high CPU usage. [624745]

CLR

• Fixes an issue that results in a System.InvalidProgramException for some very large XSLT transforms. This may also fix this kind of issue for some other very large methods. [604943]
• Addresses an issue where a the CultureAwareComparer type was not able to correctly serialize and deserialize across different versions of the .NET Framework, as described in Advisory serializing/deserializing a CultureAwareComparer with .NET Framework 4.6+. [637591]

SQL

• Resolves an issue where SqlClient login may use an infinite timeout due to truncating a small millisecond timeout to zero when converting to seconds. [631196]

WCF

• A race-condition existed in AsyncResult that closes a WaitHandle before Set() is called. When this happens, the process crashes with an ObjectDisposedException. [590542]
• Enable customers using .NET 2.0, 3.0, 3.5, 3.5.1 to use their program under TLS 1.1 or TLS 1.2 [639940]

WPF

• In multi-threaded WPF applications that process large packages simultaneously, there is potential for a deadlock when one of these files is closing and the other starts to consume larger amounts of memory.[602405]
• Under certain conditions, WPF applications (like SCCM) using WindowChromeWorker experience high CPU usage or hangs. [621651]
• In certain .NET applications, timing issues in the finalizer thread could potentially cause exceptions during AppDomain or process shutdown. This is generally seen in applications that do not correctly shut down Dispatchers running on worker threads prior to process or AppDomain shutdown. Such applications should take care to properly manage the lifetime of Dispatchers. This change adds an AppContext switch that can help alleviate (but not eliminate) some of the issues that may arise from these application design issues. To enable this, set the AppContext flag “Switch.MS.Internal.DoNotInvokeInWeakEventTableShutdownListener=true”. [609469]
• ComboBox grouped items now report children correctly via UIAutomation. [504282]
• Replaced multiple characters with a single character from IMEPad input now succeeds. [515186]

Note: Additional information on these improvements is not available. The VSTS bug number provided with each improvement is a unique ID that you can give Microsoft Customer Support, include in StackOverflow comments or use in web searches.

Getting the Update

The Preview of Quality Rollup is available via Windows Update, Windows Server Update Services, Microsoft Update Catalog, and Docker.

Microsoft Update Catalog

You can get the update via the Microsoft Update Catalog. For Windows 10, .NET Framework updates are part of the Windows 10 Monthly Rollup.

The following table is for Windows 10 and Windows Server 2016+.

The following table is for earlier Windows and Windows Server versions.

Previous Monthly Rollups

The last few .NET Framework Monthly updates are listed below for your convenience:

• August 2018 Security and Quality Rollup
• July 2018 Update
• June 2018 Security and Quality Rollup
• May 2018 Security and Quality Rollup