Table of contents
×

Release Date:

6/28/2022

Version:

OS Builds 19042.1806, 19043.1806, and 19044.1806

5/26/22
REMINDER Windows 10, version 20H2 reached end of service on May 10, 2022 for devices running the Home, Pro, Pro Education, and Pro for Workstations editions. After May 10, 2022, these devices will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10 or Windows 11. 

We will continue to service the following editions: Windows 10 Enterprise and Education, Windows 10 IoT Enterprise, Windows 10 Enterprise multi-session, Windows 10 on Surface Hub, and Windows Server, version 20H2.

5/10/22
REMINDER To update to one of the newer versions of Windows 10, we recommend that you use the appropriate Enablement Package KB (EKB). Using the EKB makes updating faster and easier and requires a single restart. To find the EKB for a specific OS, go to the Improvements section and click or tap the OS name to expand the collapsible section.

11/17/20

For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. For an overview of Windows 10, version 20H2, see its update history page

Note Follow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

 Highlights

  • Addresses an issue that prevents the Pashto language from appearing in the language list.

  • Addresses an issue that affects the touchpad area that responds to a right-click (the right-click zone).

  • Addresses a known issue that might prevent you from using the Wi-Fi hotspot feature. 

  • Addresses a known issue that might prevent the Snip & Sketch app from capturing a screenshot or from opening using the keyboard shortcut (Windows logo key+Shift+S).

Improvements

Note: To view the list of addressed issues, click or tap the OS name to expand the collapsible section.

Important: Use EKB KB5003791 to update to Windows 10, version 21H2.

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

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

  • Addresses an issue that affects devices enrolled in Update Compliance and have installed the April 2022 Windows non-security or later updates. For more information, see Monitor Windows Updates with Update Compliance. Devices that are enrolled in other Windows diagnostic data processor configuration programs or have a combined enrollment with any of these programs and Update Compliance are not affected.

  • Addresses a memory leak issue in IEMode.

  • New! Introducing the following Print and Scan features:

    • IPP over USB support – Microsoft has supported Internet Print Protocol (IPP) for network printers starting in 2018 with the release of Windows 10, version 1809. We are now expanding IPP support to USB printers.

    • Print support app (PSA) APIs – Using the PSA framework, printer manufacturers can extend printer functionalities and user experience. For more information, see Print support app design guide.

    • PIN-protected printing for IPP and Universal Print - Standard print dialogs now include a user interface to enter a PIN code.

    • eSCL Mopria Scan protocol - Windows now supports the eSCL Mopria Scan protocol. It can be used with Mopria certified scanner devices.

Important: Use EKB KB5000736 to update to Windows 10, version 21H1.

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

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

  • Addresses an issue that affects devices enrolled in Update Compliance and have installed the April 2022 Windows non-security or later updates. For more information, see Monitor Windows Updates with Update Compliance. Devices that are enrolled in other Windows diagnostic data processor configuration programs or have a combined enrollment with any of these programs and Update Compliance are not affected.

Important: Use EKB KB4562830 to update to Windows 10, version 20H2.

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

  • New! Adds IP address auditing for incoming Windows Remote Management (WinRM) connections in security event 4262 and WinRM event 91. This addresses an issue that fails to log the source IP address and machine name for a remote PowerShell connection.

  • New! Adds Server Message Block (SMB) redirector (RDR) specific public File System Control (FSCTL) code FSCTL_LMR_QUERY_INFO.

  • Addresses an issue that affects the Cloud Clipboard service and prevents syncing between machines after a period of inactivity.

  • Addresses an issue that prevents the Pashto language from appearing in the language list.

  • Enables the InternetExplorerModeEnableSavePageAs Group Policy. For more information, see Microsoft Edge Browser Policy Documentation.

  • Addresses an issue that affects the touchpad area that responds to a right-click (the right-click zone). For more information, see Right-click zone

  • Addresses an issue that affects some certificates chains to Root Certification Authorities that are members of the Microsoft Root Certification Program. For these certificates, the certificate chain status can be, “This certificate was revoked by its certification authority”.

  • Addresses an issue that leads to a false negative when you run scripts while Windows Defender Application Control (WDAC) is turned on. This might cause AppLocker events 8029, 8028, or 8037 to appear in the log when they should not.

  • Addresses an issue that prevents the use of Encrypted File System (EFS) files over a Web-based Distributed Authoring and Versioning (WebDAV) connection.

  • Addresses an issue that causes a domain controller to incorrectly write Key Distribution Center (KDC) event 21 in the System event log. This occurs when the KDC successfully processes a Kerberos Public Key Cryptography for Initial Authentication (PKINIT) authentication request with a self-signed certificate for key trust scenarios (Windows Hello for Business and Device Authentication).

  • Addresses an issue that causes the LocalUsersAndGroups configuration service provider (CSP) policy to fail when you modify the built-in Administrators group. This issue occurs if the local Administrator account isn't specified in the membership list when you perform a replace operation.

  • Addresses an issue in which malformed XML inputs might cause an error in DeviceEnroller.exe. This prevents CSPs from being delivered to the device until you restart the device or correct the XML.

  • Addresses an issue that causes Microsoft NTLM authentication using an external trust to fail. This issue occurs when a domain controller that contains the January 11, 2022 or later Windows update services the authentication request, is not in a root domain, and does not hold the Global Catalog role. The affected operations might log the following errors:

    • The security database has not been started.

    • The domain was in the wrong state to perform the security operation.

    • 0xc00000dd (STATUS_INVALID_DOMAIN_STATE).

  • Addresses a known issue that might prevent you from using the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the internet after a client device connects.

  • Addresses a known issue that might prevent the Snip & Sketch app from capturing a screenshot or from opening using the keyboard shortcut (Windows logo key+Shift+S). This issue occurs after installing the February 8, 2022 and later updates.

  • Addresses a memory leak issue in IE mode.

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

Windows 10 servicing stack update - 19042.1790, 19043.1790, and 19044.1790

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates. Key changes include:

  • Addresses an issue that prevents a pre-installed app from working as expected after you install a Windows update.

Known issues in this update

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:

  1. 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>

  2. Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>

  3. 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 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 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: 

Important You will need to install and configure the Group Policy for your version of Windows to resolve this issue.

After installing updates released June 14, 2022, or later, PowerShell Desired State Configuration (DSC) using an encrypted the PSCredential property might fail when decrypting the credentials on the target node. This failure will result in a password related error message, similar to, “The password supplied to the Desired State Configuration resource <resource name> is not valid. The password cannot be null or empty.”

Note Environments which use non-encrypted PSCredential properties will not experience the issue.

DSC is a management platform in PowerShell that enables administrators to manage IT and development infrastructure with configuration as code. This issue is not likely to be experienced by home users of Windows.

This issue is addressed in KB5015807.

Microsoft has received reports of issues affecting some printing devices following installation of this update. Symptoms observed may include duplicate copies of printers installed on a device (commonly with a similar name and the suffix "Copy1"), and applications which refer to the printer by a specific name cannot print.

Normal printer usage might be interrupted, resulting in failure of printing operations.

View the “Settings” app on your device. If a duplicate copy of a printer appears to exist under the “Bluetooth & devices” section, confirm whether this printer works. If so, this printer can be used normally, and other copies of the printer can be removed.

If the issue persists, update the print driver for your device. For guidance, see Install the latest driver for your printer. If you are still having issues, uninstalling and reinstalling your printer should solve the issue.

We are presently investigating a resolution and will provide an update when more information is available.

After installing updates released on June 28, 2022 or later, the Input Indicator and Language Bar might not appear in the notification area. The notification area is normally located on the right side of the taskbar. Affected devices have more than one language installed. The Input Indicator and Language Bar are used to switch between input or keyboard languages on Windows devices and are used especially with languages that use an Input Method Editors (IME).

This issue is addressed in KB5016616. If you are using an update released before August 9, 2022, see below.

This issue is addressed using a Known Issue Rollback (KIR). 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. The special Group Policy can be found in Computer Configuration > Administrative Templates > <Group Policy name listed below>. For information about deploying and configuring these special Group Policy, seeHow to use Group Policy to deploy a Known Issue Rollback.

Group Policy downloads with Group Policy name:

Important You must install and configure the Group Policy for your version of Windows to address this issue.

After installing this update, XPS Viewer might be unable to open XML Paper Specification (XPS) documents in some non-English languages, including some Japanese and Chinese character encodings. This issue affects both XML Paper Specification (XPS) and Open XML Paper Specification (OXPS) files. When encountering this issue, you may receive an error, "This page cannot be displayed" within XPS Viewer or it might stop responding and have high CPU usage with continually increasing memory usage. When the error is encountered, if XPS Viewer is not closed it might reach up to 2.5GB of memory usage before closing unexpectedly.

This issue does not affect most home users. The XPS Viewer is no longer installed by default as of Windows 10, version 1803 and must be manually installed.

We are working on a resolution and will provide an update in an upcoming release.

How to get this update

Before installing this update

Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

Prerequisite:

Based on your installation scenario, choose one of the following:

  1. For offline OS image servicing:

    If your image does not have the March 22, 2022 (KB5011543) or later LCU, you must install the special standalone May 10, 2022 SSU (KB5014032) before installing this update.

  2. For Windows Server Update Services (WSUS) deployment or when installing the standalone package from Microsoft Update Catalog: 

    If your devices do not have the May 11, 2021 (KB5003173) or later LCU, you must install the special standalone August 10, 2021 SSU (KB5005260) before installing this update.

Install this update

Release Channel

Available

Next Step

Windows Update or Microsoft Update

Yes

Go to Settings Update & Security > Windows Update. In the Optional updates available area, you’ll find the link to download and install the update.

Windows Update for Business

No

None. These changes will be included in the next security update to this channel.

Microsoft Update Catalog

Yes

To get the standalone package for this update, go to the Microsoft Update Catalog website.

Windows Server Update Services (WSUS)

No

You can import this update into WSUS manually. See the Microsoft Update Catalog for instructions.

If you want to remove the LCU

To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages.

Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

File information

For a list of the files that are provided in this update, download the file information for cumulative update 5014666.  

For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 19042.1790, 19043.1790, and 19044.1790

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×