Cumulative updates for Windows 10 and Windows 11 - August 2022

Sumit 44,316 Reputation points Volunteer Moderator
2022-08-09T17:33:16+00:00

The following release notes coincide with Cumulative updates for all the supported versions of Windows, released on August 9th, 2022.

Windows 11

Windows 11 (original release): KB5016629 Build 22000.856

August 9, 2022—KB5016629 (OS Build 22000.856) (microsoft.com)

Improvements

This security update includes improvements that were a part of update KB5015882 (released July 21, 2022) and also addresses the following issues: 

  • Addresses a known issue that might prevent some of you from opening the Start menu. On the affected devices, clicking or tapping the Start button or using the Windows keyboard shortcut might have no effect.

Known issues in KB5016629

Applies to Symptom Workaround
IT admins 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.<br><br>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.<br><br>Group Policy downloads with Group Policy name:<br><ul><li style="margin-left: 0"><p data-prewrap="true"><a href="https://download.microsoft.com/download/5/e/3/5e356255-fd5f-47b4-b10d-267cbfc24e63/Windows%2011%20(original%20release)%20KB5014019%20220624_22553%20Known%20Issue%20Rollback.msi" target="_blank" rel="noreferrer nofollow">Download for Windows 11</a> - Windows 11 (original release) KB5014019 220624_22553 Known Issue Rollback</p></li></ul><br>Important You will need to installand configure the Group Policy for your version of Windows to resolve this issue.

Windows 10

August 9, 2022—KB5016616 (OS Builds 19042.1889, 19043.1889, and 19044.1889)

August 9, 2022—KB5016616 (OS Builds 19042.1889, 19043.1889, and 19044.1889) (microsoft.com)

Improvements

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

Known issues with KB5016616

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.<br><br>NoteDevices 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:<br><ol type="1"><li style="margin-left: 0"><p data-prewrap="true">Extract the cab from the msu via this command line (using the package for KB5000842 as an example): <b>expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path></b></p></li><li style="margin-left: 0"><p data-prewrap="true">Extract the SSU from the previously extracted cab via this command line: <b>expand Windows10.0-KB5000842-x64.cab /f:* <destination path></b></p></li><li style="margin-left: 0"><p data-prewrap="true">You will then have the SSU cab, in this example named <b>SSU-19041.903-x64.cab</b>. Slipstream this file into your offline image first, then the LCU.</p></li></ol><br>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.<br><br>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. <br><br>Group Policy download with Group Policy name: <br><ul><li style="margin-left: 0"><p data-prewrap="true"><a href="https://download.microsoft.com/download/8/8/0/88004bea-c83b-4d0c-9ac9-1996644578e9/Windows%2010%2020H2,%2021H1%20and%2021H2%20KB5014023%20220624_22551%20Known%20Issue%20Rollback.msi" target="_blank" rel="noreferrer nofollow">Download for Windows 10, version 20H2 and Windows 10, version 21H1 - </a>Windows 10 20H2, 21H1 and 21H2 KB5014023 220624_22551 Known Issue Rollback</p></li></ul><br>Important You will need to installand configure the Group Policy for your version of Windows to resolve this issue.
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.<br><br>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.<br><br>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.<br><br>We are presently investigating a resolution and will provide an update when more information is available.

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

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

115 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-08-22T15:22:22+00:00

    Has anyone noticed any new issues with Night Light since installing this update? After installing this update I cannot get Night Light to activate either manually or using the scheduled activation.

    I have tried updating and reinstalling the display drivers. I have also tried clearing the relevant files in registry editor and rebooting. As a workaround, I tried F.Lux, but this only worked when I turned it to grayscale.

    Does anyone else have this issue or have any suggestions for how to resolve it?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-08-22T06:58:04+00:00

    Hi Sumit,

    Out of several different machines I have only one that was having problems updating KB5012170.

    All windows 11 machines did that update without any issue and so did a Windows 10 Laptop that still has Legacy Bios.

    The only one failing was the Dell XPS 8700 (UEFI and Secure Boot) running 19044.1865 and trying to get next updates.

    It was hanging and freezing at 96% installing of KB5012170 when W.U. first tried the update.

    Every subsequent attempt failed downloading with error 0x800f0900 and was blocking any other updates from W.U.

    Also, KB5012170 first attempt left corrupted files that could not be fixed by "sfc /scannow" nor by

    DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH

    as I previously mentioned.

    Since I did not want to do a clean install, I finally tried the suggested solution from this other thread:

    KB5012170: Security update for Secure Boot DBX: August 9, 2022 - Microsoft Community

    As suggested, I cleared the existing Secure Boot keys and set back the factory defaults, saved the changes and exited BIOS to reboot back to a freshly restored image of 19044.1865.

    Then I installed KB5012170 offline using the .msu file downloaded directly from the MS catalog, that finally worked without hanging or any other error.

    Image

    After that I was back in business, I could get all the other updates offered by W.U. and finally got the system up to 19044.1947 without any further issues.

    Ran "SFC /SCANNOW" again and this time it ran clean. No more corrupted files. 👍

    Problem solved for that specific box.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-21T05:20:28+00:00

    @Sumit,

    B.T.W.

    After a clean install of 19044.1947, W.U. had no problems installing that KB501.2170.

    No hangs/freeze nor corrupting files. 🤷‍♂️🤣

    Clean install is really the last resort, I don't want to do that, I have many programs installed on this machine I don't want to start from scratch. 😜

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-08-21T03:23:20+00:00

    In a way, Good that it is not installing fg. Many people have reached out to me on Twitter to get around this messy update.

    Hi Sumit,

    It is not good, because after it fails it basically blocks any other updates from working and makes the machine useless. SFC /scannow finds corrupted files that it cannot fix not even with DISM restore health. Note that all the scans were clean before W.U. tried that update.

    I also tried the standalone .msu from the MS Catalog and it freezes the PC in a similar way.

    I cannot find a way to hold back W.U. from trying to install that specific update with build 21H2 19044.xxxx

    Image

    Temporarily I have a workaround for my case, simply because W.U. is not even trying to download that update on build 19045.1947.

    Luckily, I have an image backup of 22H2 before that KB5012170 update was installed, so I just restored that and I'm back in business on that Desktop.

    I'll be waiting for MS to release a proper fix.

    This one is a big disaster. 🤐😝

    22H2 without kb5012170:

    21H2 screwed up after W.U. tried to install KB5012170:

    Was this answer helpful?

    0 comments
  5. Sumit 44,316 Reputation points Volunteer Moderator
    2022-08-21T02:37:14+00:00

    In a way, Good that it is not installing fg. Many people have reached out to me on Twitter to get around this messy update.

    Was this answer helpful?

    0 comments