Windows 11

Microsoft releases Windows 10 Build 19043.1200 (21H1) to release a preview version of Channel Insiders

Microsoft today announced the use of Windows 10 Release Preview Channel Insiders of version 21H1 released Windows 10 Version 21H1 Build 19043.1202. This version contains a bug fix as follows:

  • Microsoft Fixed an issue that caused the Windows Update settings page to stop responding after downloading optional updates.

Windows 10 Build 19043.1202 also includes all the improvements listed as part of Build 19043.1200, as follows:

  • Microsoft fixed an issue that prevented users from tracking Distributed Component Object Model (DCOM) activation failures.
  • Microsoft fixed a threading issue that could cause the Windows Remote Management (WinRM) service to stop working under high load.
  • Microsoft fixed an issue that caused the Windows Management Instrumentation (WMI) provider host process to stop working. This is because an unhandled access violation occurred while using the required state configuration (DSC).
  • Microsoft fixed an issue that caused the migration of files between Distributed File System (DFS) paths stored on different volumes to fail.When you use useMove-Item This problem occurs when the PowerShell script of the command implements the migration.
  • Microsoft fixed an issue that prevented you from writing to the WMI repository after an out-of-memory condition.
  • Microsoft fixed an issue that resets the brightness of standard dynamic range (SDR) content on high dynamic range (HDR) displays. This will happen after you restart the system or reconnect to the system remotely.
  • Microsoft fixed an issue that could cause the external monitor to display a black screen after sleep. This issue may occur when an external monitor is connected to the docking station using a specific hardware interface.
  • Microsoft fixed theVBScriptMemory leak when using nested classes.
  • Microsoft fixed an issue that prevented you from typing any words in the username box during the out-of-the-box experience (OOBE). This problem occurs when you use the Chinese Input Method Editor (IME).
  • Microsoft fixed an issue that caused applications that used shims to stop working.This problem occurs when it is not installed edgegdi.dll On the device. The error message is “Code execution cannot continue because edgegdi.dll was not found”.
  • Microsoft has fixed an issue that may prevent you from minimizing applications that use non-themed windows.
  • Microsoft fixed an issue that could cause your device to stop working during touch input gestures. This issue occurs if you let more fingers touch the touchpad or screen in the middle of the gesture.
  • Microsoft has fixed an issue where resizing images may cause flickering and residual line artifacts.
  • Microsoft fixed the problem of copying and pasting text boxes into Office 365 applications. IME prevents you from inserting text in the text box.
  • Microsoft fixed an issue that prevented USB audio headsets from working on laptops that support USB audio offloading. This issue occurs if you have installed a third-party audio driver on your laptop.
  • Microsoft fixed an issue that prevented the code integrity rule from working properly when the package family name rule was specified in the code integrity policy. This problem occurs because of incorrect handling of case-sensitive names.
  • Microsoft fixed an issue that prevented the ShellHWDetection service from starting on a privileged access workstation (PAW) device and prevented you from managing BitLocker drive encryption.
  • Microsoft fixed an issue in Windows Defender Exploit Protection that prevented certain Microsoft Office applications from running on computers with specific processors.
  • Microsoft fixed an issue that caused the IME toolbar to appear even if the remote application was closed.
  • Microsoft has fixed a problem that may occur when configuring policies, “Delete user profiles older than the specified number of days when the system restarts.” If the user logs in for longer than the time specified in the policy, the device may accidentally delete the configuration file during startup.
  • Microsoft fixed an issue where the Microsoft OneDrive sync setting “Always stay on this device”. After installing Windows Update, the setting was unexpectedly reset to “Known Folders Only”.
  • Microsoft fixed an issue where the wrong kana result was provided when the user canceled the Japanese reconversion.
  • Microsoft fixed a rare situation that prevented Bluetooth headsets from using the Advanced Audio Distribution Profile (A2DP) for music playback and caused the headset to only be used for voice calls.
  • Microsoft added a “target product version” strategy. With this, administrators can specify which Windows products they want the device to migrate to or keep (for example,Windows 10 or Windows 11).
  • Microsoft has increased the default number of entries in the local security authority (LSA) lookup cache to improve lookup performance in high lookup scenarios.
  • Microsoft fixed an issue where duplicate built-in local accounts (such as administrator or guest accounts) might be created during an in-place upgrade. If you have previously renamed these accounts, this issue will occur. Therefore, the local user and group MMC snap-in ( msc ) Is blank and has no account after the upgrade. This update removes duplicate accounts from the local Security Accounts Manager (SAM) database on the affected computer. If the system detects and deletes duplicate accounts, it will record a Directory-Services-SAM event with ID 16986 in the system event log.
  • Microsoft fixedsrv2!Smb2CheckAndInvalidateCCFFileThe stop error 0x1E.
  • Microsoft fixed an issue that could cause transmission verification to fail with the error “HRESULT E_FAIL has 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 the source.
  • Microsoft fixed an issue that could cause the system to stop working after the deduplication filter detects a damaged reparse point. This issue occurs because of the deduplication driver changes introduced in the previous update.
  • Microsoft fixed the use of with backup options ( /B )of robocopyCommand to fix the problem of data loss. This issue occurs when the source location contains tiered Azure File Sync files or tiered cloud files.
  • Microsoft stopped running queries on the OneSettings API from the outdated storage health function.
  • Microsoft has enabled more than 1,400 new mobile device management (MDM) policies. Using them, you can configure policies that are also supported by Group Policy. These new MDM strategies include administrative template (ADMX) strategies such as App Compat, event forwarding, service, and task scheduler. Starting in September 2021, you can use the Microsoft Endpoint Manager (MEM) settings directory to configure these new MDM policies.

In the Release Preview channel Windows 10 Insiders can download updates by checking for updates in “Settings”.

Related Articles

Back to top button

Adblock Detected

Please consider supporting us by disabling your ad blocker