The cause of conflict between Windows 10 and Avast wasn’t clear but Avast has issued an update fix for the problem.Īccording to Avast, an element of Windows 10 April 2018 Update is incompatible with the Avast Behavior Shield and is causing issues.
This update is now available for installation through WSUS. To get the standalone package for this update, go to the Microsoft Update Catalog website.įor a list of the files that are provided in this update, download the file information for update 4493448.Recently we reported that Microsoft has blocked Windows 10 April 2018 update on Windows PCs with Avast Antivirus. If you are using Windows Update, the latest SSU ( KB4490628) will be offered to you automatically. To get the standalone package for the latest SSU, go to the Microsoft Update Catalog. SSUs improve the reliability of the update process to mitigate potential issues while installing the Rollup and applying Microsoft security fixes.
Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest Rollup. For more information and AV update schedule, see the Avast support KB article. Avast has released emergency updates to address this issue.
Additionally, you may be unable to log in or log in after an extended period of time. Devices may become unresponsive at the login or Welcome screen.
Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install this update and restart. We are presently investigating this issue with Avira and will provide an update when available. Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing this update. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article. Microsoft has removed the temporary block for all affected Windows updates. Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing this update. For example, the SQL server service fails. Known issues in this updateĪfter installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). Security updates to Windows Kernel, Windows Server, Graphics Component, Windows Input and Composition, Windows Datacenter Networking, Windows MSXML, and the Microsoft JET Database Engine.įor more information about the resolved security vulnerabilities, please refer to the Security Update Guide. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons.Īddresses an issue that may cause compound document (OLE) server applications to display embedded objects incorrectly if you use the PatBlt API to place embedded objects into the Windows Metafile (WMF). Use these guidance documents to enable or disable these mitigations for VIA-based computers.Īddresses an issue in which netdom.exe fails to run, and the error, “The command failed to complete successfully” appears.Īddresses an issue that may cause authentication issues for Internet Explorer 11 and other applications that use WININET.DLL. For Windows Server guidance, follow the instructions in KB4072698. For Windows Client (IT Pro) guidance, follow the instructions in KB4073119. These protections are enabled by default for the Windows Client, but disabled by default for Windows Server. Provides protections against Spectre Variant 2 (CVE-2017-5715) and Meltdown (CVE-2017-5754) for VIA-based computers. This security update includes quality improvements. Security-only update Improvements and fixes