With the arrival of the second Tuesday in July, Microsoft released the KB5015814 cumulative update as scheduled, which can upgrade the Windows 11 version number to OS Build 22000.795, and KB5015818 corresponds to 22621.232.
As expected, Microsoft's update fixes a bug for Windows 11 and confirms more bugs.
This security update includes part of the update KB5014668() released on June 23, 2022 and also resolves the following issues:
Fixed an issue with redirecting PowerShell command output so that the script log does not contain any output from the command. Therefore, the decrypted password is lost.
Windows 11 Servicing Stack Update - 22000.795
This update makes quality improvements to the servicing stack, the component that installs Windows Update. Servicing Stack Update (SSU) ensures a reliable and reliable servicing stack so that devices can receive and install Microsoft updates.
Known issues with this update
After installing this update, some .NET Framework 3.5 apps may experience issues or may not open. Affected apps use certain optional components in the .NET Framework 3.5, such as Windows Communication Foundation (WCF) and Windows Workflow (WWF) components.
According to reports, you can alleviate this problem by re-enabling .NET Framework 3.5 and Windows Communication Foundation in Windows Features.
You can also perform the following actions from the command prompt (run as administrator) with advanced user rights or IT administrator rights:
dism / online / enable - feature / featurename : netfx3 / all dism / online / enable - feature / featurename : WCF - HTTP - Activation dism / online / enable - feature / featurename : WCF - NonHTTP - Activation
After installing this update, IE modal tabs in Microsoft Edge may stop responding when websites display modal dialog boxes. A modal dialog is a form or dialog that requires the user to respond before continuing or interacting with other parts of the web page or application.
Developer Notes Sites affected by this issue call window.focus.
This issue can be resolved by using Known Issue Rollback (KIR). Note that it may take up to 24 hours for the solution to automatically propagate to consumer devices and unmanaged commercial devices. Restarting the Windows device may help to apply the solution to the device more quickly. For enterprise-managed devices that have the affected update installed and are experiencing this issue, the issue can be resolved by installing and configuring the special group policies listed below.