Windows 10 20H2

Discussion in 'Windows OS and Software' started by Spartan@HIDevolution, Sep 9, 2019.

  1. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist

    Likes Received:
    Trophy Points:
    Perhaps it is something to be thankful for. One step forward, two steps backward isn't really progress. Even when you don't like the conditions, predictability is an underrated blessing.
    Spartan@HIDevolution and Papusan like this.
  2. Papusan

    Papusan TURDBOOKs Sucks! Dont waste your $$$ on FILTHY

    Likes Received:
    Trophy Points:
    February 24, 2021—KB4601382 (OS Builds 19041.844 and 19042.844) Preview

    Before installing this update


    Starting with this release, Microsoft will combine the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). To utilize this improvement, install the most recent standalone SSU (KB4598481) before installing this LCU. If you install this LCU before installing KB4598481, you might encounter error 0x800f0823 – CBS_E_NEW_SERVICING_STACK_REQUIRED. Close the error message and install the recommended SSU.

    Known issues for KB4601382
    • If you use the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows input of Furigana characters, you may not get the correct Furigana characters. You may have to enter the furigana characters manually. We are working on a solution and will provide an update in one of the next versions.
    • If you have problems with the installation and receive the error message 0x800f0988 , Ben's fix will also help here .
    • Problems that are currently still open or that have already been resolved are always updated on this page .
    Problems resolved by KB4601382
    • The highlights:
    • Windows Hello multi-camera support to set the default as an external camera when there are both external and internal Windows Hello cameras.
    • Windows Defender Application Guard performance improvements, including optimization of the scenario times when opening documents.
    • We fixed an issue that caused a delay of a minute or more when you open an Office document using Microsoft Defender Application Guard (WDAG). This occurs when you try to open a file using a Universal Naming Convention (UNC) path or a Server Message Block (SMB) share link.
    • We have improved Robocopy's performance when copying files that are over 400MB in total.
    • We fixed an issue that caused a WDAG container to use almost 1 GB of memory when the container is idle.
    • Windows Management Instrumentation (WMI) Group Policy Service (GPSVC) update performance has been improved to support remote work scenarios.
    • We fixed an issue that resulted in changes that the Active Directory (AD) administrator makes to user or computer group membership being slow to propagate. Although the access token is eventually updated, these changes will not be reflected when the administrator uses gpresult / r or gpresult / h to generate a report.

    • We fixed an issue with a memory leak in Internet Explorer 11 that occurs when using the Chinese language pack.
    • We fixed an issue with certain COM + calling policies causing blocking in certain applications.
    • Fixed an issue that prevented certain Win32 applications from opening as a different user when using the Runas
    • We fixed an issue displaying unexpected screens during Windows Out of Box Experience (OOBE).
    • We have fixed a problem that can lead to a deadlock if a COM server delivers an event to several subscribers in parallel.
    • We fixed an issue in Advanced Display Settings showing the incorrect available refresh rates for HDR (High Dynamic Range) displays.
    • Fixed an issue that could prevent certain CAD applications from opening when those applications rely on OpenGL.
    • We fixed an issue where video playback could flicker when rendering on certain low latency monitors.
    • Fixed an issue that sometimes prevented strings from being entered into the Input Method Editor (IME).
    • We fixed an issue where resources are being drained because the Desktop Windows Manager (DWM) is leaking handles and virtual memory in Remote Desktop sessions.
    • We fixed an issue with a stop error that occurs on startup.
    • We fixed an issue that can delay the deployment of a Windows Hello for Business (WHfB) Certificate Trust when opening the Settings-> Accounts-> Sign-in Options page.
    • We fixed an issue that could sometimes result in some keyboard keys not working, e.g. B. the Home key, the Ctrl key, or the left arrow key. This problem occurs when you set the Japanese IME input mode to Kana.
    • We removed the history of previously used images from a user account's profile.
    • We fixed an issue where the wrong language is displayed on a console after changing the system locale.
    • We fixed an issue resulting in the Windows Remote Management (WinRM) host process stop working when formatting messages from a PowerShell plugin.

    • We fixed an issue in the Windows Management Instrumentation (WMI) service causing a heap leak every time security settings are applied to WMI namespace permissions.
    • We fixed an issue with screen rendering after opening games with certain hardware configurations.
    • We have improved the startup times for applications with roaming settings when User Experience Virtualization (UE-V) is enabled.
    • We fixed an issue where a principal on a trusted MIT realm cannot obtain a Kerberos service ticket from Active Directory Domain Controllers (DC). This occurs on devices that have installed Windows Updates that contain CVE-2020-17049 protections and have PerfromTicketSignature configured to 1 or higher. These updates were released between November 10, 2020 and December 8, 2020. The ticket purchase also fails with the "KRB_GENERIC_ERROR" error if callers submit a PAC-less Ticket Granting Ticket (TGT) as an evidence ticket without specifying the USER_NO_AUTH_DATA_REQUIRED flag.
    • We fixed high memory and CPU usage in Microsoft Defender for Endpoint.
    • We have improved the functionality of the Data Loss Prevention and Insider Risk Management solution in Microsoft 365 Endpoints.
    • We fixed an issue that displays an error when you try to open an untrusted webpage with Microsoft Edge or open an untrusted Microsoft Office document. The error is: "WDAG Report - Container: Error: 0x80070003, Ext-Fehler: 0x00000001". This problem occurs after installing the .NET update KB4565627.
    • We fixed an issue preventing wevtutil from parsing an XML file.
    • We fixed an issue that does not report an error when the Elliptic Curve Digital Signature Algorithm (ECDSA) generates invalid keys of 163 bytes instead of 165 bytes.
    • We've added support for using the new Chromium-based Microsoft Edge as a dedicated Access Single Kiosk app. You can now also customize a breakout key sequence for single app kiosks. For more information, see Configure Microsoft Edge Kiosk Mode.
    • Fixed an issue with User Datagram Protocol (UDP) broadcast packets that are larger than the Maximum Transmission Unit (MTU). Devices that receive these packets discard them because the checksum is not valid.
    • A problem has been fixed in which the WinHTTP AutoProxy service does not adhere to the value for the maximum Time To Live (TTL) in the PAC (Proxy Auto-Configuration) file. This prevents the cached file from being dynamically updated.
    • We have improved the ability of the WinHTTP Web Proxy Auto-Discovery Service to ignore invalid Web Proxy Auto-Discovery Protocol (WPAD) URLs returned by the Dynamic Host Configuration Protocol (DHCP) server.
    • We have displayed the correct Envelope media type as the selectable output paper type for Universal Print queues.
    • We stopped displaying a random paper size for a printer when it is using the Microsoft Internet Printing Protocol (IPP) Class Driver.
    • We've enabled Windows to get updated printer functionality to ensure users have the correct set of print options to choose from.
    • We have updated support for hole punch and stapler positions for long-edge print jobs in the first-feed direction on certain printers.
    • We fixed an issue that could cause the IKEEXT service to intermittently stop working.
    • We fixed an issue that could prevent a Non-Volatile Memory Express (NVMe) device from going into the correct power state.
    • We fixed an issue that can cause stop error 7E in sys on servers running Network File System (NFS) service.
    • We fixed an issue that was preventing the User Profile Service from reliably detecting a slow or fast connection.
    • Fixed an issue that caused a metadata lock conflict when using working folders.
      We added a new dfslogkey as described below:
      The RootShareAcquireSuccessEvent has the following possible values:

    • Default value = 1; activates the protocol.
    • Any value other than 1; deactivates the protocol.
    • If this key does not exist, it will be created automatically. For a change to dfslog / RootShareAcquireSuccessEvent in the registry to take effect, you must restart the DFSN service.
    • We have updated the Open Mobile Alliance (OMA) Device Management (DM) synchronization protocol by adding a check-in reason for requests from the client to the server. The check-in reason enables the Mobile Device Management (MDM) service to make better decisions about synchronization sessions. With this change, the OMA-DM service must negotiate a protocol version of 4.0 with the Windows OMA-DM client.
    • We disabled token binding in Windows Internet (WinINet) by default.
    • We fixed an issue that could prevent the correct furigana characters from being displayed in applications that automatically allow furigana characters to be entered. You may have to enter the furigana characters manually. This problem occurs when you use the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in these applications.
    Direct download link CU (Cumulative Update) - KB4601382

    February 24, 2021-KB4601554 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10, version 2004, Windows Server, version 2004, Windows 10, version 20H2, and Windows Server, version 20H2

    Direct download link Dotnetfx48 CU
  3. KING19

    KING19 Notebook Deity

    Likes Received:
    Trophy Points:
    Is 20H2 finally safe to use without any issues? I would have to upgrade anyways since 1909 wont be supported anymore in May and since 20H1 was a major update i would have to reinstall Windows to do so.

Share This Page