KB5000842 Windows 10 Build 19043.899 21H1 Rolled out to Beta Channel

New update Windows 10 Build 19043.899 21H1 (KB5000842) rolled out to insiders in Beta Channel.

KB5000842 Windows 10 Build 19043.899 21H1

Beta channel Insiders have a long list of bug fixes to experience! Windows 10 21H1 has received an update KB5000842 increasing the version to Build 19043.899.

You can rush to Windows update Settings to install the new insider build and experience the fixes.

Windows 10 Build 19043.899 21H1 KB5000842

Here are the bug fixes –

  • The build fixed the zoom problem that occurs when using Microsoft Edge IE Mode on multiple high-DPI monitors.
  • Windows 10 version 21H1 19043.899 powered administrators to enable extended keyboard shortcuts, including Ctrl + S with the help of a Group Policy, for users in Microsoft Edge IE Mode.
  • The experts fixed icon for a Toast collection fails to appear in the Action Center if the icon file’s URI contains spaces.
  • They fixed HDR screens appearing much darker than expected.
  • Also, fixed video playback out of sync in duplicate mode when using multiple monitors.
  • They fixed applications stop working while typing Japanese characters using the Microsoft Japanese IME in compatibility mode.
  • KB5000842 fixed a device stops responding during hybrid shutdown.
  • Professionals fixed you cannot adjust or turn off the touchpad because of administrative settings.
  • They fixed a window rendering issue that causes content in a window to flash frequently when FlipEx is used.
  • Furthermore, they fixed a window rendering issue that causes content in a window to flash frequently when multi-plane overlay (MPO) is used.
  • The update fixed a problem with Japanese input that happens after focus changes between boxes in Microsoft Edge.
  • Next, the build fixed filter File Explorer search results display nothing or show Computing Filters indefinitely.
  • The experts there fixed an issue that makes the split layout unavailable for the touch keyboard when you rotate a device to portrait mode.
  • They informed users when a child account in the Family Safety plan has administrative privileges.
  • Also, they fixed you cannot close Toast Notifications using the Close button on touch screen devices.
  • They fixed heap leak that might cause exe to consume high amount of memory.
  • KB5000842 updated the Volgograd, Russia time zone from UTC+4 to UTC+3.
  • The rollout added a new time zone, UTC+2:00 Juba, for the Republic of South Sudan.
  • Windows 10 build 19043.899 fixed the Windows Event Log Forwarding client that returns the first matching certificate without checking private key permissions. Subsequent to installing this update, the client chooses the client’s certificate only if the Network Service has read permissions for the private key.
  • The rollout fixed PowerShell-based monitors that stop working when you enable transcription on the systems.
  • The update fixed BranchCache that stops working after activating Windows using Cloud Solution Provider (CSP) license.
  • The professionals fixed Windows 10 Home edition devices can not be upgraded to the Windows 10 Pro Education using mobile device management (MDM) services, for example, Microsoft Intune.
  • They fixed App-V applications that fail to open and generates error 0xc0000225.
  • They fixed an issue in which some machines enrolled with an MDM service fail to sync if the device manufacturer’s name contains a reserved character.
  • Furthermore, they fixed an issue with using a configuration service provider (CSP) policy to configure a custom setting for “Audit Other Logon/Logoff” events. During this issue, The custom setting fails to take effect.
  • They fixed system stops working when no Trusted Platform Module (TPM) is present in the system. The error code is shown in TpmTasks.dll!TrackTPMStateChanges during this situation is c0000005.
  • They fixed an issue that causes multiple instances of exe to run on a system when AppLocker is enabled and the system is not on the internet.
  • Also, they fixed an issue with credential roaming when Windows Hello for Business is enabled.
  • The currently rolled out build fixed an issue that prevents performance monitoring tools from displaying logged data for single instance counter objects.
  • Beta channel build fixed an issue that prevents Microsoft Edge from working. This problem occurs when the browser is used in combination with Microsoft App-V and fonts are enabled inside the virtual environment.
  • The rollout fixed an issue that might cause a black screen or delay signing in to Hybrid Azure Active Directory joined machines. Besides, there is no access to login.microsoftonline.com.
  • The rollout fixed an issue that causes the system to stop working and generates error code 0xC9.
  • Experts there fixed an issue with 7.1 channel audio technology.
  • They fixed an issue that turns on Caps lock unexpectedly when using RemoteApp.
  • Windows 10 v21H1 19043.899 for Beta enabled Windows to retrieve updated printer capabilities to make sure that users have the proper set of selectable print options.
  • The new version (19043.899) updated support for hole punch and stapling locations for print jobs with long edge first paper feed direction on certain printers.
  • Experts fixed high memory usage when performing XSLT transforms using MSXLM6.
  • They fixed File Explorer and other applications stop responding for several minutes. This issue takes place after a client reconnects to the corporate network and tries to use mapped drives to access file shares on the corporate network.
  • They fixed Server Message Block 1 (SMB1) clients fail to access the SMB share after restarting the LanmanServer service.
  • Also, they fixed the cluster network interface that stops working for a short period of time. Consequently, the network interface controller (NIC) is marked as failed. When the network is functional again, the system might not detect that the NIC is working and the NIC remains in a failed status.
  • They fixed signing in to a device that is in the current domain by using the default user profile of a device that is in a different, but trusted domain. The profile service of the current domain failed to retrieve the default user profile from the trusted domain and uses the local default user profile instead.
  • Current build fixed a device stops working problem when you delete files or folders that OneDrive syncs.
  • KB5000842 fixed Windows cannot activate Windows 10 v2004 using the OA 3.0 key after installing KB4598291.
  • The experts fixed an issue with evaluating the compatibility status of the Windows ecosystem to assist ensure application and device compatibility for all updates to Windows.
  • They removed the Microsoft Edge Legacy that is out of support and installed the new Microsoft Edge.
  • They fixed the Remote Desktop Protocol (RDP) fails to connect to a Windows Server 2019 device that is in Desktop Experience mode.
  • Also, they fixed an issue to allow our enterprise partners to work with the Microsoft Support program to create customized mitigations.
  • Windows 10 build 19043.899 fixed an issue that might cause a blue screen when printing to certain printers using some apps and might generate the error, APC_INDEX_MISMATCH.
  • The rollout fixed an issue with an HTTP Keep-Alive connection in Azure Front Door. Subsequent to completing a previous request and response to keep the connection open, Azure Front Door will try to reuse the connection. After an idle timeout, a race condition might happen that closes the TCP connection. As a result, the client might fail with an invalid server response.
  • Finally, KB5000842 fixed Remote Desktop sessions that end unexpectedly.

Source – Windows blog.

   
 
 
About Sunita
Love to play with Windows 10. Suggestion - Going for Registry change or system files edit then remember to take a backup or create a restore point before Starting.
Leave a Reply