-Advertisement-
HomeMicrosoftMicrosoft KB4576945 cumulative update preview for .NET Framework 3.5 and 4.8

Microsoft KB4576945 cumulative update preview for .NET Framework 3.5 and 4.8

For Windows 10, version 2004 and Windows Server, version 2004

Release Date:
October 1, 2020

Version:
.NET Framework 3.5 and 4.8

The October 1, 2020 update for Windows 10, version 2004 and Windows Server, version 2004 includes cumulative reliability improvements in .NET Framework 3.5 and 4.8. We recommend that you apply this update as part of your regular maintenance routines. Before you install this update, see the Prerequisites and Restart requirement sections.

Quality and reliability improvements


WCF1– Addressed an issue with WCF services sometimes failing to start when starting multiple services concurrently.
Winforms– Addressed a regression introduced in .NET Framework 4.8, where Control.AccessibleName, Control.AccessibleRole, and Control.AccessibleDescription properties stopped working for the following controls:Label, GroupBox, ToolStrip, ToolStripItems, StatusStrip, StatusStripItems, PropertyGrid, ProgressBar, ComboBox, MenuStrip, MenuItems, DataGridView. – Addressed a regression in accessible name for combo box items for data bound combo boxes. .NET Framework 4.8 started using type name instead of the value of the DisplayMember property as an accessible name, this improvement uses the DisplayMember again.
ASP.NET– Disabled resuse of AppPathModifier in ASP.Net control output. – HttpCookie objects in the ASP.Net request context will be created with configured defaults for cookie flags instead of .NET-style primitive defaults to match the behavior of `new HttpCookie(name)`.
SQL– Addressed a failure that sometimes occured when a user connects to one Azure SQL database, performed an enclave based operation, and then connected to another database under the same server that has the same Attestation URL and performed an enclave operation on the second server.
CLR2– Added a CLR config variable Thread_AssignCpuGroups (1 by default) that can be set to 0 to disable automatic CPU group assignment done by the CLR for new threads created by Thread.Start() and thread pool threads, such that an app may do its own thread-spreading. – Addressed a rare data corruption that can occur when using new API’s such as Unsafe.ByteOffset<T> which are often used with the new Span types. The corruption could occur when a GC operation is performed while a thread is calling Unsafe.ByteOffset<T> from inside of a loop. – Addressed an issue regarding timers with very long due times ticking down much sooner than expected when the AppContext switch “Switch.System.Threading.UseNetCoreTimer” is enabled.
Charles Leverehttps://www.riverbankwebdesign.ca/
Charles Levere is the editor-in-chief (dork-in-chief) of Urban Dork. When he is not writing or tinkering with hardware, he is most likely playing one of his favorite video games. He also loves being near the water, kayaking, water skiing, or anything that gets him on the water and in the sun.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

- Advertisment -
- Advertisment -

Recent Comments