As with KB5000842 for Windows 10 21H1, 20H2, and 2004, Microsoft has now also made KB 5000850 available for download as a non-security-relevant update. This update removes Microsoft Edge (Legacy). The new version number is 18363.1474
Remember, for Windows 10 1909, support for consumers will expire with the security update in May. As a highlight for this update, Microsoft states:
- Updates a zoom issue that occurs when using Microsoft Edge IE mode on devices with multiple high DPI monitors.
- Updates an issue with Japanese input that occurs after the focus changes between fields in Microsoft Edge Legacy.
- Updates an issue where File Explorer filtering search results would not display anything or display "Calculation Filters" indefinitely.
Fixed issues:
- Removes the Microsoft Edge legacy desktop application that is no longer supported and installs the new Microsoft Edge.
- Addresses a zoom issue that occurs when using Microsoft Edge IE mode on devices with multiple high DPI monitors.
- Allows administrators to use Group Policy to enable advanced keyboard shortcuts, including CTRL + S, for users in Microsoft Edge IE mode.
- Fixes a problem that can lead to a deadlock if a COM server sends an event to multiple subscribers in parallel.
- Addresses an issue with Japanese input that occurs after focus changes between fields in Microsoft Edge Legacy.
- Addresses an issue that could cause 16-bit apps running on NT Virtual DOS Machine (NTVDM) to stop working when you open them.
- Fixes a problem with USB 3.0 hubs. A device connected to the hub might stop working if you choose to put the device to sleep or restart the device.
- Addresses an issue that prevents users from customizing or disabling the touchpad due to administrative settings.
- Resolves an issue where File Explorer filtering search results could result in nothing or “Computer Filters” showing indefinitely.
- Updates Volgograd, Russia time zone from UTC + 4 to UTC + 3.
- Adds a new time zone (UTC + 2: 00 Juba) for the Republic of South Sudan.
- Addresses an issue with the Windows event log forwarding client returning the first matching certificate without checking private key permissions. With this update, the Windows event log forwarding client only selects the client's certificate if the network service has read permissions for the private key.
- Addresses an issue that could cause PowerShell-based monitors to stop working when you enable transcription on the systems.
- Addresses an issue that prevents BranchCache from working when you activate Windows using # A0 (Cloud Solution Provider).
- Addresses an issue preventing App-V applications from opening and error 0xc0000225.
- Addresses an issue in which some computers registered with a Mobile Device Management (MDM) service cannot sync if the device manufacturer name contains a reserved character.
- Addresses an issue with using a Configuration Service Provider (# A0) to configure a custom setting for Monitor other logon / logoff events. The custom setting does not take effect.
- Updates 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 reason for checking in allows the MDM service to make better decisions about synchronization sessions. This change requires the OMA-DM service to negotiate a protocol version of 4.0 with the Windows OMA-DM client.
- Addresses a credential roaming issue that occurs when Windows Hello for Business is enabled.
- Addresses an issue that prevents users from using Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in desktop mode.
- Addresses an issue that could prevent Hypervisor-Protected from enabling Code Integrity (HVCI) when configured using Group Policy.
- Addresses an issue that could cause appidcertstorecheck.exe to run on a system when AppLocker is enabled and the system is not on the internet.
- Addresses an issue that could result in a black screen or delay in logging in to an Azure Active Directory hybrid computer while the computer tries to connect to login.microsoftonline.com.
- Fixes an issue that prevents the chrome-based Microsoft Edge from working. This problem occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are activated in the virtual environment.
- Addresses possible race conditions that will occur when the system calls NtOpenKeyEx (), resulting in a stop error.
- Addresses a high memory usage issue when performing XSLT transformations with MSXLM6.
- Addresses an issue that prevents Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
- Addresses an issue that could cause the cluster network interface to stop working for a short period of time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system may not recognize that the NIC is working and the NIC may remain in an error state.
- Addresses an issue with logging in to a device that is in the current domain by using the default user profile of a device that is in a different but trusted domain. The profile service of the current domain cannot get the default user profile from the trusted domain and uses the local default user profile instead.
- Addresses an issue with assessing the compatibility status of the Windows ecosystem to ensure application and device compatibility for all updates for Windows.
- Addresses an issue that could cause Caps Lock to unexpectedly activate when using RemoteApp.
- Fixes a problem with the svhost process that hosts the Microsoft-Windows-TerminalServices-LocalSessionManager. The svhost process is consuming more and more memory due to a leak in COMMAND_ENTRY. Leaking memory can cause problems logging into an application or remote desktop. In extreme cases, the server may stop responding.
- support.microsoft
Manual download of KB5001205 as SSU
- The KB5001205 as SSU is required so that the new Edge can be installed
- windows10.0-kb5001205-x64.msu
- windows10.0-kb5001205-x86.msu
- windows10.0-kb5001205-arm64.msu
- More at support.microsoft.com/kb5001205
0 Comments