.NET Framework December 5, 2018 Cumulative Update for Windows 10 version 1809 and Windows Server 2019
Today, we are releasing the December 5, 2018 .NET Framework Cumulative Update for Windows 10 version 1809 and Windows Server 2019.
For more information about the new Cumulative Updates for .NET Framework for Windows 10 version 1809 and Windows Server 2019 please refer to this recent announcement.
This release contains the following quality and reliability improvements.
- Addressed a situation where the System.Security.Cryptography.Algorithms reference was not correctly loaded on .NET Framework 4.7.1 after the 7B/8B patch. 
- Updated Japanese dates that are formatted for the first year in an era and for which the format pattern uses “y年”. The format of the year together with the symbol “元” is supported instead of using year number 1. Also, formatting day numbers that include “元” is supported. 
- Updated Venezuela currency information, this change affected the culture of “es-VE” in the following ways.  1) currency symbol changed to “Bs.S” 2) English currency name is changed to “Bolívar Soberano” 3) Native Currency name is changed to “bolívar soberano” 4) Intl Currency Code changed to “VES”
- Addressed an issue with KB4096417 where we switched to CLR-implemented write-watch for pages. The GC will no longer call VirtualAlloc when running under workstation GC mode. 
- Provides an AppContext flag for making the default value of TransparentNetworkIPResolution false in SqlClient connection strings. 
Addressed a System.AccessViolationException due to accessing disposed X509Certificate2 instance in a rare race condition to defer the service certificate cleanup to GC. The impacted scenario is WCF NetTcp bindings using reliable sessions with certificate authentication. 
- Addressed 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. 
- Addressed a race condition involving temporary files and some anti-virus scanners. This was causing crashes with the message “The process cannot access the file “. 
- Addressed an issue on some .NET Remoting scenarios, when using TransactionScopeAsyncFlowOption.Enabled, 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). 
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.
The Preview of Quality Rollup is available via Windows Update, Windows Server Update Services, and Microsoft Update Catalog.
You can get the update via the Microsoft Update Catalog. For Windows 10 version 1809 and Windows Server 2019, .NET Framework updates are independent of the Windows 10 Monthly Rollup.
|Product Version||Preview of Cumulative Update KB|
|Windows 10 1809 (October 2018 Update)||Catalog 4469041|
|.NET Framework 3.5, 4.7.2||4469041|