August 9, 2022—KB5016616 (OS Builds 19042.1889, 19043.1889, and 19044.1889)
Release Date:
8/9/2022
Version:
OS Builds 19042.1889, 19043.1889, and 19044.1889
EXPIRATION NOTICE
IMPORTANT As of 9/12/2023, this KB is only available from Windows Update. It is no longer available from the Microsoft Update Catalog or other release channels. We recommend that you update your devices to the latest security quality update.
NEW 8/26/22
IMPORTANT Microsoft released KB5012170 on August 9, 2022. It provides support for Secure Boot Forbidden Signature Database (DBX). This is a standalone, security update. Windows 8.1 and newer clients and Windows Server 2012 and newer servers must install this update regardless of whether BitLocker is enabled or supported on your device. After you install the update, you might receive error “0x800f0922”; see Update might fail to install and you might receive a 0x800f0922 error. After you install the update, your device might start up in BitLocker recovery mode. See Some devices might start up into BitLocker Recovery and Finding your BitLocker recovery key in Windows.
UPDATED 8/9/22
IMPORTANT Windows Server, version 20H2 is at end of service today, August 9, 2022. After August 9, 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 Server.We will continue to service the following editions: Windows 10 Enterprise and Education, Windows 10 IoT Enterprise, Windows 10 Enterprise multi-session, and Windows 10 on Surface Hub.
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 affects the printing of files you submit to a printer.
-
Addresses a known issue that might prevent the Input Indicator and Language Bar from displaying in the notification area. This issue affects devices that have more than one language installed.
-
Addresses a known issue that might cause printing operations to fail. It might also create printer duplicates on a device. The duplicate printer’s name usually has the suffix "Copy1". Applications that refer to the printer by a specific name cannot print.
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 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.
Important: Use EKB KB5000736 to update to Windows 10, version 21H1.
This 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.
Important: Use EKB KB4562830 to update to Windows Server, version 20H2.
This security update includes improvements that were a part of update KB5015878 (released July 26, 2022) and also addresses the following issues:
-
Addresses an issue that might cause the Local Security Authority Server Service (LSASS) to leak tokens. This issue affects devices that have installed Windows updates dated June 14, 2022 or later. This issue occurs when the device performs a specific form of service for user (S4U) in a non-Trusted Computing Base (TCB) Windows service that runs as Network Service.
-
Addresses an issue that creates a duplicate print queue. This causes the original print queue to lose functionality.
-
Addresses a known issue that might prevent the Input Indicator and Language Bar from displaying in the notification area. This issue affects devices that have more than one language installed.
-
Addresses a known issue that might cause printing operations to fail. It might also create printer duplicates on a device. The duplicate printer’s name usually has the suffix "Copy1". Applications that refer to the printer by a specific name cannot print.
If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.
For more information about security vulnerabilities, please refer to the new Security Update Guide website and the August 2022 Security Updates.
Windows 10 servicing stack update - 19042.1852, 19043.1852, and 19044.1852
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.
Known issues in this update
Symptom |
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:
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 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:
Important You will need to install and configure the Group Policy for your version of Windows to resolve 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. |
This issue is addressed in KB5017380. |
After installing this update, some Windows devices might have issues with audio not working. Some affected Windows devices might have no audio, but other affected Windows devices might only have issues on certain ports, certain audio devices or only within certain applications. Most affected audio devices drivers have the "audio enhancements" setting disabled before installing this update or the sound device driver has issues with the "audio enhancements" feature. |
This issue can be mitigated differently depending on your symptoms and if you have installed the update already. Please see the known issue on Windows release health for instructions to prevent and mitigate this issue. This issue is addressed using a Known Issue Rollback (KIR). This KIR will prevent the issue on Windows devices that have not installed KB5015878, but will have no effect on devices already affected by this known issue. 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 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, see How 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 resolve this issue. |
Starting at 12:00 A.M. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by the Chilean government about a daylight saving time (DST) time zone change. This moves the DST change which was previously September 4 to September 10. Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022:
|
This issue is addressed in KB5017380. |
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:
-
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.
-
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 and Microsoft Update |
Yes |
None. This update will be downloaded and installed automatically from Windows Update. |
Windows Update for Business |
No |
No longer available. |
Microsoft Update Catalog |
No |
No longer available. |
Windows Server Update Services (WSUS) |
No |
No longer available. |
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 5016616.
For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 19042.1852, 19043.1852, and 19044.1852.