December 5, 2018—KB4469041 Preview of cumulative update for .NET Framework 3.5 and 4.7.2 for Windows 10, version 1809 and Windows Server 2019

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Addresses an issue in which the System.Security.Cryptography.Algorithms reference was not correctly loaded on .NET Framework 4.7.1 after the July 10, 2018 and August 14, 2018 patches.
• Addresses a crash due to TaskCanceledException that can occur during shutdown of some WPF apps. Apps that continue to do work involving weak events or data binding after Application.Run() returns are known to be vulnerable to this crash.
• Addresses a race condition in temporary files and some antivirus scanners that causes .NET Framework applications to stop working. The error message is, "The process cannot access the file <name of temp file>".
• Updates support for the formatting of Japanese dates for the first year in the eras. When the format pattern is “y?”, the year format will use the symbol "?" and not use year number 1. Additionally, we will support dates that include the "?" symbol.
• Updates Venezuela currency information. This will affect the culture of “es-VE” as follows:
  • Currency symbol is changed to “Bs.S”
  • English currency name is changed to “Bolívar Soberano”
  • Native currency name is changed to “bolívar soberano”
  • International currency code is changed to “VES”
• Addresses an issue in KB4096417 in which we switched to CLR-implemented write-watch for pages. The GC no longer calls VirtualAlloc when it runs under workstation GC mode.
• Addresses a System.AccessViolationException that is caused by accessing disposed X509Certificate2 instance in a rare race condition to defer the service certificate cleanup to GC. The affected scenario is WCF NetTcp bindings that use reliable sessions with certificate authentication. 
• Provides an AppContext flag for making the default value of TransparentNetworkIPResolution false in SqlClient connection strings. 
• Addresses an issue in some .NET remoting scenarios when using TransactionScopeAsyncFlowOption.Enabled. In this scenario, it was possible to have Transaction.Current reset to null after a remoting call. This occurred when the remoting call did not leave the caller’s AppDomain (with 4.7.2).

Microsoft is not currently aware of any issues with this update.