[German]Microsoft has released updates for Windows 10 version 1809 and 1909 as of March 26, 2021. These are updates that are supposed to fix bugs. For Windows 10 version 1909, the update is supposed to remove the Legacy Edge from the Windows 10 installation. As it seems, these preview updates do not correct anything more about the printing issues that occurred in March 2021, but were corrected by special updates..
Advertising
A list of the updates can be found on this Microsoft web page. The D-week updates are optional and are used in companies to test features that will be rolled out on patchday in April 2021. I have pulled out the details below.
Updates for Windows 10 Version 1909
Windows 10 version 1903 is out of support on December 8, 2020. The following updates are available for Windows 10 version 1909 released in 2019.
Update KB5000850 for Windows 10 Version 1909
Cumulative Update KB5000850 is available for Windows 10 version 1909 as well as Windows Server version 1909, and raises the OS build to 18363.1474. The update includes quality improvements but no new OS features. Here's the list of improvements, called highlights by Microsoft:
- Updates an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
- Updates an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge Legacy.
- Updates an issue that displays nothing or shows "Computing Filters" indefinitely when you filter File Explorer search results.
So a zoom bug in the IE mode of the Edge and a bug in filtering in the file explorer have been fixed – the correction of the Edge for Japanese input should rather not tangent my circle of readers here in the blog. In the list of changes below, the note that the Legacy Edge (i.e. the old Edge) is now removed is the most important point.
- Removes the Microsoft Edge Legacy desktop application that is out of support and installs the new Microsoft Edge. For more information, see New Microsoft Edge to replace Microsoft Edge Legacy with April's Windows 10 Update Tuesday release
- Addresses an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
- Allows administrators to use a Group Policy to enable extended keyboard shortcuts, including Ctrl+S, for users in Microsoft Edge IE Mode.
- Addresses an issue that might cause a deadlock when a COM server delivers an event to multiple subscribers in parallel.
- Addresses an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge Legacy.
- Addresses issue that causes 16-bit apps that run on NT Virtual DOS Machine (NTVDM) to stop working when you open them.
- Addresses an issue with USB 3.0 hubs. A device connected to the hub might stop working when you set the device to hibernate or restart the device.
- Addresses an issue that prevents users from adjusting or turning off the touchpad because of administrative settings.
- Addresses an issue that displays nothing or shows "Computing Filters" indefinitely when you filter File Explorer search results.
- Updates the 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, which returns the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client selects the client's certificate only if the Network Service has read permissions for the private key.
- Addresses an issue that causes PowerShell-based monitors to stop working when you enable transcription on the systems.
- Addresses an issue that stops BranchCache from working if you activate Windows using Cloud Solution Provider (CSP) license.
- Addresses an issue that prevents App-V applications from opening and generates error 0xc0000225.
- Addresses an issue in which some machines enrolled with a mobile device management (MDM) service fail to sync if the device manufacturer's name contains a reserved character.
- Addresses an issue with using a configuration service provider (CSP) policy to configure a custom setting for Audit Other Logon/Logoff events. The custom setting fails to take effect.
- Updates the Open Mobile Alliance (OMA) Device Management (DM) sync protocol by adding a check-in reason for requests from the client to the server. The check-in reason will allow the MDM service to make better decisions about sync sessions. With this change, the OMA-DM service must negotiate a protocol version of 4.0 with the Windows OMA-DM client.
- Addresses an issue with credential roaming that occurs when Windows Hello for Business is enabled.
- Addresses an issue that prevents users from using the Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
- Addresses an issue that might prevent Hypervisor-Protected Code Integrity (HVCI) from being enabled when you configure it using a Group Policy.
- Addresses an issue that causes multiple instances of appidcertstorecheck.exe to run on a system when AppLocker is enabled and the system is not on the internet.
- Addresses an issue that causes a black screen or delays signing in to a Hybrid Azure Active Directory joined machine while the machine attempts to connect to login.microsoftonline.com.
- Addresses an issue that prevents the Chromium-based Microsoft Edge from working. This issue occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled inside the virtual environment.
- Addresses possible race conditions that occur when the system calls NtOpenKeyEx(),which results in a stop error.
- Addresses an issue with high memory usage when performing XSLT transforms using 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 might cause the cluster network interface to stop working for a short time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system might not detect that the NIC is working and the NIC remains in a failed status.
- Addresses an issue with signing 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 retrieve the default user profile from the trusted domain and uses the local default user profile instead.
- Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
- Addresses an issue that turns on Caps lock unexpectedly when using RemoteApp.
- Addresses an issue with the svhost process that hosts the Microsoft-Windows-TerminalServices-LocalSessionManager. The svhost process consumes increasingly large amounts of memory because of a leak in COMMAND_ENTRY objects. Memory leaks might cause issues when signing in to an application or to the Remote Desktop. In extreme cases, the server might stop responding.
This update is optional and should be displayed as a link on the Windows Update page of the Settings app under Optional updates. The update is only downloaded and installed when the link is selected. This update is also available from the Microsoft Update Catalog, but not via WSUS. Microsoft strongly recommends installing the latest Service Stack Update (SSU) KB5001205 before the latest Cumulative Update (LCU) when installing manually. For the update, Microsoft states in the support article, among other things, the certificate problem that has existed for some time, so if necessary, read there what else should be noted.
Advertising
In addition, Microsoft has released an update directly for the Windows Update client to improve its reliability. This is rolled out outside of Windows Update if the machine is compatible and not an LTSC variant, and updates have not been blocked via GPO.
Updates for Windows 10 Version 1809
The following updates are available for Windows 10 October 2018 Update (version 1809) and Windows Server 2019.
Update KB5000854 für Windows 10 Version 1809
Cumulative Update KB5000854 raises the OS build (according to MS) to 17763.1852 and includes quality improvements but no new OS features. Here's the list of improvements, described by Microsoft as highlights:
- Updates an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
- Updates an issue that displays nothing or shows "Computing Filters" indefinitely when you filter File Explorer search results.
- Updates an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge Legacy.
These are the same fixes as for version 1909, plus the following fixes and improvements to the Windows version:
- Addresses an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
- Allows administrators to use a Group Policy to enable extended keyboard shortcuts, including Ctrl+S, for users in Microsoft Edge IE Mode.
- Addresses an issue that prevents users from adjusting or turning off the touchpad because of administrative settings.
- Addresses an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge Legacy.
- Addresses an issue with USB 3.0 hubs. A device connected to the hub might stop working when you set the device to hibernate or restart the device.
- Addresses an issue that displays nothing or shows "Computing Filters" indefinitely when you filter File Explorer search results.
- Addresses an issue with a heap leak that might cause explorer.exe to consume high amounts of memory.
- Updates the 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, which returns the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client selects the client's certificate only if the Network Service has read permissions for the private key.
- Addresses an issue that causes PowerShell-based monitors to stop working when you enable transcription on the systems.
- Addresses an issue that prevents App-V applications from opening and generates error 0xc0000225.
- Addresses an issue in which some machines enrolled with a mobile device management (MDM) service fail to sync if the device manufacturer's name contains a reserved character.
- Addresses an issue with RSA key generation that generates a damaged key.
- Addresses an issue that prevents users from using the Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
- Addresses an issue that might prompt for credentials when not needed and might fail to authenticate in an Azure Active Directory environment.
- Addresses an issue that causes multiple instances of appidcertstorecheck.exe to run on a system when AppLocker is enabled and the system is not on the internet.
- Addresses an issue that might prevent Hypervisor-Protected Code Integrity (HVCI) from being enabled when you configure it using a Group Policy.
- Addresses an issue that causes a black screen or delays signing in to a Hybrid Azure Active Directory joined machine while the machine attempts to connect to login.microsoftonline.com.
- Addresses an issue that prevents the Chromium-based Microsoft Edge from working. This issue occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled inside the virtual environment.
- Addresses an issue that causes a virtual machine (VM) to lose internet connectivity when you configure the Instance-Level Public IP and outbound network address translation (NAT) for the VM.
- Addresses an issue with input-output memory management unit (IoMMU) support on certain processors for Windows Server 2019 guest VMs that are on server virtualization software.
- Addresses possible race conditions that occur when the system calls NtOpenKeyEx(),which results in a stop error.
- Addresses an issue with high memory usage when performing XSLT transforms using 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 might cause the cluster network interface to stop working for a short time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system might not detect that the NIC is working and the NIC remains in a failed status.
- Addresses an issue with signing 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 retrieve the default user profile from the trusted domain and uses the local default user profile instead.
- Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
- Addresses an issue that turns on Caps lock unexpectedly when using RemoteApp.
- Adds new capabilities to the Packet Monitor (PKTMON) network diagnostic tool.
- Addresses an issue with the svhost process that hosts the Microsoft-Windows-TerminalServices-LocalSessionManager. The svhost process consumes increasingly large amounts of memory because of a leak in COMMAND_ENTRY objects. Memory leaks might cause issues when signing in to an application or to the Remote Desktop. In extreme cases, the server might stop responding.
This update is optional and should be displayed as a link on the Windows Update page of the Settings app under Optional updates. The update is only downloaded and installed when the link is selected. This update is also available from the Microsoft Update Catalog, but not via WSUS. Microsoft strongly recommends installing the latest Service Stack Update (SSU) KB5000859 before the latest Cumulative Update (LCU) when installing manually. For the update Microsoft states in the support article among other things the already long existing problem that the error 0x800f0982 – PSFX_E_MATCHING_COMPONENT_NOT_FOUND occurs. So read there if necessary, what else is to be considered.
In addition, Microsoft has released an update directly for the Windows Update client to improve its reliability. This is rolled out outside of Windows Update if the machine is compatible and not an LTSC variant, and updates have not been blocked via GPO..
Similar articles:
Patchday: Windows 10-Updates (March 9, 2021)
Windows 10: Out-of-band Update for Blue Screen printing bug
Windows 10: Out-of-band Update for graphics printing bug (March 18, 2021)
Windows 10: March 2021 update released again?
