Jump to content

Zdenal

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by Zdenal

  1. 1 hour ago, 1776blues said:

    Currently I have Real Time and Web Protection disabled  and just  turned on Do Not Disturb after reading your post. I repaired Avast as well.

    I had no issues while all three were disabled Question; I read that old files in Avast were not being removed when the program updated, is this still the case. I posted 4 screenshots on Avast and wonder if the two files dated last year could be the problem? See my post above and click on this title; Avast Blocking Access to Internet After Update 

    @1776blues Problem what you mention with bad file versions is not a cause of the malwarebytes iterop problems. It's something different. If you are affected by this issue, no internet browsing works with AVAST and WebShield enabled.  It's not this case. Preblem here is just in MalwareBytes  WebProtection and RealSite interop.

  2. 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.

     

    I'll appreciate if an responsible WFP developer contact us. I'll be happy to explain to him how to to solve the problem. 

    Best regards

    Zdenek

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.