Microsoft has released a new preview build of Windows 11 22000.917 (KB5016691) for Windows Insiders using the Release Preview channel.
This cumulative update brings with it a number of fixes for bugs found in the release version of Windows 11. You can find the full list of fixes on the official blog.
Complete build number: 10.0.22000.829.co_release_svc_prod2.220706-1736.
Changes and fixes
- New! Now IT administrators can remotely add languages and manage related features. Moreover, it became possible to manage language scripts in multiple instances of Endpoint Manager.
- New! File compression now occurs regardless of file size if Server Message Block (SMB) Compression is configured.
- New! Enhanced capabilities of Microsoft Defender for Endpoint to detect and intercept ransomware and advanced attacks.
- We fixed an issue where in some full configuration scenarios ServerAssignedConfigurations was equal to zero.
- We fixed an issue that affected the Auto HDR feature for GPU drivers that support Cross-Adapter Resource Scanning (CASO).
- We fixed a known issue resulting in Microsoft Edge becoming unresponsive when using IE mode. This issue also prevented interaction with dialog boxes.
- We fixed an issue that caused virtualized App-V Microsoft Office applications to not open or stop working.
- We fixed an issue where, under certain circumstances, after resetting the device, installation of the Windows Hello for Business certificate could fail.
- Fixed several issues related to printing to USB printers, such as:
- Fixed a crash in printers after restarting or reinstalling them.
- Fixed incorrect behavior after switching from Internet Printing Protocol (IPP) Class Driver to Independent Hardware Vendor (IHV) driver.
- Fixed issues with bi-directional communication that prevented access to device features
- Fixed an issue that affected ProjectionManager.StartProjectingAsync API and did not allow connecting to Miracast Sinks when using certain localizations.
- We fixed an issue that slowed BitLocker performance.
- We fixed an issue that caused Windows 11 SE to not trust some apps from the Microsoft Store.
- We fixed an issue resulting in HyperVisor Code Integrity not being automatically enabled on devices with ARM64 processors.
- We fixed an issue that prevented non-Windows devices from being able to authenticate. This issue occurs when users connect to Windows-based Remote Desktop and use a smart card for authentication.
- We fixed an issue where the Resultant Set of Policy tool (Rsop.msc) stopped working if it processed 1000 or more “File System” security settings.
- We fixed an issue that caused the Take the Test app to remove all policies related to locking the device when the app was closed.
- We fixed an issue that caused the Settings app to stop working on server-side domain controllers (DCs) when accessing the Privacy -> Activity History page.
- We fixed an issue where some Bluetooth audio headsets might stop playing after setting the status indicator. This issue affects modern systems that support Advanced Audio Distribution Profile (A2DP).
- We fixed an issue where devices were not prompted by Windows Update to extend the functionality of the base driver package if the extension was installed separately from the base driver.
- We fixed an issue that caused the Local Security Authority Subsystem Service (LSASS) to stop working on Active Directory domain controllers. This issue occurs when LSASS processes concurrent Lightweight Directory Access Protocol (LDAP) requests over Transport Layer Security (TLS) that cannot be decrypted. Error code: 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN).
- We fixed an issue with looking up a non-existent security identifier (SID) within the local domain using a read-only domain controller (RODC). Search unexpectedly returns STATUS_TRUSTED_DOMAIN_FAILURE instead of STATUS_NONE_MAPPED or STATUS_SOME_MAPPED.
- We fixed an issue that could result in token leaks in the Local Security Authority Server Service (LSASS). This issue affects devices that have Windows Updates June 14, 2022 or later installed. The issue occurs when the device is running some form of service for the user (S4U) on a non-Trusted Computing Base (TCB) Windows service that runs as a Network Service.