June 2, 2022—KB5014023 (OS Builds 19042.1741, 19043.1741, and 19044.1741) 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! Introduces new sorting version 6.4.3, which addresses the sorting issue that affects Japanese half-width katakana.

• Prevents users from bypassing forced enrollment by disconnecting from the internet when they sign in to Azure Active Directory (AAD).

• Addresses an issue that might run an AnyCPU application as a 32-bit process.

• Addresses an issue that prevents Azure Desired State Configuration (DSC) scenarios that have multiple partial configurations from working as expected.

• Addresses an issue that affects remote procedure calls (RPC) to the Win32_User or Win32_Group WMI class. The domain member that runs the RPC contacts the primary domain controller (PDC). When multiple RPCs occur simultaneously on many domain members, this might overwhelm the PDC.

• Addresses an issue that occurs when adding a trusted user, group, or computer that has a one-way trust in place. The error message, “The object selected doesn't match the type of destination source” appears.

• Addresses an issue that fails to display the Application Counters section in the performance reports of the Performance Monitor tool.

• Addresses a rare issue that prevents Microsoft Excel or Microsoft Outlook from opening.

• Addresses a memory leak issue that affects Windows systems that are in use 24 hours each day of the week.

• Addresses an issue that affects the IE mode window frame.

• Addresses an issue that prevents internet shortcuts from updating.

• Addresses an issue that causes an Input Method Editor (IME) to discard a character if you enter the character while the IME is converting previous text.

• Addresses an issue that causes print failures when a low integrity level (LowIL) application prints to a null port.

• Addresses an issue that prevents BitLocker from encrypting when you use the silent encryption option.

• Addresses an issue that occurs when you apply multiple WDAC policies. Doing that might prevent scripts from running when the policies allow scripts to run.

• Addresses an issue that affects the behavior and shape orientation of a mouse cursor for Microsoft Defender Application Guard (MDAG), Microsoft Office, and Microsoft Edge. This issue occurs when you turn on a virtual graphics processing unit (GPU).

• Addresses an issue that might cause the Remote Desktop client application to stop working when you end a session.

• Addresses a reliability issue in the Terminal Services Gateway (TS Gateway) service that randomly causes clients to disconnect.

• Deploys search highlights to devices that are domain-joined. For more information about the feature, see Group configuration: search highlights in Windows. You can configure search highlights at the enterprise scale using Group Policy settings defined in the Search.admx file and Policy CSP - Search.

• Addresses an issue that displays the wrong image for the Input Method Editor (IME) mode indicator icon when you turn on the Font Mitigation policy. For more information, see Block untrusted fonts in an enterprise.

• Addresses an issue that causes a yellow exclamation point to display in Device Manager. This occurs when a Bluetooth remote device advertises the Advanced Audio Distribution Profile (A2DP) source (SRC).

• Addresses an issue in which the Cluster Windows Management Instrumentation (WMI) provider (ClustWMI.dll) generates high CPU usage in WMIPRVSE.EXE.

• Addresses an issue that causes Microsoft’s deduplication driver to consume large amounts of nonpaged pool memory. As a result, this depletes all the physical memory on the machine, which causes the server to stop responding.

• Addresses an issue that causes file copying to be slower because of a wrong calculation of write buffers within cache manager.

• Addresses an issue that might cause a system to stop responding when a user signs out if Microsoft OneDrive is in use.

• Addresses a known issue that might prevent recovery discs (CD or DVD) from starting if you created them using the Backup and Restore (Windows 7) app in Control Panel. This issue occurs after installing Windows updates released January 11, 2022 or later.

• Addresses a known issue that affects certain GPUs and might cause apps to close unexpectedly or cause intermittent issues that affect some apps that use Direct3D 9. You might also receive an error in the Event Log in Windows Logs/Applications, and the faulting module is d3d9on12.dll and the exception code is 0xc0000094.

• Addresses an issue that prevents the file system control code (FSCTL_SET_INTEGRITY_INFORMATION_EX) from handling its input parameter correctly.

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.
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.
After installing this update, IE mode tabs in Microsoft Edge might stop responding when a site displays a modal dialog box. A modal dialog box is a form or dialog box that requires the user to respond before continuing or interacting with other portions of the webpage or app. Developer Note Sites affected by this issue call window.focus.	This issue is addressed in KB5016688. If you do not want to install this release, see the instructions below. This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can resolve it by installing and configuring the special Group Policy listed below. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.  Group Policy download with Group Policy name:  Download for Windows 10, version 20H2 and Windows 10, version 21H1 - Windows 10 20H2, 21H1 and 21H2 KB5014023 220624_22551 Known Issue Rollback Important You will need to install and configure the Group Policy for your version of Windows to resolve this issue.