March 22, 2022—KB5011543 (OS Builds 19042.1620, 19043.1620, and 19044.1620) Preview

This non-security update includes quality improvements. Key changes include:

• This build includes all the improvements from Windows 10, version 20H2.

• No additional issues were documented for this release. 

This non-security update includes quality improvements. Key changes include:

• This build includes all the improvements from Windows 10, version 20H2.

• No additional issues were documented for this release.

This non-security update includes quality improvements. Key changes include:

• New! Introducing search highlights

  Search highlights will present notable and interesting moments of what’s special about each day—like holidays, anniversaries, and other educational moments in time both globally and in your region. To see more details at a glance, hover, click, or tap on the illustration in the search box.

  For enterprise customers, search highlights will also feature the latest updates from your organization and suggest people, files, and more.

  Search highlights will roll out to Windows 10 customers over the next several weeks. We are taking a phased and measured approach. Broad availability will occur in the coming months. For more information, see Group configuration: search highlights in Windows.

• New! Provides the ability to change the color of toast buttons to identify success and critical scenarios more easily for apps that send notifications using Windows notifications in the OS. This feature also makes notifications more visually compact.

• New! Adds a new policy that expands an app’s top three notifications by default in the Action Center for apps that send notifications using Windows notifications in the OS. This feature displays multiple notifications that you can interact with simultaneously.

• Addresses an issue that causes searchindexer.exe to stop responding during a dismount operation in the Remote Desktop setup environment.

• Addresses an issue that affects searchindexer.exe and prevents Microsoft Outlook’s offline search from returning recent emails.

• Addresses an issue that might deactivate Windows when you change the National Language Support (NLS) version from 6.3 to 6.2.

• Addresses an issue in which modern browsers fail to correctly render HTML that is generated by gpresult/h.

• Addresses an issue that causes an “Access denied” exception for a file during a PowerShell test for AppLocker.

• Addresses an issue that might cause the Group Policy Service to stop processing telemetry information for Group Policy Registry Preferences.

• Addresses an issue that might prevent a DNS Server query resolution policy from working as expected when you specify a fully qualified domain name (FQDN) and subnet conditions.

• Addresses a heap leak in PacRequestorEnforcement that degrades the performance of a domain controller.

• Addresses an issue that affects the Key Distribution Center (KDC) Proxy. The KDC Proxy cannot properly obtain Kerberos tickets for signing in to Key Trust Windows Hello for Business.

• Adds support for Microsoft Account (MSA) Pass-through scenarios in Azure Active Directory (AAD) Web Account Manager (WAM).

• Addresses an issue that logs Event ID 37 during certain password change scenarios, including failover cluster name object (CNO) or virtual computer object (VCO) password changes.

• Addresses an issue that might unintentionally add a Trusted Platform Module (TPM) protector when you use the Silent BitLocker enablement policy.

• Addresses an issue that prevents the User Account Control (UAC) dialog from correctly showing the application that is requesting elevated privileges.

• Addresses an issue that causes the Move-ADObject command to fail when you move computer accounts across domains. The error message is, “Multiple values were specified for an attribute that can have only one value”.

• Addresses an issue that prevents Event 4739 from displaying the new values of certain attributes after a policy change.

• Addresses an issue that prevents Android device users from signing in to some Microsoft applications, such as Microsoft Outlook or Microsoft Teams. This issue occurs after rolling over token signing and decrypting certificates, resetting a user's password, or when an administrator has revoked refresh tokens.

• Addresses an issue that might cause domain joining to fail in environments that use disjoint DNS hostnames.

• Addresses an issue that prevents the Back button of the credentials window, where you sign in, from being visible in high contrast black mode.

• Addresses an issue that prevents you from accessing Server Message Block (SMB) shares using an IP Address when SMB hardening is enabled.

• Addresses an issue that occurs when the Best Practices Analyzer (BPA) values for SMB have not been updated for more recent platforms.

• Addresses an issue that causes stop error 0x1E in the SMB Server (srv2.sys).

• Addresses an issue that causes a mismatch between NetBIOS and DNS Active Directory domain names when you create a cluster.

• Addresses an issue that causes the Network File System (NFS) redirector to stop working (error 0x50) when you convert a text file to a PDF.

• Addresses a known issue that might cause some devices to receive error messages on a blue screen when those devices are paired to Bluetooth devices. This issue occurs when certain configuration service provider (CSP) policies are in place that affect the Bluetooth A2dp profile.

If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.

Symptoms	Workaround
Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps.	To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU: Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path> Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path> You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.
After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING".	For more information and a workaround, see KB5005322.
After installing the Windows updates released January 11, 2022 or later Windows versions on an affected version of Windows, recovery discs (CD or DVD) created by using the Backup and Restore (Windows 7) app in Control Panel might be unable to start. Recovery discs that were created by using the Backup and Restore (Windows 7) app on devices which have installed Windows updates released before January 11, 2022 are not affected by this issue and should start as expected. Note No third-party backup or recovery apps are currently known to be affected by this issue	This issue is addressed in KB5014023.
After installing this update, some apps might render content incorrectly or outside of the app's window. Affected apps are using WebView2 to render content generated locally or downloaded from the internet.	This issue is addressed using a Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the KIR to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the KIR to apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, you can address it by installing and configuring a special Group Policy listed below. Important Verify that you are using the correct Group Policy for your version of Windows. Group Policy downloads with Group Policy name: Download for Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 - KB5011543 Issue 001 Rollback Important You must install and configure the Group Policies specific to your version of Windows to address this issue. To configure the special Group Policy, use the following steps: If the KIR Group Policy has not been installed, install it from the link above. Open Group Policy Editor, navigate to either Local Computer Policy or the Domain policy on your domain controller then: Administrative Templates -> <Name as listed above>, then select the version of Windows you want to use this group policy on.  Note You might need to select the Windows 10 version that use the same update as a version of Server you are using. For example, you might need to select Windows 10, version 1809 if you are using Windows Server 2019. Set it to, "Disabled". If you are setting this on a domain controller, you must wait for the Group Policy to replicate group policy changes in Active Directory and the SYSVOL. Devices that apply a KIR GP in a local or domain policy must either apply a background or manual group policy refresh. Restart the affected device. Note You should not need to restart the domain controller after installing this KIR Group Policy. Allow the Group Policy to refresh on affected devices before installing the affected Windows update. For information on deploying and configuring these special Group Policies, see How to use Group Policy to deploy a Known Issue Rollback.
We are receiving reports that the Snip & Sketch app might fail to capture a screenshot and might fail to open using the keyboard shortcut (Windows key+shift+S). This issue occurs after installing KB5010342 (February 8, 2022) and later updates.	This issue is addressed in KB5014666.
Universal Windows Platform (UWP) apps might not open on devices that have undergone a Windows device reset. This includes operations that were initiated using Mobile Device Management (MDM), such as Reset this PC, Push-button reset, and Autopilot Reset. UWP apps you downloaded from the Microsoft Store are not affected. Only a limited set of apps are affected, including: App packages with framework dependencies Apps that are provisioned for the device, not per user account. The affected apps will fail to open without error messages or other observable symptoms. They must be re-installed to restore functionality.	This issue is addressed in KB5015878 for all releases starting June 21, 2021 and later.