[German]As of May 20, 2021 (3rd week of the month, C-Week), Microsoft has released several optional cumulative (preview) updates for Windows 10 version 1809 and 1909, as well as their Windows Server counterparts. Here's an overview of the updates in question.
The information can be found in the Windows 10 update history page. It should be noted that these updates are so-called preview or preview updates. These are optional and must be manually triggered for download and installation by default.
Update KB5003212 for Windows 10 V1909
Since Windows 10 version 1909 has reached the end of support in the Home, Pro, Pro for Workstation, Nano Container and Server SAC editions, the updates are only available for Enterprise, Education and IoT Enterprise. Cumulative update KB5003212 for Windows 10 version 1909 and Windows Server 1909 raises the build to 18363.1592. The update includes a number of bug fixes, but no new operating system features and no security fixes. Here's the list of changes described as highlights:
- Updates an issue that prevents users from receiving geographic location information.
- Updates an issue with muting a phone call when you transfer the call.
- Updates an issue that prevents a touch device from working as a serial mouse in multiple monitor situations.
Below is the complete list of fixed bugs and changes.
- Addresses an issue with the just-in-time (JIT) behavior of jscript9.dll.
- Addresses an issue that might cause a device to stop responding during hybrid shutdown.
- Addresses an issue that prevents a touch device from working as a serial mouse in multiple monitor situations.
- Addresses an issue in Safe Mode that prevents users from signing in if Web Sign-in is enabled.
- Addresses an issue in Active Directory (AD) Admin Center that displays an error when it lists many organizational units (OU) or container objects and PowerShell Transcription is enabled. The error message is, "Collection was modified after the enumerator was instantiated".
- Addresses an issue with devices that were configured using mobile device management (MDM) RestrictedGroups, LocalUsersAndGroups, or UserRights policies. These devices incorrectly continue to receive the policy after you use MDM to remove the configuration profile that has the policy. As a result, users of the affected devices might have incorrect group memberships and UserRights assignments or other symptoms. This issue occurs after installing Windows updates from October 20, 2020 and later.
- Addresses an issue with the Autopilot Reset command taking too long to process after it has been sent.
- Addresses an issue that might cause application installers to fail. This issue occurs when you enable Address Space Layout Randomization (ASLR) using the PowerShell command "set-processmitigation -system -enable forcerelocateimages".
- Addresses an issue that fails to apply BitLocker encryption automatically using a Group Policy. This issue occurs on external drives that have a master boot record (MBR) active boot partition.
- Addresses a memory leak issue in PKU2U that causes cluster nodes to run out of memory.
- Addresses an issue that fails to register a DNS update to an A record and a PTR when Azure virtual machines update against corporate DNS zones.
- Addresses an issue that prevents users from receiving geographic location information even when all the geolocation UI settings are enabled correctly, and the device contains a location sensor.
- Addresses an issue with muting a phone call when you transfer the call.
- Addresses an issue with per-user profiles that occurs after you set the Group Policy Object "Allow everyone to create all user profiles" to "Disabled". After restarting the device, Wi-Fi doesn't automatically reconnect when using per-user profiles.
- Addresses an issue that prevents a task from working correctly when you set the condition "Start only if the following network connection is available" for the task.
- Addresses a memory leak that might occur in some Remote Desktop screen sharing scenarios.
- Addresses an issue with the PerfMon API that might cause handle leaks, which slow performance.
- Updates Delivery Optimization to accept a custom port in the DOCacheHost configuration.
- Addresses an issue that might cause endless replication when you promote a new domain controller and the Active Directory Recycle Bin feature is enabled.
- Addresses an issue that sporadically prevents the Resource Host Subsystem (RHS) from registering network name resources in the Domain Name System (DNS). As a result, Event ID 1196 appears.
- Addresses a timing issue that might cause a RemoteApp to intermittently duplicate characters that were entered on the local keyboard or pasted from the Windows clipboard.
The update is optional and is only offered under Windows Update when the user explicitly checks for updates in the settings page. The update can also be downloaded and installed from the Microsoft Update Catalog. However, it is important to make sure that the latest Servicing Stack Update (SSU) is installed. Microsoft lists the certificate issue that has been known for months when upgrading from version 1809 with this update.
In addition, Microsoft has made direct improvements to the update client for Windows 10 V1909 to improve its reliability.
Update KB5003217 for Windows 10 V1809
Windows 10 version 1809 is out of support on May 11, 2021 (applies to Enterprise, Education and IoT Enterprise editions) and there are no longer monthly security and quality updates. However, Microsoft is offering the update for Enterprise G, HoloLens and LTSC editions for Client, Server and IoT. Cumulative update KB5003217 for Windows 10 V1809 and its server counterparts bumps the build to 17763.1971. Here's the list of what are considered highlights changes:
Updates an issue that prevents a touch device from working as a serial mouse in multiple monitor situations.
Below is the complete list of fixed bugs and changes.
- Addresses an issue with the just-in-time (JIT) behavior of jscript9.dll.
- Addresses an issue that causes the Shutdown Event Tracker to appear every time you sign in, even after you dismiss the dialog correctly.
- Addresses an issue that prevents a touch device from working as a serial mouse in multiple monitor situations.
- Addresses an issue in Active Directory (AD) Admin Center that displays an error when it lists many organizational units (OU) or container objects and PowerShell Transcription is enabled. The error message is, "Collection was modified after the enumerator was instantiated".
- Addresses an issue with the Autopilot Reset command taking too long to process after it has been sent.
- Addresses an issue that might cause application installers to fail. This issue occurs when you enable Address Space Layout Randomization (ASLR) using the PowerShell command "set-processmitigation -system -enable forcerelocateimages".
- Addresses a memory leak issue in PKU2U that causes cluster nodes to run out of memory.
- Addresses an issue that fails to apply BitLocker encryption automatically using a Group Policy. This issue occurs on external drives that have a master boot record (MBR) active boot partition.
- Addresses an issue that sometimes causes event log entries to appear corrupted for Microsoft-Windows-Kerberos-Key-Distribution-Center source and Event IDs 4933, 4928, and 4937.
- Addresses an issue that fails to register a DNS update to an A record and a PTR when Azure virtual machines update against corporate DNS zones.
- Addresses an issue that might prevent the Windows Dynamic Host Configuration Protocol (DHCP) Server from offering a lease to a DHCPv6 client after the client moves to a different virtual LAN (VLAN).
- Addresses an issue that prevents a task from working correctly when you set the condition "Start only if the following network connection is available" for the task.
- Addresses a memory leak that might occur in some Remote Desktop screen sharing scenarios.
- Adds support for the USB Test and Measurement Class.
- Addresses an issue with the PerfMon API that might cause handle leaks, which slow performance.
- Addresses an issue that sporadically prevents the Resource Host Subsystem (RHS) from registering network name resources in the Domain Name System (DNS). As a result, Event ID 1196 appears.
The update is optional and is only offered in Windows Update when the user explicitly checks for updates in the settings page. The update can also be downloaded and installed from the Microsoft Update Catalog. However, it is important to make sure that the latest Servicing Stack Update (SSU) is installed. Microsoft lists two known issues with this update in the support post.
In addition, Microsoft has made direct improvements to the update client for Windows 10 V1809 to improve its reliability.
new preview update for Win10 v2004, 20H2 & 21H1 – KB5003214 released Tue. May 25 (build 1904x.1023):
https://support.microsoft.com/help/5003214
https://www.catalog.update.microsoft.com/Search.aspx?q=5003214
I had this issue "OS settings cannot be opened" after aplied KB5003217 in a Windows 10 LTSC 1809.
Just now I figured out that the problem exist when some especific user language is selected, in my case Portuguese-Brazil (PT-BR).
When I change the language to fr-FR, en-EN or de-DE there is no problem. It seems the problem is language pack related. I found this post about this issue: https://docs.microsoft.com/en-us/answers/questions/408413/kb5003217-os-settings-cannot-be-opened.html, without any solution yet.