On Friday, Windows Insiders received a beta and release build of Windows 11 that contained only fixes, but we completely overlooked that Windows Insiders still running Windows 10 21H2 also received a new build. containing only fixes. New build 19044.1499 (21H2) (KB5009596) is available through the Release Preview channel.
This update includes the following improvements:
- We fixed an issue in Microsoft UI Automation that could cause Microsoft Outlook to stop working.
- We have changed DST to start in February 2022 instead of March 2022 in Jordan.
- We fixed an issue that caused the Windows Subsystem for Linux 2 (WSL2) Local Host Relay to not start when fast startup was enabled.
- We’ve added parameters that are passed in in telemetry to collect additional usage data to address application compatibility issues.wmic.exe
- Fixed issue in CLSID_InternetExplorer.
- We’ve added a reminder to Internet Explorer 11 that notifies users of its impending retirement.
- We fixed an issue that could cause Japanese-language Microsoft Office applications to sometimes stop working when using the new Japanese Input Method Editor (IME).
- We fixed an issue that caused apps to stop working when entering text with a Chinese IME.
- We fixed an issue that could cause Windows to stop working when using the Pen Haptics API.
- We’ve updated the Windows activation phone number for locales with the wrong phone number.
- We fixed an issue that caused a device to incorrectly report itself as not compliant with Conditional Access due to antivirus or firewall configuration.
- We fixed an issue that caused printing to stop or produce incorrect output when printing using USB on Windows 10 version 2004 or later.
- We fixed an issue that was affecting the remote desktop screen in some cases when using Advanced Video Coding (AVC) software encoding.
- We fixed an issue that prevented certain surround sounds from playing in Microsoft Edge.
- We fixed a deadlock in i. vpnike.dll_
- We fixed an issue that affected the Fast Identity Online 2.0 (FIDO2) credential provider and prevented the PIN entry window from being displayed.
- We fixed an issue that caused Windows to stop working and throw an “IRQL_NOT_LESS_OR_EQUAL” error.
- We fixed an issue that could cause the Get-TPM PowerShell command to failThe PowerShell command fails when trying to report Trusted Platform Module (TPM) information. The command fails with the error “0x80090011 Microsoft.Tpm.Commands.TpmWmiException,Microsoft.Tpm.Commands.GetTpmCommand “.
- We fixed an issue that caused the AltGr key to stop working if the Remote Desktop client was running or RemoteApp was disabled.
- We’ve added a new feature that gives you direct access to a selection of your Microsoft Edge profiles from the News & Interests section. You can also go to Microsoft Edge directly from News & Interests in the same qualifying profile.
- We’ve added a new feature called “Settings Sync” for users who are downgrading to the original version of Windows 11. You’ll use Settings Sync to automatically back up your app list to your Microsoft account. You can then quickly restore these apps to your original Windows 11 device. This new feature will be rolled out in the coming weeks.
- Fixed an issue that caused working Bluetooth devices to stop working when trying to connect to a non-working Bluetooth device.
- Fixed an issue that caused the device to stop working and reboot. This issue occurs when you query the Windows NT Directory Service (NTDS) counters after you stop the NTDS.lsass.exe service
- We fixed an issue that prevented the “Do not allow compression on all NTFS volumes” Group Policy Object (GPO) from being applied in some cases.
- Fixed an issue that prevented Robocopy from repeating the file copy process.
- Fixed an issue that could occur when you enable verbose Active Directory Federation Services (AD FS) audit logging and log an invalid setting. As a result, event 207 is logged, indicating a failure to write to the audit log.
- Fixed a memory leak that occurred when calling WinVerifyTrust (). This issue occurs if the verification of the first signature of a file with multiple signatures fails.
This build contains no known issues and, as previously stated, no new features. To check and find out which version of Windows 10 you have, simply type winver in the Windows search box on your taskbar (or right-click Start and select Run, then type winver). It should show up as “Version 21H2”.
View the official press release for build 19044.1499 here .
Thanks to the anonymous friend who sent the news tip.