Windows 10 1809/1909: Preview-Updates (25.3.2021)

[English]Microsoft hat zum 26. März 2021 Updates für Windows 10 Version 1809 und 1909 freigegeben. Es handelt sich um Updates, die Bugs beheben sollen. Bei Windows 10 Version 1909 soll der Legacy Edge durch das Update aus der Windows 10-Installation entfernt werden. Wie es scheint, korrigieren diese Preview-Updates nichts mehr an den im März 2021 aufgetretenen, aber durch Sonderupdates korrigierten, Druckproblemen.

Eine Liste der Updates lässt sich auf dieser Microsoft-Webseite abrufen. Die D-Woche-Updates sind optional und dienen in Firmen zum Testen von Funktionen, die im April 2021 zum Patchday ausgerollt werden. Ich habe nachfolgend die Details herausgezogen.

Updates für Windows 10 Version 1909

Windows 10 Version 1903 ist am 8. Dezember 2020 aus dem Support gefallen. Für das in 2019 erschienene Windows 10 Version 1909 stehen folgende Updates zur Verfügung.

Update KB5000850 für Windows 10 Version 1909

Das kumulative Update KB5000850 steht für Windows 10 Version 1909 sowie für Windows Server Version 1909 bereit und hebt die OS-Build auf 18363.1474. Das Update beinhaltet Qualitätsverbesserungen aber keine neuen Betriebssystemfunktionen. Hier die Liste der Verbesserungen, von Microsoft als Highlights bezeichnet:

• 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.

Es wurden also ein Zoom-Bug im IE-Mode des Edge und ein Bug beim Filtern im Dateiexplorer behoben – die Korrektur des Edge bei japanischen Eingaben dürfte meinen Leserkreis hier im Blog eher nicht tangieren. In der Liste der nachfolgenden Änderungen ist der Hinweis, dass der Legacy Edge (also der alte Edge) jetzt entfernt wird, der wichtigste Punkt sein.

• 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.

Dieses Update ist optional und sollte auf der Seite Windows Update der Einstellungen-App unter Optionale Updates als Link angezeigt werden. Erst bei Anwahl des Links wird das Update heruntergeladen und installiert. Dieses Update ist auch im Microsoft Update Catalog, nicht aber per WSUS erhältlich. Microsoft empfiehlt bei einer manuellen Installation dringend, das neueste Service Stack Update (SSU) KB5001205 vor dem neuesten kumulativen Update (LCU) zu installieren. Für das Update gibt Microsoft im Supportbeitrag u.a. das schon länger bestehende Zertifikate Problem an, also dort ggf. nachlesen, was sonst noch zu beachten ist.

Zudem hat Microsoft ein Update direkt für den Windows Update Client veröffentlicht, um dessen Zuverlässigkeit zu verbessern. Das wird außerhalb von Windows Update ausgerollt, wenn die Maschine kompatibel und keine LTSC-Variante ist und Updates nicht per GPO blockiert wurden.

Updates für Windows 10 Version 1809

Für Windows 10 Oktober 2018 Update (Version 1809) und Windows Server 2019 stehen folgende Updates zur Verfügung.

Update KB45000854 für Windows 10 Version 1809

Das kumulative Update KB5000854 hebt die OS-Build (laut MS) auf 17763.1852  und beinhaltet Qualitätsverbesserungen aber keine neuen Betriebssystemfunktionen. Hier die Liste der Verbesserungen, von Microsoft als Highlights bezeichnet:

• 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.

Das sind quasi die gleichen Fixes wie für die Version 1909. Hinzukommen folgende Fixes und Verbesserungen an der 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.

Dieses Update ist optional und sollte auf der Seite Windows Update der Einstellungen-App unter Optionale Updates als Link angezeigt werden. Erst bei Anwahl des Links wird das Update heruntergeladen und installiert. Dieses Update ist auch im Microsoft Update Catalog, nicht aber per WSUS erhältlich. Microsoft empfiehlt bei einer manuellen Installation dringend, das neueste Service Stack Update (SSU) KB5000859 vor dem neuesten kumulativen Update (LCU) zu installieren. Für das Update gibt Microsoft im Supportbeitrag u.a. das schon länger bestehende Problem an, dass der Fehler 0x800f0982 – PSFX_E_MATCHING_COMPONENT_NOT_FOUND auftritt. Also dort ggf. nachlesen, was sonst noch zu beachten ist.

Zudem hat Microsoft ein Update direkt für den Windows Update Client veröffentlicht, um dessen Zuverlässigkeit zu verbessern. Das wird außerhalb von Windows Update ausgerollt, wenn die Maschine kompatibel und keine LTSC-Variante ist und Updates nicht per GPO blockiert wurden.

Ähnliche Artikel:
Patchday: Windows 10-Updates (9. März 2021)
Windows 10: Außerplanmäßiges Update für Drucken BlueScreen-Bug
Windows 10: Außerplanmäßiges Update für Grafik-Bug beim Drucken
Windows 10: März 2021-Update erneut freigegeben?