New
#1
Is this a regular CU or this supposed to be an insider CU? From what I've gathered, it appears to be just a bad titling incident, but I'm not 100% on that.
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
Applies to: .NET Framework
Improvements and fixes
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 元.
- 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”
- 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.
- 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.
- Provides an AppContext flag for making the default value of TransparentNetworkIPResolution false in SqlClient connection strings.
- 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).
Known issues in this update
Microsoft is not currently aware of any issues with this update.
How to get this update
Install this update
To download and install this update, go to Settings > Update & Security > Windows Update and select Check for updates.
This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website.
Read more: https://support.microsoft.com/en-us/...2018-kb4469041
See also: .NET Framework December 5, 2018 Preview of Cumulative Update for Windows 10 version 1809 and Windows Server 2019 | .NET Blog
Direct download links for KB4469041 MSU file from Microsoft Update Catalog:
Download KB4469041 MSU for Preview of Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows 10 v1809 32-bit (x86) - 26.3 MB
Download KB4469041 MSU for Preview of Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows 10 v1809 64-bit (x64) - 49.5 MB
Download KB4469041 MSU for Preview of Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows Server 2019 64-bit (x64) - 49.5 MB
Is this a regular CU or this supposed to be an insider CU? From what I've gathered, it appears to be just a bad titling incident, but I'm not 100% on that.
I was not in The IP any longer but now the Hub shows me back in. It is the only place that shows me as an insider. How do I get out of this? Other users that were never in The IP are now in it. This is crazy. So what do we do?
Here's another source about this preview update.
.NET Framework December 5, 2018 Preview of Cumulative Update for Windows 10 version 1809 and Windows Server 2019 | .NET Blog