Malwarebyte's web protection blocks adguard's web assistant from running. When i disable web protection and reopen chrome, i can see assistant working and blocking the ads, but when web protection is on, web assistant is not loaded and no ads are getting blocked. Is anyone facing such issues? Is there any ways to solve it?
Malwarebytes web protection blocks the Adguard web assistant.
- Thread starter srisar
- Start date
Windows 10, v 1909. After disabling WPF driver, it is holding up.
Hello there! 
Same thing for me. Adguard windows is no longer working after updating Malwarebytes.
As said by srisar, I have put WPF driver "OFF" - Intercept TCP connections (Advanced settings) is still "ON"
It is working again that way.
My configuration:
* Adguard windows 7.3
* Malwarebytes Premium 4.0.4.49 - Version of the "updated kit" 1.0.17732 - Version of "composant kit" 1.0793
* Windows 10 - version 1903 (18362.535)
Same thing for me. Adguard windows is no longer working after updating Malwarebytes.
As said by srisar, I have put WPF driver "OFF" - Intercept TCP connections (Advanced settings) is still "ON"
It is working again that way.
My configuration:
* Adguard windows 7.3
* Malwarebytes Premium 4.0.4.49 - Version of the "updated kit" 1.0.17732 - Version of "composant kit" 1.0793
* Windows 10 - version 1903 (18362.535)
Last edited:
awesome! thanks.
steve1209
Beta Tester
Strange I'm not having this problem in Adguard
WFP driver enabled
Intercept TCP connections (Advanced settings) is "ON"
Adguard 7.3 Nightly 25
Malwarebytes Premium 4.0.4.49 - update package version 1.0.18146 - Version of "component package version" 1.0.804
***There was a Beta update for Malwarebytes today I got***
Windows 10 Home version 1909 version 18363.592
PS I did NOT have this problem prior to today's Malwarebytes update either!!
WFP driver enabled
Intercept TCP connections (Advanced settings) is "ON"
Adguard 7.3 Nightly 25
Malwarebytes Premium 4.0.4.49 - update package version 1.0.18146 - Version of "component package version" 1.0.804
***There was a Beta update for Malwarebytes today I got***
Windows 10 Home version 1909 version 18363.592
PS I did NOT have this problem prior to today's Malwarebytes update either!!
I had this issue and when i disabled Use WPF network driver in AdG it worked afterward. I am right now on AdG 7.4 nightly 9 and i have no problem with WPF network driver on. (also i am using MB 4.1.0)
Legacy Edge is a different kind of animal.
In 7.4 the Assistant is considered legacy and has been replaced with the new Browser Assistant browser extension, which *should* work fine with Malwarebytes. The problem, obviously, is that it's not available for the legacy version of Microsoft Edge (since legacy Edge is more-or-less considered a dead browser with the new Edge released to replace it). And yes, for the new Chromium-based Edge the Browser Assistant found in the Chrome Web Store works fine.
IMO, once 7.4 final is released, this should be more-or-less considered a non-issue since the Browser Assistant is and will be available for all popular web browsers... well, except legacy Edge and Internet Explorer, of course. IMHO, those two browsers really shouldn't be used anymore.
In 7.4 the Assistant is considered legacy and has been replaced with the new Browser Assistant browser extension, which *should* work fine with Malwarebytes. The problem, obviously, is that it's not available for the legacy version of Microsoft Edge (since legacy Edge is more-or-less considered a dead browser with the new Edge released to replace it). And yes, for the new Chromium-based Edge the Browser Assistant found in the Chrome Web Store works fine.
IMO, once 7.4 final is released, this should be more-or-less considered a non-issue since the Browser Assistant is and will be available for all popular web browsers... well, except legacy Edge and Internet Explorer, of course. IMHO, those two browsers really shouldn't be used anymore.