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. 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 downloads with Group Policy name: <ul><li style="margin-left: 0"><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</li></ul> Important You will need to install and 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. 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: <ol type="1"><li style="margin-left: 0">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></li><li style="margin-left: 0">Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path></li><li style="margin-left: 0">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.</li></ol> 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 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: <ul><li style="margin-left: 0"><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</li></ul> Important You will need to install and 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. 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. Note Follow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

August 26, 2022—KB5016688 (OS Builds 19042.1949, 19043.1949, and 19044.1949) Preview (microsoft.com) Build 19044.1949, KB5016688 available to Public build. - Microsoft Community

after the windows update ,camera application is not working

Just did it. Same info as above. Not sure how to get a link, but title is: Problem with KB5016616 Cumulative Update - doesn't finish install - Catagory Install and Update / Downloading, installing, and configuring Windows Update. In the FBH report there is a share button that can generate the link, then just copy and paste the link that it generates. 😎

I let what updates that were out there already including the update that I believe trashed me go ahead and install, and it did install ok. But then I suspended further updates,, and still have not turned them back on. Still a little bit leery about updates for Windows 11 after the Microsoft support told be to be careful of them. Too be honest I installed the Microsoft updates accidently after I cleaned up my computer, because I thought it was asking me about Dell updates. I must have got lucky the second time around. From my experience with updates it is not unusual for this to happen. Could be I didn't have some process running the second time around that made the update burp the first time. That happens on a lot of systems during updates. You can't plan for everything the user might have when you are testing the update, What is not acceptable is that it trashes the system, and you can not back out and recover properly. When I was working with customers during an update, they always wanted verification that the system could be returned back to pre-update condition, or it cost us big$$$$$$$$$. Hope this helps.

Chuck_in_Ma, The Start menu problem was just one of many problems I had in Windows 11, after (KB5015814), I tried using the chkdsk command from the cmd prompt window. I am most comfortable with that as my Microsoft experience goes back to the days before windows. Anyway.... each time it just errored out. My guess is that the update corrupted a sector that could not be fixed without re-formatting. Only a guess. As I said in an earlier thread, Microsoft support also tried various tricks to no avail. Finally had to go to Dell support and re-formatted and re-installed the basic system, then I luckily had backups to get my system back up to the functionality I had before the corruption. Good luck.

Cumulative updates for Windows 10 and Windows 11 - August 2022

Sumit 44,316 Volunteer Moderator

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.

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

Anonymous

2022-08-26T22:58:34+00:00

August 26, 2022—KB5016688 (OS Builds 19042.1949, 19043.1949, and 19044.1949) Preview (microsoft.com)

Build 19044.1949, KB5016688 available to Public build. - Microsoft Community
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
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 No comments
Anonymous

2022-08-15T01:34:47+00:00

Just did it. Same info as above. Not sure how to get a link, but title is: Problem with KB5016616 Cumulative Update - doesn't finish install - Catagory Install and Update / Downloading, installing, and configuring Windows Update.

In the FBH report there is a share button that can generate the link, then just copy and paste the link that it generates. 😎
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2022-08-11T22:41:31+00:00

I let what updates that were out there already including the update that I believe trashed me go ahead and install, and it did install ok. But then I suspended further updates,, and still have not turned them back on. Still a little bit leery about updates for Windows 11 after the Microsoft support told be to be careful of them. Too be honest I installed the Microsoft updates accidently after I cleaned up my computer, because I thought it was asking me about Dell updates. I must have got lucky the second time around. From my experience with updates it is not unusual for this to happen. Could be I didn't have some process running the second time around that made the update burp the first time. That happens on a lot of systems during updates. You can't plan for everything the user might have when you are testing the update, What is not acceptable is that it trashes the system, and you can not back out and recover properly. When I was working with customers during an update, they always wanted verification that the system could be returned back to pre-update condition, or it cost us big$$$$$$$$$. Hope this helps.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-08-11T01:42:15+00:00

Chuck_in_Ma,

The Start menu problem was just one of many problems I had in Windows 11, after (KB5015814), I tried using the chkdsk command from the cmd prompt window. I am most comfortable with that as my Microsoft experience goes back to the days before windows.

Anyway.... each time it just errored out. My guess is that the update corrupted a sector that could not be fixed without re-formatting. Only a guess. As I said in an earlier thread, Microsoft support also tried various tricks to no avail. Finally had to go to Dell support and re-formatted and re-installed the basic system, then I luckily had backups to get my system back up to the functionality I had before the corruption. Good luck.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments