Windows Insider Beta Channel Builds for 20H2 (Slow Ring)

Windows Insider Build 19042.789 (20H2) Released to Beta and Release Preview Channels: Releasing Windows 10 Build 19042.789 (20H2) to Beta and Release Preview Channels | Windows Insider Blog.

This update includes all the fixes in 20H2 Build 19042.782 plus the following additional fixes:
  • We fixed an issue with Microsoft Exchange accounts and some Surface Hub devices that occurs after updating to Windows 10, version 20H2. The message, “Something went wrong” appears, and the error code is 0x80131500.
  • We fixed an issue with Windows Update scans that occurs when an authenticated proxy is used as a fallback for the sync service after the previous proxy setting fails.
  • We fixed an issue that causes an update from Windows 10, version 1703 to Windows 10, version 20H2 to fail on a Surface Hub device. The message “Getting ready…” remains on the screen indefinitely.
 
Windows Insider Build 19042.804 (20H2) Released to Beta and Release Preview Channels: Releasing Windows 10 Build 19042.804 (20H2) to Beta and Release Preview Channels | Windows Insider Blog.

This security update includes quality improvements and the following key changes:
  • We fixed a possible elevation of privilege vulnerability in the win32k component.
  • We fixed an issue that might damage the file system of some devices and prevent them from starting up after running chkdsk /f.
  • We fixed a security vulnerability by preventing applications that run as a SYSTEM account from printing to “FILE:” ports. To address this issue in the future, make sure your applications or services run as a specific user or service account.
  • Security updates to the Windows App Platform and Frameworks, Windows Apps, Windows Input and Composition, Windows Cloud Infrastructure, Windows Management, Windows Authentication, Windows Fundamentals, Windows Cryptography, Windows Virtualization, Windows Core Networking, and Windows Hybrid Cloud Networking.
For more information about the resolved security vulnerabilities, please refer to the new Security Update Guide website.
 
Windows Insider Build 20H2 Build 19042.844 (KB4601382) Released to the Beta Release Preview Channels and Windows 10 Insider Preview Build 19043.844 (21H1) Releasing Windows 10 Build 19042.844 (20H2) to Beta and Release Preview Channels | Windows Insider Blog. See the blog post for the very long list of fixes and improvements.

and

Windows 10 Insider Preview Build 19043.844 (21H1) Released to Insiders in the Beta Channel only who are interested in moving up to 21H1: Announcing Windows 10 Insider Preview Build 19043.844 (21H1) | Windows Insider Blog.

This Build is being released to build to Insiders in the Beta Channel via the “seeker” experience in Windows Update. This means Insiders in the Beta Channel will need to go to Settings > Update & Security > Windows Update and choose to download and install 21H1. The Build includes all of the fixes and improvements of Build 19042.844, referenced above, as well as the new features referenced in Introducing the next feature update to Windows 10, version 21H1 | Windows Experience Blog.
 
Windows Inside Preview Build 21322 Released to Insiders on the Preview Channel: Announcing Windows 10 Insider Preview Build 21322 | Windows Insider Blog.

Fixes
  • We fixed an issue where if you tried to access an Azure Active Directory (AAD) joined device via Remote Desktop (RDP), it would fail after updating to recent Dev Channel builds.
  • We fixed an issue that could result in your PC bugchecking when switching between users.
  • We fixed an issue that could result in deleted files unexpectedly remaining visible on the desktop until the desktop was refreshed.
  • [News and interests] We fixed an issue where the taskbar button might show no content after the primary monitor was changed.
  • [News and interests] We fixed an issue where news and interests would continue to refresh content in the background even when the screen was turned off, consuming resources.
  • [News and interests] We fixed multiple issues impacting performance and reliability.
  • We fixed an issue with the new “Paste as plain text” option in clipboard history where clipboard history didn’t close after it was used, inconsistent with the normal paste behavior.
  • We fixed an issue that could result in erroneous torn write errors being logged.
  • We fixed an issue that could result in delayed audio playback on certain devices in the last few builds.
  • We fixed an issue where if you changed the calendar format multiple times under Settings > Date & Time > Region, the enumerated values of the other data formats may not be correct.
 
Update to Releasing Windows 10 Build 19042.844 (20H2) to Beta and Release Preview Channels | Windows Insider Blog:

Quote
UPDATE 3/2: 21H1 is now being offered as a recommended update to all Windows Insiders in the Beta Channel. Insiders who previously didn’t choose to install 21H1 will now automatically receive 21H1 in the Beta Channel.

Hello Windows Insiders, today we are announcing Windows 10 version 21H1 as the next feature update for Windows 10. As part of today’s announcement, we’re also releasing 21H1 Build 19043.844 (KB4601382) to the Beta Channel.

We are releasing this build to the Beta Channel via our “seeker” experience in Windows Update. This means Insiders in the Beta Channel will need to go to Settings > Update & Security > Windows Update and choose to download and install 21H1.
Click to expand...
 
Windows Insider Preview Build 19043-867 (21H1) Released to Insiders in the Beta Channel: Releasing Windows 10 Build 19043.867 (21H1) to Beta Channel | Windows Insider Blog.

This is a security update and quality improvement update with the following key changes:
  • We fixed an elevation of privilege security vulnerability documented in CVE-2021-1640 related to print jobs submitted to “FILE:” ports. After installing Windows updates from March 9, 2021 and later, print jobs that are in a pending state before restarting the print spooler service or restarting the OS will remain in an error state. Manually delete the affected print jobs and resubmit them to the print queue when the print spooler service is online.
  • Security updates to the Windows Shell, Windows Fundamentals, Windows Management, Windows Apps, Windows User Account Control (UAC), Windows Virtualization, Windows Kernel, the Microsoft Graphics Component, Internet Explorer, Microsoft Edge Legacy, and Windows Media.
 
Windows Insider Preview Build 19043.899 Released to the Beta Channel: Releasing Windows 10 Build 19043.899 (21H1) to Beta Channel | Windows Insider Blog.

The update includes the following long list of fixes:
  • We fixed an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
  • We enabled administrators to use a Group Policy to enable extended keyboard shortcuts, including Ctrl+S, for users in Microsoft Edge IE Mode.
  • We fixed an issue that prevents the icon for a Toast collection from appearing in the Action Center if the icon file’s URI contains spaces.
  • We fixed an issue that makes high dynamic range (HDR) screens appear much darker than expected.
  • We fixed an issue that causes video playback to be out of sync in duplicate mode when you use multiple monitors.
  • We fixed an issue that might cause applications to stop working while you type Japanese characters using the Microsoft Japanese Input Method Editor (IME) in compatibility mode.
  • We fixed an issue that might cause a device to stop responding during hybrid shutdown.
  • We fixed an issue that prevents users from adjusting or turning off the touchpad because of administrative settings.
  • We fixed a window rendering issue that causes content in a window to flash frequently when FlipEx is used.
  • We fixed a window rendering issue that causes content in a window to flash frequently when multi-plane overlay (MPO) is used.
  • We fixed an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge.
  • We fixed an issue that displays nothing or shows “Computing Filters” indefinitely when you filter File Explorer search results.
  • We fixed an issue that makes the split layout unavailable for the touch keyboard when you rotate a device to portrait mode.
  • We informed users when a child account in the Family Safety plan has administrative privileges.
  • We fixed an issue that prevents you from closing Toast Notifications using the Close button on touchscreen devices.
  • We fixed an issue with a heap leak that might cause explorer.exe to consume high amounts of memory.
  • We updated the Volgograd, Russia time zone from UTC+4 to UTC+3.
  • We added a new time zone, UTC+2:00 Juba, for the Republic of South Sudan.
  • We fixed an issue with the Windows Event Log Forwarding client, which returns the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client selects the client’s certificate only if the Network Service has read permissions for the private key.
  • We fixed an issue that causes PowerShell-based monitors to stop working when you enable transcription on the systems.
  • We fixed an issue that stops BranchCache from working if you activate Windows using Cloud Solution Provider (CSP) license.
  • We fixed an issue that prevents Windows 10 Home edition devices from upgrading to the Windows 10 Pro Education edition using mobile device management (MDM) services such as Microsoft Intune.
  • We fixed an issue that prevents App-V applications from opening and generates error 0xc0000225.
  • We 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.
  • We fixed an issue with using a configuration service provider (CSP) policy to configure a custom setting for Audit Other Logon/Logoff events. The custom setting fails to take effect.
  • We fixed an issue that causes a system to stop working when no Trusted Platform Module (TPM) is present in the system. The error code in TpmTasks.dll!TrackTPMStateChanges is c0000005.
  • We 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.
  • We fixed an issue with credential roaming when Windows Hello for Business is enabled.
  • We fixed an issue that prevents performance monitoring tools from displaying logged data for single instance counter objects.
  • We fixed an issue that prevents the Chromium-based Microsoft Edge from working. This issue occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled inside the virtual environment.
  • We fixed an issue that might cause a black screen or delay signing in to Hybrid Azure Active Directory joined machines. Additionally, there is no access to login.microsoftonline.com.
  • We fixed an issue that causes the system to stop working and generates error code 0xC9.
  • We fixed an issue with 7.1 channel audio technology.
  • We fixed an issue that turns on Caps lock unexpectedly when using RemoteApp. 31259510
  • We enabled Windows to retrieve updated printer capabilities to ensure that users have the proper set of selectable print options.
  • We updated support for hole punch and stapling locations for print jobs with long edge first paper feed direction on certain printers.
  • We fixed an issue with high memory usage when performing XSLT transforms using MSXLM6.
  • We fixed an issue that might cause File Explorer and other applications to stop responding for several minutes. This issue occurs after a client reconnects to the corporate network and attempts to use mapped drives to access file shares on the corporate network.
  • We fixed an issue that prevents Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
  • We fixed an issue that might cause the cluster network interface to stop working for a short time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system might not detect that the NIC is working and the NIC remains in a failed status.
  • We fixed an issue with 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 cannot retrieve the default user profile from the trusted domain and uses the local default user profile instead.
  • We fixed an issue that causes a device to stop working if you delete files or folders that OneDrive syncs.
  • We fixed an issue that prevents Windows from activating Windows 10, version 2004 using the OA 3.0 key after installing KB4598291.
  • We fixed an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • We removed the Microsoft Edge Legacy desktop application that is out of support and installs the new Microsoft Edge. For more information, see New Microsoft Edge to replace Microsoft Edge Legacy with April’s Windows 10 Update Tuesday release.
  • We fixed an issue that prevents users from using the Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
  • We fixed an issue to allow our enterprise partners to work with the Microsoft Support program to create customized mitigations.
  • We fixed an issue that might cause a blue screen when attempting to print to certain printers using some apps and might generate the error, APC_INDEX_MISMATCH.
  • We fixed an issue with an HTTP Keep-Alive connection in Azure Front Door. After 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 occur that closes the Transmission Control Protocol (TCP) connection. As a result, the client might fail with an invalid server response.
  • We fixed an issue that causes Remote Desktop sessions to end unexpectedly.
 
Windows Insider Build 19042.906 (21H1) Released to Insiders in the Beta Channel: Releasing Windows 10 Build 19043.906 (21H1) to Beta Channel | Windows Insider Blog.

This update includes all the fixes in 21H1 Build 19043.899 plus the following additional fix:
  • We fixed an issue that fails to print the graphical content in a document after installing the March 9, 2021 update.
In addition:

Windows Insider Build 19042.906 (20H2) Released to Insiders in the Release Preview Channel: Releasing Windows 10 Build 19042.906 (20H2) to Release Preview Channel | Windows Insider Blog.

The update includes a long list of fixes:
  • We fixed an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
  • We enabled administrators to use a Group Policy to enable extended keyboard shortcuts, including Ctrl+S, for users in Microsoft Edge IE Mode.
  • We fixed an issue that prevents the icon for a Toast collection from appearing in the Action Center if the icon file’s URI contains spaces.
  • We fixed an issue that makes high dynamic range(HDR) screens appear much darker than expected.
  • We fixed an issue that causes video playback to be out of sync in duplicate mode when you use multiple monitors.
  • We fixed an issue that might cause applications to stop working while you type Japanese characters using the Microsoft Japanese Input Method Editor (IME) in compatibility mode.
  • We fixed an issue that might cause a device to stop responding during hybrid shutdown.
  • We fixed an issue that prevents users from adjusting or turning off the touchpad because of administrative settings.
  • We fixed a window rendering issue that causes content in a window to flash frequently when FlipEx is used.
  • We fixed a window rendering issue that causes content in a window to flash frequently when multi-plane overlay (MPO) is used.
  • We fixed an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge Legacy.
  • We fixed an issue that displays nothing or shows “Computing Filters” indefinitely when you filter File Explorer search results.
  • We fixed an issue that makes the split layout unavailable for the touch keyboard when you rotate a device to portrait mode.
  • We informed users when a child account in the Family Safety plan has administrative privileges.
  • We fixed an issue that prevents you from closing Toast Notifications using the Close button on touchscreen devices.
  • We fixed an issue with a heap leak that might cause explorer.exe to consume high amounts of memory.
  • We updated the Volgograd, Russia time zone from UTC+4 to UTC+3.
  • We added a new time zone, UTC+2:00 Juba, for the Republic of South Sudan.
  • We fixed an issue with the Windows Event Log Forwarding client, which returns the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client selects the client’s certificate only if the Network Service has read permissions for the private key.
  • We fixed an issue that causes PowerShell-based monitors to stop working when you enable transcription on the systems.
  • We fixed an issue that stops BranchCache from working if you activate Windows using Cloud Solution Provider (CSP) license.
  • We fixed an issue that prevents Windows 10 Home edition devices from upgrading to the Windows 10 Pro Education edition using mobile device management (MDM) services such as Microsoft Intune.
  • We fixed an issue that prevents App-V applications from opening and generates error 0xc0000225.
  • We 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.
  • We fixed an issue with using a configuration service provider (CSP) policy to configure a custom setting for Audit Other Logon/Logoff events. The custom setting fails to take effect.
  • We fixed an issue that causes a system to stop working when no Trusted Platform Module (TPM) is present in the system. The error code in TpmTasks.dll!TrackTPMStateChanges is c0000005.
  • We fixed an issue that causes multiple instances of appidcertstorecheck.exe to run on a system when AppLocker is enabled and the system is not on the internet.
  • We fixed an issue with credential roaming when Windows Hello for Business is enabled.
  • We fixed an issue that prevents performance monitoring tools from displaying logged data for single instance counter objects.
  • We fixed an issue that prevents the Chromium-based Microsoft Edge from working. This issue occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled inside the virtual environment.
  • We fixed an issue that might cause a black screen or delay signing in to Hybrid Azure Active Directory joined machines. Additionally, there is no access to login.microsoftonline.com.
  • We fixed an issue that causes the system to stop working and generates error code 0xC9.
  • We fixed an issue with 7.1 channel audio technology.
  • We fixed an issue that turns on Caps lock unexpectedly when using RemoteApp. 31259510
  • We enabled Windows to retrieve updated printer capabilities to ensure that users have the proper set of selectable print options.
  • We updated support for hole punch and stapling locations for print jobs with long edge first paper feed direction on certain printers.
  • We fixed an issue with high memory usage when performing XSLT transforms using MSXLM6.
  • We fixed an issue that might cause File Explorer and other applications to stop responding for several minutes. This issue occurs after a client reconnects to the corporate network and attempts to use mapped drives to access file shares on the corporate network.
  • We fixed an issue that prevents Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
  • We fixed an issue that might cause the cluster network interface to stop working for a short time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system might not detect that the NIC is working and the NIC remains in a failed status.
  • We fixed an issue with 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 cannot retrieve the default user profile from the trusted domain and uses the local default user profile instead.
  • We fixed an issue that causes a device to stop working if you delete files or folders that OneDrive syncs.
  • We fixed an issue that prevents Windows from activating Windows 10, version 2004 using the OA 3.0 key after installing KB4598291.
  • We fixed an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • We removed the Microsoft Edge Legacy desktop application that is out of support and installs the new Microsoft Edge. For more information, see New Microsoft Edge to replace Microsoft Edge Legacy with April’s Windows 10 Update Tuesday release.
  • We fixed an issue that prevents users from using the Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
  • We fixed an issue to allow our enterprise partners to work with the Microsoft Support program to create customized mitigations.
  • We fixed an issue that causes Remote Desktop sessions to end unexpectedly.
  • We fixed an issue with an HTTP Keep-Alive connection in Azure Front Door. After 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 occur that closes the Transmission Control Protocol (TCP) connection. As a result, the client might fail with an invalid server response.
  • We fixed an issue that might cause a blue screen when attempting to print to certain printers using some apps and might generate the error, APC_INDEX_MISMATCH.
  • We fixed an issue that fails to print the graphical content in a document after installing the March 9, 2021 update.
 
Last edited:
Windows Insider Build 19043-928 (20H1) Released to both Beta and Release Preview Channels: Releasing Windows 10 Build 19043.928 (21H1) to Beta & Release Preview Channels | Windows Insider Blog.

This security update includes quality improvements. Key changes include:
  • We fixed an issue in which a principal in a trusted MIT realm fails to obtain a Kerberos service ticket from Active Directory domain controllers (DC). This occurs on devices that installed Windows Updates that contain CVE-2020-17049 protections and configured PerfromTicketSignature to 1 or higher. These updates were released between November 10, 2020 and December 8, 2020. Ticket acquisition also fails with the error, “KRB_GENERIC_ERROR”, if callers submit a PAC-less Ticket Granting Ticket (TGT) as an evidence ticket without providing the USER_NO_AUTH_DATA_REQUIRED flag.
  • We fixed an issue with security vulnerabilities identified by a security researcher. Because of these security vulnerabilities, this and all future Windows updates will no longer contain the RemoteFX vGPU. For more information about the vulnerability and its removal, see CVE-2020-1036 and KB4570006. Secure vGPU alternatives are available using Discrete Device Assignment (DDA) in Windows Server LTSC releases (Windows Server 2016 and Windows Server 2019) and Windows Server SAC releases (Windows Server, version 1803 and later versions).
  • We fixed a potential elevation of privilege vulnerability in the way Azure Active Directory web sign-in allows arbitrary browsing from the third-party endpoints used for federated authentication. For more information, see CVE-2021-27092 and Policy CSP – Authentication.
  • Security updates to Windows App Platform and Frameworks, Windows Apps, Windows Input and Composition, Windows Office Media, Windows Fundamentals, Windows Cryptography, the Windows AI Platform, Windows Kernel, Windows Virtualization, Internet Explorer, and Windows Media.
  • We have resolved an issue where some Insiders were getting an 0x800f081f error when attempting to install an early version of KB5000842. If you continue to hit an issue with the final version of KB5000842 update, let us know via Feedback Hub.
 
Windows Insider build 19043.962.21 (21H1) Released to Insiders on the Beta and Release Preview Channels: Releasing Windows 10 Build 19043.962 (21H1) to Beta Channel & Release Preview Channels | Windows Insider Blog.

Fixes and Improvements:
  • We fixed an issue that prevents a site from transitioning out of Microsoft Edge IE Mode when expected.
  • We fixed an issue that fails to remove mandatory profiles completely when you sign out when using the “Delete cached copies of roaming profiles” Group Policy.
  • We fixed an issue that causes blank tiles to appear on the Start menu with names such as “ms-resource:AppName” or “ms-resource:appDisplayName”. These blank tiles represent the installed applications and appear for approximately 15 minutes after updating to a newer version of Windows 10. Installing this update prevents these blank tiles from appearing on the Start menu.
  • We fixed an issue with the Microsoft Japanese Input Method Editor (IME) that prevents an app’s custom candidate window from displaying correctly.
  • We are rolling out news and interests on the Windows taskbar to Beta and Release Preview rings. This has been available in the Dev Channel, with on-going improvements based on Insider feedback. News and interests on the taskbar make it easy to stay up to date with information at a glance, and we look forward to hearing what you think.
  • We fixed an issue that occurs when you install inventory applications.
  • We fixed an issue that includes kernel mode rules for .NET applications in Windows Defender Application Control policies. As a result, the generated policies are significantly larger than necessary.
  • We fixed an issue that causes devices to fail Device Health Attestation.
  • We fixed an issue that turns off S Mode when you enable System Guard Secure Launch on a system running Windows 10 in S Mode.
  • We fixed an issue that causes lsass.exe memory usage to grow until the system becomes unusable. This occurs when Transport Layer Security (TLS) resumes a session.
  • We fixed an issue with a race condition between Task Scheduler and the Workstation Service. As a result, users cannot automatically join a hybrid Azure Active Directory (AAD) domain and error 0x80070490 is generated.
  • We fixed an issue that causes Azure Active Directory authentication to fail after signing in on Windows Virtual Desktop machines.
  • We fixed an issue that causes AAD Work Accounts to unexpectedly disappear from certain apps such Microsoft Teams or Microsoft Office.
  • We fixed an issue with a partial Service Connection Point (SCP) configuration that causes dsregcmd.exe to stop working. This issue occurs because of a case-sensitive domain ID name comparison that occurs when joining a hybrid Azure Active Directory domain using single sign-on (SSO).
  • We fixed an issue that accidently triggers hybrid AAD joining when the Group Policy “Register domain-joined computers as devices” is set to DISABLED. For more information, see Post configuration tasks for Hybrid Azure AD join.
  • We added the ability to adjust the amount of idle time before a headset goes to sleep in the Settings app for Windows Mixed Reality.
  • We fixed an issue that might generate a stop error when Docker containers run with process isolation.
  • We fixed an issue that causes automatic enrollment and certificate retrieval to fail with the error, “The parameter is incorrect.”
  • We fixed an issue that might cause Microsoft Defender Application Guard virtual machines to stop responding when Microsoft Defender Application Guard for Office opens a document. This issue might occur on some devices or in drivers that utilize GPU Hardware Accelerated Scheduling.
  • We fixed an issue that prevents some media players from playing content on hybrid devices that are running with dGPU on iGPU displays.
  • We fixed an issue with race conditions that cause high CPU usage. As a result, the system stops working and deadlocks occur.
  • We fixed an issue with a deadlock in the New Technology File System (NTFS).
  • We fixed an issue that causes DWM.exe to stop working in some cases.
  • We fixed an issue that might prevent an application screen from working when using a Remote Desktop ActiveX control that is embedded in an HTML page.
  • We improved the Windows Server Storage Migration Service by:
    • Adding support for migration from NetApp FAS arrays to Windows Servers and clusters.
    • Resolving multiple issues and improving reliability.
    • For more information, see Storage Migration Service overview.
 
Last edited:
Windows 10 Build 19043.964 (21H1) Released to Beta & Release Preview Channels: Releasing Windows 10 Build 19042.962 (20H2) to Release Preview Channel | Windows Insider Blog.

Important: See the blog post here on preparing the Windows 10 May 2021 Update (21H1) for release.

This update includes all the fixes in 21H1 Build 19043.962 plus the following additional fix:

This update includes the following improvements:
  • We fixed an issue causing a 0xC2 (BAD_POOL_CALLER) bugcheck when using IOCTL_SCSI_PASS_THROUGH_DIRECT.
 
Last edited:
Windows Insider Bu8ild 19043.985 (21h1) Released to Insiders in the Beta and Preview Channels: Releasing Windows 10 Build 19043.985 (21H1) to Beta & Release Preview Channels.

This security update includes quality improvements. Key changes include:
  • Security updates to Windows App Platform and Frameworks, the Windows Kernel, Windows Media, the Microsoft Scripting Engine, and the Windows Silicon Platform.
 
Windows Insider Build 19043.1023 (21H1) Released to Insiders in the Beta and Release Preview Channels: Releasing Windows 10 Build 19043.1023 (21H1) to Beta & Release Preview Channels.

Fixes:
  • We fixed an issue with the just-in-time (JIT) behavior of jscript9.dll.
  • We fixed an issue that might prevent users from opening phone apps that are pinned to the taskbar. This issue occurs after they update to Windows 10, version 2004 and then use the Your Phone app.
  • We fixed an issue that prevents certain Win32 apps from opening when using the runas command.
  • We fixed an issue that prevents certain Win32 apps from opening when the “BlockNonAdminUserInstall” Group Policy is turned on.
  • We fixed an issue that displays progressive web application (PWA) icons as blank when you pin them to the taskbar.
  • We fixed an issue that fails to properly manage memory for touch input before a session ends.
  • We fixed a memory leak in ctfmon.exe that occurs when you refresh an application that has an editable box.
  • We fixed an issue that prevents a touch device from working as a serial mouse in multiple monitor situations.
  • We fixed an issue that unexpectedly displays the Settings page text “Let’s finish setting up your device” at startup.
  • We fixed an issue that might display items on the desktop after you have deleted them from the desktop.
  • We fixed an issue that prevents users from viewing the Mouse settings page after the Settings Page Visibility Group Policy is set to “showonly:easeofaccess-mousepointer”.
  • We fixed an issue in Safe Mode that prevents users from signing in if Web Sign-in is enabled.
  • We fixed an issue in Active Directory (AD) Admin Center that displays an error when it lists many organizational units (OU)or container objects and PowerShell Transcription is enabled. The error message is, “Collection was modified after the enumerator was instantiated”.
  • We fixed an issue that causes Screen Readers to report the wrong UI information. This issue occurs because UI Automation reports inaccurate property information for some controls, such as IsDialog and IsControl.
  • We fixed an issue that fails to apply BitLocker encryption automatically using a Group Policy. This issue occurs on external drives that have a master boot record (MBR) active boot partition.
  • We fixed a memory leak issue in PKU2U that causes cluster nodes to run out of memory.
  • We fixed an issue with the Autopilot Reset command taking too long to process after it has been sent.
  • We fixed an issue that might prevent the Windows Dynamic Host Configuration Protocol (DHCP) Server from offering a lease to a DHCPv6 client after the client moves to a different virtual LAN (VLAN).
  • We fixed an issue that prevents a task from working correctly when you set the condition “Start only if the following network connection is available” for the task.
  • We fixed an issue that might display the “Device Removed” error when Direct3D developers use the SetStablePowerState() API in Windows Developer Mode.
  • We fixed an error that might cause video playback to fail when you switch from an external high-dynamic-range (HDR) display to a built-in non-HDR display.
  • We fixed an issue that fails to apply the spatial audio effect to sounds when you enable spatial audio.
  • We fixed an issue with noise when you enable spatial audio and use Bluetooth USB headphones.
  • We fixed a metadata encoding issue that causes Free Lossless Audio Codec (FLAC) music files to become unplayable if you change their title, artist, or other metadata.
  • We added support for the .hif file extension for High Efficiency Image File (HEIF) images.
  • We fixed an issue that might cause a system to stop working when using Remote Desktop for USB redirection of an Xbox One controller.
  • We fixed an issue that might cause a RemoteApp window to flicker or move to another area of the screen when using touch or pen input.
  • We fixed an issue with the PerfMon API that might cause handle leaks, which slow performance.
  • We fixed an issue that might cause endless replication when you promote a new domain controller and the Active Directory Recycle Bin feature is enabled.
  • We fixed an issue that sporadically prevents the Resource Host Subsystem (RHS) from registering network name resources in the Domain Name System (DNS). As a result, Event ID 1196 appears.
  • We fixed an issue with devices that were configured using mobile device management (MDM) RestrictedGroups, LocalUsersAndGroups, or UserRights policies. These devices incorrectly continue to receive the policy after you use MDM to remove the configuration profile that has the policy. As a result, users of the affected devices might have incorrect group memberships and UserRights assignments or other symptoms. This issue occurs after installing Windows updates from October 29, 2020 and later.
  • We fixed an issue that prevents users from receiving geographic location information even when all the geolocation UI settings are enabled correctly, and the device contains a location sensor.
  • We fixed an issue that fails to register a DNS update to an A record and a PTR when Azure virtual machines update against corporate DNS zones.
  • We fixed a timing issue that might cause a RemoteApp to intermittently duplicate characters that were entered on the local keyboard or pasted from the Windows clipboard.
 
Windows Insider Build 19043.1052 Released to Insiders on the Beta and Release Preview Channels: Releasing Windows 10 Build 19043.1052 (21H1) to Beta & Release Preview Channels.

This security update includes quality improvements. Key changes include:

Security updates to the Microsoft Scripting Engine, Windows App Platform and Frameworks, Windows Input and Composition, Windows Management, Windows Cloud Infrastructure, Windows Authentication, Windows Fundamentals, Windows Virtualization, Windows Kernel, Windows HTML Platform and Windows Storage and Filesystems.
Click to expand...
 
There are two releases today. The first for Windows Insiders on the 20H2 Release.

Windows 10 Build 19042.1081 (20H2) to Release Preview Channel to Insiders on the Beta and Release Preview Channels: Releasing Windows 10 Build 19042.1081 (20H2) to Release Preview Channel

This update includes the following improvements:

  • We fixed an issue that causes blurry text on the news and interests button on the Windows taskbar for some display configurations.
  • We fixed an issue that causes communication between apps to stop working after you enable the “AppMgmt_COM_SearchForCLSID” policy.
  • We fixed a performance issue in the MultiByteToWideChar() function that occurs when it is used in a non-English locale.
  • We fixed an issue that prevents sorting from working properly when using multiple versions of National Language Support (NLS) sorting.
  • We fixed an issue in a small subset of users that have lower than expected performance in games after installing KB5000842 or later.
  • We fixed an issue that causes the Japanese Input Method Editor (IME) to suddenly stop working while you are typing.
  • We fixed an issue that causes WMIMigrationPlugin.dll to return an error when you attempt to migrate in offline mode.
  • We fixed an issue with the Set-RuleOption PowerShell command that fails to provide the option for the Windows Defender Application Control (WDAC) policy to treat files signed with an expired certificate as unsigned.
  • We fixed an issue that causes Windows to stop working when it uses AppLocker to validate a file that has multiple signatures. The error is 0x3B.
  • We fixed an issue that might cause BitLocker to go into recovery mode after updating the Trusted Platform Module (TPM) firmware. This occurs when the “Interactive logon: Machine account lockout Threshold” policy is set and there were incorrect password attempts.
  • We fixed an issue that causes Windows to generate many AppLocker or SmartLocker success events.
  • We fixed an issue with authenticating for a domain controller when Credential Guard and Remote Credential Guard are enabled.
  • We fixed an issue that prevents certain screen reader apps from running when Hypervisor-protected code integrity (HVCI) is enabled.
  • We fixed an issue in which signing in using a PIN fails. The error message is “Something happened and your PIN isn’t available. Click to set up your PIN again.”
  • We added Windows support for System Management Mode protections (firmware protection version 2.0) for certain processors that support Secure Launch.
  • We fixed an issue that, in certain cases, takes you out of the exclusive virtual reality (VR) app and back to Windows Mixed Reality Home when you press the Windows button on the controller. With this update, when you press the Windows button, the Windows Start menu appears. When you close the Start menu, you will go back to the exclusive VR app.
  • We improved the accuracy and efficiency of sensitive data analysis in the Microsoft 365 Endpoint data loss prevention (DLP) Classification Engine.
  • We fixed an issue with the Internet Key Exchange (IKE) VPN service on remote access server (RAS) servers. Periodically, users cannot connect a VPN to the server over the IKE protocol. This issue might start several hours or days after restarting the server or restarting the IKEEXT service. Some users can connect while many others cannot connect because the service is in DoS Protection mode, which limits incoming connection attempts.
  • We fixed an issue that causes Wi-Fi connections to fail because of an invalid Message Integrity Check (MIC) on a four-way handshake if Management Frame Protection (MFP) is enabled.
  • We fixed an issue that might cause a VPN to fail after renewing a user auto-enrolled certificate. The error message is “There are no more files”.
  • We fixed an issue with the Tunnel Extensible Authentication protocol (TEAP) that replaces the outer identity with “anonymous” even though identity privacy is not selected or is disabled.
  • We fixed an issue that causes Remote Desktop sessions to stop responding while the User Datagram Protocol (UDP) is enabled.
  • We added support for the USB Test and Measurement Class.
  • We fixed an issue in Adamsync.exe that affects the syncing of large Active Directory subtrees.
  • We fixed an error that occurs when the Lightweight Directory Access Protocol (LDAP) bind cache is full, and the LDAP client library receives a referral.
  • We fixed a redirector stop error that is caused by a race condition that occurs when the system deletes binding objects when connections close.
  • We fixed an issue that prevents users from setting or querying disk quotas on the C drive.
  • We fixed an issue that causes 16-bit apps that run on NT Virtual DOS Machine (NTVDM) to stop working when you open them.
  • We fixed an issue that causes fontdrvhost.exe to stop working when Compact Font Format version 2 (CFF2) fonts are installed.
  • We fixed an issue that might prevent End User Defined Characters (EUDC) from printing correctly because of font fallback settings.
  • We fixed an issue with Search box graphics on the Windows taskbar that occurs if you use the taskbar’s context menu to turn off News and interests. This graphics issue is especially visible when using dark mode.
  • We fixed an issue that might cause signing in with your fingerprint to fail after the system starts up or resumes from sleep.
  • We fixed an issue that might redirect you to the Microsoft Store page for Gaming Services when you try to install or start an Xbox Game Pass game on your Windows 10 device. Additionally, you receive error 0x80073D26 or 0x8007139F. For more information, see KB5004327.
 
The second release is to Windows Insiders on 21H1.

Windows 10 Build 19043.1081 (21H1) to Insiders on the Beta & Release Preview Channels: Releasing Windows 10 Build 19043.1081 (21H1) to Beta & Release Preview Channels.

See Preparing the Windows 10 May 2021 Update for Release:

This update includes the following improvements:

  • We fixed an issue that causes blurry text on the news and interests button on the Windows taskbar for some display configurations.
  • We fixed an issue that causes communication between apps to stop working after you enable the “AppMgmt_COM_SearchForCLSID” policy.
  • We fixed a performance issue in the MultiByteToWideChar() function that occurs when it is used in a non-English locale.
  • We fixed an issue that prevents sorting from working properly when using multiple versions of National Language Support (NLS) sorting.
  • We fixed an issue in a small subset of users that have lower than expected performance in games after installing KB5000842 or later.
  • We fixed an issue that causes the Japanese Input Method Editor (IME) to suddenly stop working while you are typing.
  • We fixed an issue that causes WMIMigrationPlugin.dll to return an error when you attempt to migrate in offline mode.
  • We fixed an issue with the Set-RuleOption PowerShell command that fails to provide the option for the Windows Defender Application Control (WDAC) policy to treat files signed with an expired certificate as unsigned.
  • We fixed an issue that causes Windows to stop working when it uses AppLocker to validate a file that has multiple signatures. The error is 0x3B.
  • We fixed an issue that might cause BitLocker to go into recovery mode after updating the Trusted Platform Module (TPM) firmware. This occurs when the “Interactive logon: Machine account lockout Threshold” policy is set and there were incorrect password attempts.
  • We fixed an issue that causes Windows to generate many AppLocker or SmartLocker success events.
  • We fixed an issue with authenticating for a domain controller when Credential Guard and Remote Credential Guard are enabled.
  • We fixed an issue that prevents certain screen reader apps from running when Hypervisor-protected code integrity (HVCI) is enabled.
  • We fixed an issue in which signing in using a PIN fails. The error message is “Something happened and your PIN isn’t available. Click to set up your PIN again.”
  • We added Windows support for System Management Mode protections (firmware protection version 2.0) for certain processors that support Secure Launch.
  • We fixed an issue that, in certain cases, takes you out of the exclusive virtual reality (VR) app and back to Windows Mixed Reality Home when you press the Windows button on the controller. With this update, when you press the Windows button, the Windows Start menu appears. When you close the Start menu, you will go back to the exclusive VR app.
  • We improved the accuracy and efficiency of sensitive data analysis in the Microsoft 365 Endpoint data loss prevention (DLP) Classification Engine.
  • We fixed an issue with the Internet Key Exchange (IKE) VPN service on remote access server (RAS) servers. Periodically, users cannot connect a VPN to the server over the IKE protocol. This issue might start several hours or days after restarting the server or restarting the IKEEXT service. Some users can connect while many others cannot connect because the service is in DoS Protection mode, which limits incoming connection attempts.
  • We fixed an issue that causes Wi-Fi connections to fail because of an invalid Message Integrity Check (MIC) on a four-way handshake if Management Frame Protection (MFP) is enabled.
  • We fixed an issue that might cause a VPN to fail after renewing a user auto-enrolled certificate. The error message is “There are no more files”.
  • We fixed an issue with the Tunnel Extensible Authentication protocol (TEAP) that replaces the outer identity with “anonymous” even though identity privacy is not selected or is disabled.
  • We fixed an issue that causes Remote Desktop sessions to stop responding while the User Datagram Protocol (UDP) is enabled.
  • We added support for the USB Test and Measurement Class.
  • We fixed an issue in Adamsync.exe that affects the syncing of large Active Directory subtrees.
  • We fixed an error that occurs when the Lightweight Directory Access Protocol (LDAP) bind cache is full, and the LDAP client library receives a referral.
  • We fixed a redirector stop error that is caused by a race condition that occurs when the system deletes binding objects when connections close.
  • We fixed an issue that prevents users from setting or querying disk quotas on the C drive.
  • We fixed an issue that causes 16-bit apps that run on NT Virtual DOS Machine (NTVDM) to stop working when you open them.
  • We fixed an issue that causes fontdrvhost.exe to stop working when Compact Font Format version 2 (CFF2) fonts are installed.
  • We fixed an issue that might prevent End User Defined Characters (EUDC) from printing correctly because of font fallback settings.
  • We fixed an issue with Search box graphics on the Windows taskbar that occurs if you use the taskbar’s context menu to turn off News and interests. This graphics issue is especially visible when using dark mode.
  • We fixed an issue that might cause signing in with your fingerprint to fail after the system starts up or resumes from sleep.
  • We fixed an issue that might redirect you to the Microsoft Store page for Gaming Services when you try to install or start an Xbox Game Pass game on your Windows 10 device. Additionally, you receive error 0x80073D26 or 0x8007139F. For more information, see KB5004327.
 
Due to the move to Windows 11 Insider Builds, unpinning this topic. If you are running Insider Builds, see the chart below to see how your device fits.


Modify message
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top