After cooperation and receiving detailed analysis from our lead driver developer, Avast determined there was a flaw in their driver implementation. This developer initially indicated that there was a problem with Malwarebytes Web Protection driver implementation. “Upon first discovering the conflict between Malwarebytes and Avast, Malwarebytes reached out to a product manager at Avast, who put us in contact with one of their Real Site feature developers. Update 9/3/18: Below is the statement BleepingComputer received from Malwarebyes concerning this topic: Collins further stated that Malwarebytes is working with Avast/AVG to resolve these issues.īleeping Computer has contacted both Malwarebytes and Avast for comment, but had not heard back at the time of this publication. While this could be one cause of conflict, there is obviously something else going on as users on the Avast forums have indicated that they are having problems after the even when they do not have Malwarebytes installed.įor now, according to Malwarebytes support engineer Devin Collins, if you are a MBAM user and wish to continue using their Web Protection module, you need to disable Avast's "Real Site Protection".
The developer further indicates that Malwarebytes is not performing UDP filtering using a MS recommended solution. Others have reported that they can Malwarebyte's Web Protection component again if they disable Avast's similar "Real Site Protection" feature.Īccording to a post by a Avast developer on the Malwarebytes forum, this issue is supposedly a conflict between the two program's web protection modules. Some users have reported that they can get Malwarebytes working again by disabling the program's Web Protection component, which protects users from malicious sites. Some of the issues being reported include being unable to open the program's dashboard, errors using Malwarebyte's support tool, Malwarebytes crashing, or the inability to keep real time protection enabled. To make matters worse, Malwarebytes users who have Avast installed are also reporting numerous problems this week as well after upgrading Avast. Permanent fix for the update issue is coming in future version.Īvast forum regulars are suggesting that users perform a clean install of Avast to see if that resolves the issue. Or uninstall and newly re-install your Avast Antivirus. To fix the problem please perform a repair: We have identified the issue as a problem during program update, that left some old Avast stuff there, that should have been updated. In one support forum post, a Avast employee named Filip Braun stated that this problem could be caused by a failed update that left old Avast drivers behind. When disabling the Avast WebShield component, which protects users from browsing to malicious sites or scripts, users reported that they were once again able to browse the web as normal.
0 kommentar(er)
