Dev-Info: Hallo, I'm responsible for Real Site protection in the Avast product. I have tested both products several minutes ago, and problem is only in MalwareBytes Web Protection activation process. It hangs the MB product completely.
If I disable Real Site, enable MB WebProterction and then enable Real Site again, everything works well.
Some more technical pieces of information:
Malware Bytes is trying to filter the UDP traffic (probbably DNS). It's same as Real site does. If two products try to capture UDP traffic by Windows WFP technology, a UDP packet loop can occurs if it's not implemented correctly. We found this problem with several other products. It's caused by two WFP drivers, when each capture UDP packet generated by other, drop it and generate new one. But this new one is presented to first driver, captured, dropped, generated again and it can continue indefinitely.
We discussed the problem with Microsoft WFP developers, to try to find solution for the problem. Avast had some protection against this before, but it doesn't work every time. Then we implemented new solution recommended by Microsoft. I can see from driver debugging, that it works, when both components are active (as described above). Problem is just in WebProtection activation process (not under my control, no time for reverse engineering). Seems that the MB UDP filtering solution is not compatible with MS recommended solution, but anyway, if you use capture, drop, create and inject new packet scenario for the UDP traffic, it's completely wrong and can cause conflicts with many products.
Thanks, Asyn. I read that the day it was posted. But, with all respect to the stalwarts of the community... please try to see this from a slightly different angle:
- Despite the thoughtful/informed explanation Zdenal provided, it didn't really explain (maybe I missed i?) why this problem began with an Avast update? Users, who hadn't the benefit of the dev's explanation would rightly conclude...
- People coming here for a solution are being advised to perform all manner of draconian ('final' solution-type) remedial measures, when the same thread you quote reports they have been tried & bore no positive effect.
- In the absence of a software fix by either camp, I suggested a temporary solution, tried & verified by many (me!), which allowed users seeking help to regain use of their PC & stop panicking. None of the other suggestions achieved this end (short of completely removing one product , or the other).
Please understand that I own licenses for both of these products, & trust them sufficiently to install them on my PCs. I try not to take sides.
Further, I respect the helpful individuals who daily offer their personal time & wisdom to help others, but who, in this case, found myself knocking heads with. Sometimes the 'classics' aren't the solution. Sorry, & thank you.