Microsoft opens Windows 10 21H1 build 19043.844 update to beta channel

In February of this year, Microsoft released Windows 10 21H1 Build 19043.844 (KB4601382) for Beta channel users through the “seeker” experience. This means that users of the Beta channel need to go to “Settings”> “Update and Security”> “Windows Update”, and then choose to download and install the latest version of 21H1.

Today, Microsoft announced that the update is a “recommended update” and is open to all Windows Insider users of the Beta channel. This means that Insiders who did not choose to install 21H1 before will now automatically receive 21H1 updates in the Beta channel.

Join Our RealMi Central Channel On Telegram

In Windows 10 21H1 Build 19043.844 (KB4601382), Microsoft provides multi-camera support for Windows Hello and improves the performance of Windows Defender Application Guard. Although 20H2 Build 19042.844 does not have the new features and improvements included in 21H1 Build 19043.844, the following bugs are fixed:

Fixed the memory leak problem in Internet Explorer 11. When you use the Chinese language pack, such a problem may occur.

  • Fixed the problem of deadlock in some applications caused by some COM+ calling strategies.
  • Fixed the problem that certain Win32 applications cannot be opened by different users when you use runas.
  • Fixed an issue where an unexpected screen was displayed during the Windows Out of Box Experience (OOBE).
  • Fixed the issue that may cause deadlock when the COM server transmits events in parallel to multiple subscribers.
  • Fixed an issue where the available refresh rate of high dynamic range (HDR) displays in the “Advanced Display Settings” was incorrect.
  • Fixed the problem that running certain CAD applications that rely on OpenGL may prevent these applications from opening.
  • Fixed an issue that may cause video playback to flicker when rendering on some low-latency displays.
  • Fixed the problem that sometimes the character string cannot be input in the input method editor (IME).
  • Fixed the resource exhaustion due to the leakage of handle and virtual memory in the Remote Desktop session due to Desktop Windows Manager (DWM).
  • Fixed the problem of stop errors that occurred during startup.
  • Fixed the issue that the deployment of Windows Hello for Business (WHfB) certificate trust may be delayed when opening the “Settings” -> “Accounts” -> “Login Options” page.
  • Fixed an issue that may sometimes prevent some keyboard keys from working, such as homepage, Ctrl, or left arrow key. This problem occurs when you set the Japanese IME input mode to Kana.
  • Deleted the historical records of previously used pictures in the user account profile.
  • Fixed the problem that the console display language was wrong after changing the system region.
  • Fixed an issue where the host process of Windows Remote Management (WinRM) stopped working when formatting messages from the PowerShell plug-in.
  • Fixed an issue in the Windows Management Instrumentation (WMI) service that would cause a heap leak every time security settings are applied to WMI namespace permissions.
  • Fixed the problem of screen rendering after opening the game under certain hardware configurations.
  • Improved the startup time of applications with roaming settings when user experience virtualization (UE-V) is turned on.
  • Fixed an issue where a principal in the trusted MIT realm could not obtain a Kerberos service ticket from an Active Directory domain controller (DC). This happens on devices that have installed a Windows update that includes CVE-2020-17049 protection measures and configured PerfromTicketSignature to 1 or higher. These updates were released between November 10, 2020 and December 8, 2020. If the caller submits a PAC-free ticket-granting ticket (TGT) as an evidence ticket without providing the USER_NO_AUTH_DATA_REQUIRED flag, the ticket acquisition will also fail with an error, that is, “KRB_GENERIC_ERROR”.
  • Fixed high memory and CPU utilization in Microsoft Defender for Endpoint.
  • Enhanced data loss prevention and internal personnel risk management solutions in Microsoft 365 endpoints.
  • Fixed the issue of external cameras that support Windows Hello. By default, when the internal Windows Hello camera is present, Windows Hello will now use the external camera.
  • Fixed an issue where when you try to open an untrusted webpage or open an untrusted Microsoft Office document using Microsoft Edge , an error will be displayed. The error is: “WDAG Report-Container. Error. 0x80070003, Ext error. 0x00000001”. This problem occurred after installing the .NET update KB4565627.
  • Fixed an issue that prevented wevtutil from parsing XML files.
  • Fixed an issue where an error cannot be reported when the elliptic curve digital signature algorithm (ECDSA) generates an invalid key of 163 bytes instead of 165 bytes.
  • Added support for using the new Chromium-based Microsoft Edge as the designated access single kiosk. Now, you can also customize a breakpoint key sequence for a single kiosk. For more information, see Configure Microsoft Edge kiosk mode.
  • Fixed the problem that User Datagram Protocol (UDP) broadcast packets are larger than the maximum transmission unit (MTU). The device receiving these packets will discard them because the checksum is invalid.
  • Fixed the problem that the WinHTTP automatic proxy service does not meet the maximum time to live (TTL) setting value on the proxy automatic configuration (PAC) file. This makes the cache file unable to be dynamically updated.
  • Improved the ability of the WinHTTP Web Proxy Auto-discovery service to ignore invalid Web Proxy Auto-discovery Protocol (WPAD) URLs returned by the Dynamic Host Configuration Protocol (DHCP) server.
  • Display the correct envelope media type as the selectable output paper type for the universal print queue. When the printer uses the Microsoft Internet Printing Protocol (IPP) class driver, the display of random paper size ends.
  • Enable Windows to retrieve updated printer features to ensure that users have the correct set of selectable printing options.
  • Updated the support for hole punching and stapler position for print jobs with long-edge first-feed direction on some printers.
  • Fixed an issue that may cause the IKEEXT service to stop working intermittently.
  • Fixed an issue that may prevent non-volatile memory Express (NVMe) devices from entering the correct power state.
  • Fixed the problem that stop error 7E may appear in sys on servers running Network File System (NFS) services.
  • Fixed an issue where the user profile service could not reliably detect slow or fast links.
  • Fixed an issue that caused contention for metadata locks when using working folders.
  • A new dfslogkey has been added, as described below.


The RootShareAcquireSuccessEvent field has the following possible values.

Default value=1; log is enabled.

Value is less than 1; log is disabled.

If this key does not exist, it will be created automatically. In order to take effect, any changes to dfslog/RootShareAcquireSuccessEvent in the registry require you to restart the DFSN service.

  • Updated the Open Mobile Alliance (OMA) Device Management (DM) synchronization protocol, and added a sign-in reason for requests from the client to the server. The sign-in reason will allow the mobile device management (MDM) service to make better decisions about the synchronization session. With this change, the OMA-DM service must negotiate the 4.0 protocol version with the Windows OMA-DM client.
  • Token binding is turned off by default in Windows Internet (WinINet).
  • Fixed an issue that the correct Kuri Kana characters may not be displayed in applications that automatically allow the input of Kuri Kana characters. You may need to manually enter the ancient kana characters. This problem occurs when using the Microsoft Japanese Input Method Editor (IME) to input Chinese characters in these applications.

If you like our news and you want to see such news even further, then follow RealMi Central on Telegram, Twitter, Facebook (Page) (Group) & Instagram.

Leave a Comment