KB5015814

IT admins

After installing this update, some .NET Framework 3.5 apps might have issues or might fail to open. Affected apps are using certain optional components in .NET Framework 3.5, such as Windows Communication Foundation (WCF) and Windows Workflow (WWF) components.

This issue should be resolved automatically via a Troubleshooter on affected unmanaged devices. If your device is managed by an IT department or with enterprise management tools, you might not get the troubleshooter automatically and might require the below workaround to resolve the issue. For more information on this troubleshooter, please see Windows Update Troubleshooter for repairing .NET Framework components.

If you do not automatically receive the troubleshooter, you can mitigate this issue by re-enabling .NET Framework 3.5 and the Windows Communication Foundation in Windows Features. For instructions, please see Enable the .NET Framework 3.5 in Control Panel. Advanced users or IT admins can do this programmatically using an elevated Command Prompt (run as administrator) and running the following commands:

dism /online /enable-feature /featurename:netfx3 /all

dism /online /enable-feature /featurename:WCF-HTTP-Activation

dism /online /enable-feature /featurename:WCF-NonHTTP-Activation

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 addressed in KB5016691. If you do not want to install this update, 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 downloads with Group Policy name:

• Download for Windows 11 - Windows 11 (original release) KB5014019 220624_22553 Known Issue Rollback

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

All users

After installing this update, we have received reports that a small number of devices might be unable to open the Start menu. On affected devices, clicking or selecting the Start button or using the Windows key on your keyboard might have no effect.

This issue is addressed in KB5016629. If you are using an update released before August 9, 2022, see 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 a special Group Policy. The special Group Policy can be found in Computer Configuration > Administrative Templates > KB5014668 220721_04201 Known Issue Rollback > Windows 11 (original release). For information on 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:

• Download for Windows 11, version 21H2 - KB5014668 220721_04201 Known Issue Rollback

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

IT admins

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