KB5014697

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

All users

After installing this update, Windows devices might be unable use the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the internet after a client device connects.

This issue is addressed in KB5014668.

IT admins

After installing this update on a Windows Arm-based device, you might be unable to sign in using Azure Active Directory (AAD). Apps and services that use Azure Active Directory to sign in might also be affected. Some scenarios that might be affected are VPN connections, Microsoft Teams, Microsoft OneDrive, and Microsoft Outlook.

Note This issue only affects Windows devices that use Arm processors.

This issue is addressed in KB5016138.

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.

IT admins

After installing updates released June 14, 2022, or later, PowerShell Desired State Configuration (DSC) using an encrypted the PSCredential property might fail when decrypting the credentials on the target node. This failure will result in a password related error message, similar to, “The password supplied to the Desired State Configuration resource <resource name> is not valid. The password cannot be null or empty.”

Note Environments which use non-encrypted PSCredential properties will not experience the issue.

DSC is a management platform in PowerShell that enables administrators to manage IT and development infrastructure with configuration as code. This issue is not likely to be experienced by home users of Windows.

This issue is addressed in KB5015814.