Microsoft today announced the release of Windows 10, version 21H1 Build 19043.1202 to the Release Preview Channel Insiders who are on Windows 10, version 21H1. This build includes one bug fix, which can be seen below:
- Microsoft fixed an issue that causes the Windows Update settings page to stop responding after you download an optional update.
Windows 10 Build 19043.1202 also includes all the improvements listed as part of Build 19043.1200 which can be seen below:
- Microsoft fixed an issue that prevents users from tracking Distributed Component Object Model (DCOM) activation failures.
- Microsoft fixed a threading issue that might cause the Windows Remote Management (WinRM) service to stop working when it is under a high load.
- Microsoft fixed an issue that causes the Windows Management Instrumentation (WMI) provider host process to stop working. This occurs because of an unhandled access violation that occurs when using the Desired State Configuration (DSC).
- Microsoft fixed an issue that causes file migration between Distributed File System (DFS) paths that are stored on different volumes to fail. This issue occurs when you implement the migration using PowerShell scripts that use the Move-Item command.
- Microsoft fixed an issue that prevents you from writing to a WMI repository after a low memory condition occurs.
- Microsoft fixed an issue that resets the brightness for standard dynamic range (SDR) content on high-dynamic range (HDR) monitors. This occurs after you restart the system or reconnect to the system remotely.
- Microsoft fixed an issue that might cause an external monitor to display a black screen after Hibernation. This issue might occur when the external monitor connects to a docking station using a certain hardware interface.
- Microsoft fixed a memory leak that occurs when you use nested classes within VBScript.
- Microsoft fixed an issue that prevents you from typing any words in the username box during the out-of-box experience (OOBE) process. This issue occurs when you use the Chinese Input Method Editor (IME).
- Microsoft fixed an issue that causes applications that use a shim to stop working. This issue occurs on devices that do not have edgegdi.dll installed. The error message is, “The code execution cannot proceed because edgegdi.dll was not found”.
- Microsoft fixed an issue that might prevent you from minimizing an application that uses unthemed windows.
- Microsoft fixed an issue that might cause your device to stop working during a touch input gesture. This issue occurs if you bring more fingers into contact with the touchpad or screen during the middle of the gesture.
- Microsoft fixed an issue with resizing images that might produce flickering and residual line artifacts.
- Microsoft fixed an issue with copying and pasting a text box into Office 365 apps. The IME prevents you from inserting text into the text box.
- Microsoft fixed an issue that prevents USB audio headsets from working on laptops that support USB audio offload. This issue occurs if you installed third-party audio drivers on the laptops.
- Microsoft fixed an issue that prevents Code Integrity rules from working correctly when specifying Package Family Name rules in a Code Integrity policy. This issue occurs because of the incorrect handling of case-sensitive names.
- Microsoft fixed an issue that prevents the ShellHWDetection service from starting on a Privileged Access Workstation (PAW) device and prevents you from managing BitLocker drive encryption.
- Microsoft fixed an issue in Windows Defender Exploit Protection that prevents some Microsoft Office applications from working on machines that have certain processors.
- Microsoft fixed an issue that causes the IME toolbar to appear even when the Remote App is closed.
- Microsoft fixed an issue that might occur when you configure the policy, “Delete user profiles older than a specified number of days on system restart”. If a user has been signed in for longer than the time specified in the policy, the device might unexpectedly delete profiles at startup.
- Microsoft fixed an issue with the Microsoft OneDrive sync setting “Always keep on this device”. The setting is unexpectedly reset to “Known folders only” after you install Windows updates.
- Microsoft fixed an issue that provides the wrong Furigana result when a user cancels the Japanese reconversion.
- Microsoft fixed a rare condition that prevents Bluetooth headsets from connecting using the Advanced Audio Distribution Profile (A2DP) for music playback and causes the headsets to only work for voice calls.
- Microsoft added the “Target Product Version” policy. With this, administrators can specify the Windows product they want devices to migrate to or remain on (for example, Windows 10 or Windows 11).
- Microsoft increased the default number of entries in the local security authority (LSA) Lookup Cache to improve lookup performance in high lookup volume scenarios.
- Microsoft fixed an issue that might create duplicate built-in local accounts, such as administrator or guest account, during an in-place upgrade. This issue occurs if you previously renamed those accounts. As a result, the Local Users and Groups MMC snap-in (msc) appears blank with no accounts after the upgrade. This update removes the duplicate accounts from the local Security Account Manager (SAM) database on the affected machines. If the system detected and removed duplicate accounts, it logs a Directory-Services-SAM event, with ID 16986, in the System event log.
- Microsoft fixed a stop error 0x1E in srv2!Smb2CheckAndInvalidateCCFFile.
- Microsoft fixed an issue that might cause transfer validations to fail with the error, “HRESULT E_FAIL has been returned from a call to a COM component”. This issue occurs when you use Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 as sources.
- Microsoft fixed an issue that might cause a system to stop working after a deduplication filter detects damage in a reparse point. This issue occurs because of deduplication driver changes introduced in a previous update.
- Microsoft fixed an issue with using the robocopy command with the backup option (/B) to fix data loss. This issue occurs when the source location contains tiered Azure File Sync files or tiered Cloud Files.
- Microsoft stopped running queries against OneSettings APIs from the obsolete Storage Health feature.
- Microsoft enabled over 1400 new mobile device management (MDM) policies. With them, you can configure policies that Group Policies also support. These new MDM policies include administrative template (ADMX) policies, such as App Compat, Event Forwarding, Servicing, and Task Scheduler. Starting in September 2021, you can use the Microsoft Endpoint Manager (MEM) Settings Catalog to configure these new MDM policies.
Windows 10 Insiders in the Release Preview channel can download the update by checking for updates in Settings.