As we are running hundreds of computers we cannot install the June-update manually, we do need a fix! Even more as Windows Defender does not receive any updates any more! Until now we have not found out which most likely cumulative updates of the last months exactly results in these problems but our users PCs Win 10 x64 enterprise v and some with v run in several problems afterwards:.
Thank you, MS - again I am facing the problem that updating should be stopped until it is not certified that updates won't create problems With Win10 we had switched to MS-Defender only but now it seems that we need to install another antivirus-software as well.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. Threats include any threat of suicide, violence, or harm to another. Any content of an adult theme or inappropriate to a community web site. Any image, link, or discussion of nudity. Any behavior that is insulting, rude, vulgar, desecrating, or showing disrespect. Any behavior that appears to violate End user license agreements, including providing product keys or links to pirated software.
Unsolicited bulk mail or bulk advertising. Any link to or advocacy of virus, spyware, malware, or phishing sites. Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct.
CSP policies are not common outside of enterprise environments, for which this issue is not common for home users and personal devices. Workaround: To mitigate this issue, IT administrators using Intune or other tools can modify the Windows registry before installing this update following the steps below:. Note: If you have already installed the update and the blue screen error message shows up during the device's restart, please launch Windows in Safe mode to add the registry entry.
Important : This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs.
For more information about how to back up, restore, and modify the registry, see How to back up and restore the registry in Windows. Resolution: This issue was resolved in updates released March 22, KB and later. If you are using an update released before March 22, , you can resolve this issue using KIR. This KIR will not propagate to devices automatically. Devices that have installed an affected update and encountered this issue can resolve it by installing and configuring a special Group Policy which can be downloaded here.
To configure the special Group Policy use the following steps:. This issue might be encountered when attempting a manual reset initiated within Windows or a remote reset. Workaround: To mitigate this issue, you can do the following:.
Resolution: This issue was resolved in KB Some devices might take up to 7 days after the installation of KB to resolve the issue and prevent files from persisting after reset. For immediate resolution, you can manually trigger Windows Update Troubleshooter using the instructions in Windows Update Troubleshooter. Important: Devices which have already been reset and OneDrive files have persisted will require the workaround above or another reset after applying one of the resolutions above.
After installing KB on domain controllers DCs , affected versions of Windows Servers might restart unexpectedly. You might receive an error dialog for Lsass. Currently, the latest security update was released on February 8, and is the recommended option. If you would like to install the update, you will need to Check for updates and select "Optional updates" and then select KB See the Microsoft Update Catalog for instructions. Note KB will not install automatically.
Resolution: This issue was resolved in updates released January 11, KB and later. If you are using an update released before January 11, , you can resolve this issue using KIR. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy preferred.
Recent emails might not appear in search results on Outlook desktop app on Windows If the default search in the Outlook app is set to server search, the issue will only affect the advanced search. Workaround: To mitigate the issue, you can disable Windows Desktop Search which will cause Outlook to use its built-in search.
This issue is resolved in KB Devices connected to a domain that is configured to use MIT Kerberos realms may not start up or may continue to restart after installation of this update. Devices that are domain controllers or domain members are both affected.
If you are not sure if your device is affected, contact your administrator. Microsoft strongly recommends you install the latest servicing stack update SSU for your operating system before installing the latest cumulative update LCU.
SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU. For more information, see Servicing stack updates. To get the standalone package for this update, go to the Microsoft Update Catalog website. You can import this update into WSUS manually.
See the Microsoft Update Catalog for instructions. For a list of the files that are provided in this update, download the file information for cumulative update Table of contents. Windows 10, version 21H2 update history. Windows 10, version 21H1 update history. Windows 10, version 20H2 and Windows Server, version 20H2 update history. Windows 10, version and Windows Server, version update history. Windows 10, version , Windows Server, version , and Windows Server update history.
Windows 10, version update history. Windows 10, version and Windows Server update history. Windows 10 initial version released July update history. Windows 10, version , all editions More Release Date:.
OS Build Need more help? Expand your skills. Get new features first. Was this information helpful?