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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-08-22T22:16:02+00:00

    SUCCESS

    sfc /scannow solved my problem

    A number of the commentors in this thread have mentioned using this command without success for them. I decided to try the least drastic method before uninstalling the apparently offending updates of August 9, specifically KB5016616, on my Windows 10 laptop in anticipation of having to do the dreaded system retore (Yes, I have system backups) or, worse yet, a reset and clean install of Windows 10. My computer was working well enough to allow preparation for a short trip I took last week.

    After returning, I faced up to fixing things by whatever means. Lo and behold the sfc scan found corrupt system files and replaced them. Everything now works as far as I know. I had been missing the START menu accessed by key or mouse, many Windows accessories such as the snipping tool, access to the Activity Center, Phone Link, the SEARCH function in File Explorer, access to programs unless there were shortcuts on my task bar or desktop or I could find their exe files, and other Windows features. All now work.

    Because I had no access to the START menu, I also lost access to finding apps or RUN by simple typing. Fortunately, WINDOWS+X, did bring up a simplified menu of options including Settings, Power Options, and the Windows Power Shell with an option for running it as an Administrator. This access was critical to running the analytical tools without having to start the computer in safe mode.

    I followed the instructions from Windows Support.

    Windows Support File System Checker

    I ran the Deployment Image Servicing and Management (DISM) tool first as required for Windows 8, 8.1, and 10. I then ran sfc /scannow .

    The sfc tool reported it had found and replaced corrupted system files. I have not viewed the detail in the CBS log file it created.

    As if by magic (AIBM), but actually by the good efforts of the Microsoft programmers and the grace of the Windows deities, I am back in business with relatively little effort. The moral may be, "Always try the simple and minimally intrusive fixes first but have respect for others for which those fixes do not work."

    I do not suggest this method will solve everyone's issues. I appreciate the efforts of those much more expert than I am to contribute their experience and knowhow to this forum. With thanks, I am out of here.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-08-23T01:37:39+00:00

    chuck_in_MA

    Fantastic! Thanks for the feedback!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-23T02:52:43+00:00

    You are welcome. Stay positive. Well, not for Covid.

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Anonymous
    2022-08-23T03:46:54+00:00

    after the windows update ,camera application is not working

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments