Avast installing 3 drivers, then destroying the TCP/IP stack.

[Vipersfate]

Had a customer bring me their computer in with issues. Customer installed avast. Checked out the system, no rootkits, virii, or anything negative, except that the entire TCP stack corrupted itself with the avast drivers. Why in the hell does avast need to install virtual drivers to protect a computer? Seriously, what's the fix for taking care of those issues? I've already reinstalled the TCP stack, and lo and behold, it's still out because of the avast drivers. Explanation required.

Edit: This is the same shit that Norton has an issue with as well. Be careful Avast! team, you're going to do the same shit norton did, and fail miserably like they did.

[essexboy]

As far as I am aware Avast does not mess with the stack - if it did then there would be a multitude of irate people around

What is the name of the driver ?

[Vipersfate]

Avast Firewall NDIS Filter Miniport.

EDIT: Ran aswclear, which I should'nt have to, and it removed the driver and cleared up the tcp/ip stack. That's a definite issue right here. There is absolutely no reason to install proprietary virtual drivers to protect a computer. Quit this shit.

I'm going to be recommending other products to my customers from now on, this is just unacceptable

[essexboy]

I have AIS on my system and have not experienced this problem

What was the previous AV/Firewall installed

[igor]

It shouldn't be that hard to understand that a network driver might be needed to implement the firewall functionality.
And since you seem to be the only one having this problem, the issue is/was most likely something else.

[AdrianH]

AIS on 3 systems here and never had this issue in avast 5/6/7.

[essexboy]

I have come across this problem before where McAfee or Norton was not fully uninstalled and the stack was blocked, and internet access was not available until it was totally removed