KB4562899 Cumulative Update .NET Framework 3.5, 4.8 Windows 10 July 31 Win Update

Page 1 of 2 12 LastLast
    KB4562899 Cumulative Update .NET Framework 3.5, 4.8 Windows 10 July 31

    KB4562899 Cumulative Update .NET Framework 3.5, 4.8 Windows 10 July 31

    Preview update for Windows 10 version 2004
    Category: Win Update
    Last Updated: 31 Jul 2020 at 15:59

    July 31, 2020 - KB4562899 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 2004


    The July 31, 2020 update for Windows 10 Version 2004 includes cumulative reliability improvements in .NET 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

    CLR1 - A change in .NET Framework 4.8 regressed certain EnterpriseServices scenarios where an single-thread apartment object may be treated as an multi-thread apartment and lead to a blocking failure. This change now correctly identifies single-thread apartment objects as such and avoids this failure.
    - Addresses an issue in assemblies with IBC profile data causing Ngen worker processes to crash and fall back to full native images.
    - Addresses rare crashes that could occur during thread abort delivery.
    SQL - SqlBulkCopy.WriteToServer can cause transactions to in-memory SQL tables, to fail. The client may see an exception with message "Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding." SqlBulkCopy.WriteToServer was sending an Attention token (cancellation message) after sending data to Sql Server, causing the server to abort the transaction for in-memory tables.
    ASP.NET - Use FIPS-compliant hashes in ASP.Net telemetry data.
    - Addresses an issue where "Unspecified" was not an allowed value in config for the 'cookieSameSite' attribute of the forms authentication and session state configuration sections.
    WPF2 - Addresses an issue when spell-checking is enabled in WPF TextBox or RichTextBox, words like “etc.”, “e.g.” are identified as spelling errors incorrectly.
    - Addresses an issue when some Per-Monitor Aware WPF applications that run on .NET 4.8 may occasionally encounter a crash with exceptionSystem.ComponentModel.Win32Exception.
    - Addresses an issue where TextBlock reflows (makes different line-breaking decisions) during render and hit-test, vs. during measure. The symptoms include missing text, and FailFast crashes during programmatic text processing.
    - Addresses an issue with a render thread failure caused by HostVisual disconnecting its target on the wrong thread.
    - Addresses an issue with a hang while scrolling a TreeView whose tree is non-uniform, in the sense thata given node's children govern subtrees whose sizes are quite different.
    - Addresses an issue with a crash that can occur when closing a tooltip that is re-entrantly closed by user code.
    - When an HwndHost leaves the visual tree, a stack trace is created. This is expensive, and usually unnecessary. The logic is now changed to create the stack trace only when the anomalous condition occurs.
    - Addresses a memory leak in System.Speech.SpeechSynthesizer.
    - DataGrid's Copy command throws an exception if the system clipboard is locked by another process. This crashes, as there is usually no app code on the stack to catch the exception. The behavior of TextBox (and other apps like Notepad, Word, browsers) in this situation is to fail silently - nothing is copied to the clipboard, but no exception. A WPF app can now opt-in to this behavior by setting <appSettings> <add key="ShouldThrowOnDataGridCopyOrCutFailure" value="false"/> </appSettings>in its app.config file.
    - Addresses an issue in constructing the internal model for a FixedPage document. Some text was appearing in the wrong order for the purposes of editing operations such as selection and copy/paste.
    WCF3 - When using a UPN Windows username with the format similar to username@dns.domain in the username property of a NetworkCredential when using NetTcpBinding or NetNamedPipeBinding, WCF would incorrectly split the username and dns.domain placing them into the UserName and Domain properties. This is invalid in some scenarios and would result in failing to authenticate. This fix removes the credential modification when using a UPN username. The modification can be re-enabled by setting the AppSetting "wcf:enableLegacyUpnUsernameFix" to true.
    Net Libraries - Addresses a memory leak in HttpListener.
    Winforms - Addresses an issue with DataGridView IsReadOnlyaccessibility state: Narrator and other accessible tool announces read-only cell status accordingly.
    - Addresses a regression in .NET Framework 4.8 when applications using the DataGridView ComboBox cell type and have opted into Level 3 Accessibility, may experience intermittent crashes while editing the cell.
    - Addresses an issue in ClickOnce RFC3161 timestamp verification code.
    Winforms Accessibility Improvements In this release we are adding new accessibility improvements that your application can opt-in into. By default these changes are disabled. Applications that opt-in into accessibility features introduced in .NET 4.8 and earlier, can add the following compatibility switch to the application's config file:
    "Switch.UseLegacyAccessibilityFeatures.4=false"
    Specifically, if an application targets .NET 4.8, add the following AppContextSwitchOverrides section:
    <?xml version="1.0" encoding+"utf-8" ?>
    <configuration>
    <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Versionv4.8"/>
    </startup>
    <runtime>
    <!-- AppContextSwitchOverrides value attribute is in the form of key1=true|false;key2=true|false -->
    <AppContextSwitchOverrides value="Switch.UseLegacyAccessibilityFeatures.4=false" />
    </runtime>
    </configuration>
    If an application targets an earlier version of the framework and opts in into the previously release sets of accessibility features, then add a single "Switch.UseLegacyAccessibilityFeatures.4=false" switch to the existing AppContextSwitchOverrides section:
    <?xml version="1.0" encoding+"utf-8" ?>
    <configuration>
    <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Versionv4.7"/>
    </startup>
    <runtime>
    <!-- AppContextSwitchOverrides value attribute is in the form of key1=true|false;key2=true|false -->
    <AppContextSwitchOverrides value="Switch.UseLegacyAccessibilityFeatures=false|Switch.UseLegacyAccessibilityFeatures.2=false|Swi tch.UseLegacyAccessibilityFeatures.3=false|Switch.UseLegacyAccessibilityFeatures.4=false"/>
    </runtime>
    </configuration>
    Winforms accessibility improvements included in this release are:
    - Addresses an issue with announcing PropertyGrid control items and categories expanded/collapsed state by Screen Readers.
    - Updated the accessible patterns of Property Grid control and its inner elements.
    - Updated the accessible names of Property Grid control inner elements to correctly announce these by screen reader.
    - Addresses bounding rectangle accessible properties for the PropertyGridView controls
    - Enables screen readers to announce DataGridView ComboBox cell expanded/collapsed state correctly.

    1 Common Language Runtime (CLR)
    2 Windows Presentation Foundation (WPF)
    3 Windows Communication Foundation


    How to obtain and install the update

    Install this update

    Release Channel Available Next Step
    Windows Update and Microsoft Update Yes To download and install this update, go to Settings > Update & Security > Windows Update, and then select Check for updates.
    Microsoft Update Catalog Yes To get the standalone package for this update, go to the Microsoft Update Catalog website.
    Windows Server Update Services (WSUS) No You can import this update into WSUS manually. See the Microsoft Update Catalog for instructions.

    File information

    For a list of the files that are provided in this update, download the file information for cumulative update .

    Prerequisites

    To apply this update, you must have .NET Framework 3.5 or 4.8 installed.

    Restart requirement

    You must restart the computer after you apply this update if any affected files are being used. We recommend that you exit all .NET Framework-based applications before you apply this update.


    Source: https://support.microsoft.com/en-us/...-net-framework

    See also: https://devblogs.microsoft.com/dotne...-version-2004/


    Direct download links for KB4562899 MSU file from Microsoft Update Catalog:

    Download KB4562899 MSU for Windows 10 v2004 32-bit (x86) - 39.7 MB

    Download KB4562899 MSU for Windows 10 v2004 64-bit (x64) - 62.8 MB

    Download KB4562899 MSU for Windows 10 v2004 ARM64 - 39.7 MB
    Brink's Avatar Posted By: Brink
    31 Jul 2020


  1. Posts : 68,931
    64-bit Windows 11 Pro for Workstations
       #1

    KB4562899 Cumulative Update .NET Framework 3.5, 4.8 Windows 10 July 31-kb4562899.jpg
      My Computers


  2. Posts : 94
    Windows 10 - 21H2
       #2

    Downloaded this one manually. Originally, the automatic check queued the update. I restarted the computer a few hours later and when I checked the update history a few hours later, it said that this update failed with an 0x8024001e error and the update page said "we couldn't complete the install because an update service was shutting down" and kept that message up after clicking retry. I suspect the categorization of this update as "other" instead of "quality" might not push it to some devices automatically? and to go along with the hiding of optional updates..

    So anyways, the manual install worked fine. Upon emerging from the restart, the orchestrator downloaded a second copy of this update and then the log said "Installation Successful" 5 seconds after that download finished (with no log for "installation started"). So, alright then.
      My Computer


  3. Posts : 16,946
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #3

    Do you know why it is called 'Preview'?

    Denis
      My Computer


  4. Posts : 1,862
    Windows 10 Pro 2004 20H1
       #4

    Try3 said:
    Do you know why it is called 'Preview'?
    From Microsoft -

    Preview of Monthly Rollup

    Definition: A tested, cumulative set of new updates that are packaged together and distributed over Windows Update, WSUS, System Center Configuration Manager and Microsoft Update Catalog ahead of the release of the next Monthly Rollup for customers to proactively download, test and provide feedback. The Preview of Monthly Rollup is product specific and addresses new non-security updates, and includes fixes from the latest Monthly Rollup.
      My Computer


  5. Posts : 16,946
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #5

    Thanks.

    Where is that quotation taken from?

    Denis
      My Computer


  6. Posts : 1,862
    Windows 10 Pro 2004 20H1
       #6

    Microsoft.
      My Computer


  7. Posts : 16,946
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #7

    Try3 said:
    Do you know why it is called 'Preview'?
    Standard terminology for MS software updates - KB824684

    and, for this case, there is a blog at

    Net Framework Monthly Rollups Explained - Net Blog [MS]

    Denis
      My Computer


  8. Posts : 349
    Windows 10
       #8

    A preview update should not be installed automatically if you check for updates.
      My Computer


  9. Posts : 624
    Windows 11 Pro (x64)(v23H2)(Build 22631.3447)
       #9

    Ground Sloth said:
    A preview update should not be installed automatically if you check for updates.
    yeah.. I installed that Saturday the 1st of August 2020 aka yesterday....
    so far no issues..
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:10.
Find Us




Windows 10 Forums