latest update causes avast to become unresponsive

[jeanscondie]

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.

   Now I have to make a choice between MWB and Avast, easy really as there is only one MWB. I asked for a download link to the previous version which  worked without any issues but got no reply for that request, so tried to restore win 7  back to the previous version and that messed things up completely, had to reinstall windows 7 and to say that I am unhappy about that is an understatement.
So can I have a download  link to the previous version and how do I cancel my automatic renewal for avast
Kudos to you for taking responsibility for this mess, I certainly wouldn't have put my head above water.
 

[d00zah]

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.

[bob3160]

Maybe it's time to go back to basics. Use MB on demand not as a program running in the background.
I personally have done that since the release of version 3 because frankly it's a system hog.
I may own a lifetime license but only run the program once in a while as a double check to
see if it shows anything not shown by Avast. Outside of some questionable PUP's, that's never happened.
Your computer, your choice. I made mine quite a while ago.

[Asyn]

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

NP, everything else is for the devs to answer, I just did spread the info.

[d00zah]

As noted in another thread, I have had no such issues (most don't). MB/Avast (typically) run together with 'an acceptable' resource footprint... even on older HW. NOT gonna choose sides here, but you're right... if i doesn't work to your satisfaction, don't use it.

[REDACTED]

Hi everyone.

I had the same problem, my PC was unresponsive, crashing no internet ect.
I did solve the problem thats why I am here, I uninstalled Avas that I had bought a licence for.

Now my PC is working as it did before, can I ask for a refund as you supplied me with broken software.
I spent days trying to find out what was wrong, then I rang my local PC repair man he said to uninstall Avast
and see what happens.

Not a happy customer and I am not experienced like others in this forum, I buy software and expect it to
work, thats why I buy it. I had to install the free version of AVG to keep me safe, I am scared to install
Avast again.

Waisted money on this Avast stuff. Please dont have a go at me I am not as smart as you people on here
this is meant for the avast staff.

[bob3160]

Hi everyone.

I had the same problem, my PC was unresponsive, crashing no internet ect.
I did solve the problem thats why I am here, I uninstalled Avas that I had bought a licence for.

Now my PC is working as it did before, can I ask for a refund as you supplied me with broken software.
I spent days trying to find out what was wrong, then I rang my local PC repair man he said to uninstall Avast
and see what happens.

Not a happy customer and I am not experienced like others in this forum, I buy software and expect it to
work, thats why I buy it. I had to install the free version of AVG to keep me safe, I am scared to install
Avast again.

Waisted money on this Avast stuff. Please dont have a go at me I am not as smart as you people on here
this is meant for the avast staff.

Are you also running Malwarebytes

[bob3160]

Coco is not using MalWareBytes and still has the problem. So the problem is not MalWareBytes. Avast updated itself - overnight Tuesday to Wednesday? - and now

1   prevents access to the internet: Chrome claims the server was too slow to respond, but if I turn Avast off there is no problem. The servers respond as quickly as they have ever done.
2   prevents Outlook sending and downloading mail. Outlook reports that there are too many concurrent connections. It has not done so before.

I have rebooted the machine, and briefly things were better, but then they went wrong again. I have disabled the webshield controls. Avast looks at me sternly and says: 'All antivirus shields are off and that's bad. If the three...' How could I possibly disagree, but if Avast will not even allow me to connect to its own website, what am I too do.

When that message goes away it will tell me to reboot. But I have just rebooted this machine. Oh the irony of it! If I switch the machine off, of course the problem will go away.

Avast is the problem. The Avast free devices on this local network have no problems whatsoever with the internet connection or with email.

Has Avast been fixed, or does Coco have to go back to Norton?

I just ran across this article regarding Outlook too many simultaneous connections:
https://windowsreport.com/outlook-error-too-many-simultaneous-connections/

[REDACTED]

Are you also running Malwarebytes
[/quote]

Yes and I had it before as well, only thing that changed was Avast. Dont ask me to do anything as I uninstalled Avast thats how I can access this site and uses my PC.

[bob3160]

Are you also running Malwarebytes

Yes and I had it before as well, only thing that changed was Avast. Dont ask me to do anything as I uninstalled Avast thats how I can access this site and uses my PC.
No sense talking to someone who already has their mind set even when it may not be correct.
Your computer. Not mine.

[REDACTED]

Are you also running Malwarebytes

Yes and I had it before as well, only thing that changed was Avast. Dont ask me to do anything as I uninstalled Avast thats how I can access this site and uses my PC.
No sense talking to someone who already has their mind set even when it may not be correct.
Your computer. Not mine.

IF you read my first message to the Avast Staff you would of seen that I had uninstalled it.
You would of also read that I am a novice and not as smart as you people on here.

Your reply is not nice and uncalled for.

Yes it my computer and its working now whereas before it was not working.

LEARN to READ messages before to start on someone. Your reply was uncalled for, that's why you have a high post count you reply when you dont have to. The message did say its meant for Avast staff.

Dont reply to me again, I did read forum before posting so I know what you were going to say. I see you do a lot of posting. And most of the time the same replys.

[d00zah]

bob3160, your badge declares you an 'Überevangelist', which, by definition, suggests you've taken a side & are somewhat less than objective. Not necessarily a bad thing... I've consulted this forum for years & your helpful posts figure prominently. But...

People are coming here, in a panic because their PC was rendered unusable... following an Avast update. Given the choice of temporarily disabling a single Avast component vs completely uninstalling software you don't use/formerly discarded, even when the former option has proven effective, your advice troubles me.

Please consider allowing the user to regain use of their PC, calm down & objectively weigh options.

Nuf sed. Thanks for your wisdom.

[bob3160]

Don't shoot the messenger. Just because you don't like the message.
The problem is clearly a conflict between Avast and Malwarebytes caused by Malwarebytes.
Removing either of the two programs or disabling the part that's causing the conflict solves the problem.
I just don't like to see the blame for the problem passed on to the wrong program.

[schmidthouse]

Don't shoot the messenger. Just because you don't like the message.
The problem is clearly a conflict between Avast and Malwarebytes caused by Malwarebytes.
Removing either of the two programs or disabling the part that's causing the conflict solves the problem.
I just don't like to see the blame for the problem passed on to the wrong program.

Seems to me that the options are clear, as you pointed out Bob.
"nuff said"

[Man1971]

d00zah, just a thank you for the workaround you posted yesterday in another thread to solve this issue.
I had an important task to deliver and you saved my bacon. 
Cheers!