Releasing Windows 10 Build 19044.2192 to Release Preview Channel

Posted by

This post has been republished via RSS; it originally appeared at: Windows Blog.

Hello Windows Insiders, today we are releasing Windows 10 21H2 Build 19044.2192 (KB5018482) to the Release Preview Channel for those Insiders who are on Windows 10, version 21H2. This update includes the following improvements:
  • We fixed an issue that affects Distributed Component Object Model (DCOM) authentication hardening. We will automatically raise the authentication level for all non-anonymous activation requests from DCOM clients to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY. This occurs if the authentication level is below Packet Integrity.
  • We fixed a DCOM issue that affects the Remote Procedure Call Service (rpcss.exe). We raise the authentication level to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY instead of RPC_C_AUTHN_LEVEL_CONNECT if RPC_C_AUTHN_LEVEL_NONE is specified.
  • We fixed an issue that causes an OS upgrade to stop responding, and then it fails.
  • We fixed an issue that affects the Microsoft Azure Active Directory (AAD) Application Proxy connector. It cannot retrieve a Kerberos ticket on behalf of the user. The error message is, “The handle specified is invalid (0x80090301).”
  • We fixed an issue that affects the font of three Chinese characters. When you format these characters as bold, the width size is wrong.
  • We fixed an issue that affects Microsoft Direct3D 9 games. The graphics hardware stops working if the hardware does not have a native Direct3D 9 driver.
  • We fixed graphical issues in games that use Microsoft D3D9 on some platforms.
  • We fixed an issue that affects Microsoft Edge when it is in IE Mode. The titles of pop-up windows and tabs are wrong.
  • We fixed an issue that affects Microsoft Edge IE mode. It stops you from opening webpages. This occurs when you enable Windows Defender Application Guard (WDAG) and you do not configure Network Isolation policies.
  • We fixed an issue that might cause an application to stop responding. This might occur when the input queue overflows.
  • We fixed an issue that affects input method editors (IME) from Microsoft and third parties. They stop working when you close the IME window. This occurs if the IME uses Windows Text Services Framework (TSF) 1.0.
  • We fixed an issue that affects the lasso tool in a graphics editing program.
  • We fixed an issue that affects Miracast advertisements. This issue occurs on Surface Hub devices under certain conditions.
  • We fixed an issue that affects some drivers. They use more power when you play hardware-protected digital rights management (DRM) content.
  • We fixed an issue that affects .msi files. Windows Defender Application Control (WDAC) will ignore them when you disable script enforcement.
  • We fixed an issue that affects a remote desktop virtual desktop infrastructure (VDI) scenario. The session might use the wrong time zone.
Thanks, The Windows Insider Program Team

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.