Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: ejrmelendez on December 07, 2012, 01:03:54 AM

Title: Internet connection not working after Avast! Boot-Time Scan
Post by: ejrmelendez on December 07, 2012, 01:03:54 AM
Basically, this is what happened with minimal scrutinous details:

Avast! detected malware threat and offered to "lock in Chest."
After this happened, I was prompted to restart my system and
perform a Boot-Time scan prior to rebooting it. I obliged,
and let the Boot-Time scan run. After returning, my internet connect
was disabled, as well as my Internet protection shields.
Also, internet in the rest of my house works, and my computer is bug free.
I've called my ISP, so it's not the connection error either.

Is this a common
problem, and how do I diagnose and fix it?

TL;DR: Internet worked fine. After malware threat, boot-time scan was performed.
Boot-time scan disabled internet connection. How do I fix it?
Title: Re: Internet connection not working after Avast! Boot-Time Scan
Post by: DavidR on December 07, 2012, 01:11:50 AM
What was the file name and location ?
Have you looked in the avast virus chest (avastUI > Maintenance > Virus Chest, this should give the file name and original location ?
Title: Re: Internet connection not working after Avast! Boot-Time Scan
Post by: chris.. on December 07, 2012, 01:20:34 AM
exactly what happened to me today.
Maybe your bootscan has deleted tcpip.sys file (if patched tcpip with wxp).
I resolve with tool I took in the topic:
http://forum.avast.com/index.php?topic=110804.15
Title: Re: Internet connection not working after Avast! Boot-Time Scan
Post by: DavidR on December 07, 2012, 02:44:27 AM
Which is why I asked what the file was and its location, if it was tcpip.sys and it is in the chest then it can be resolved, by restoration and exclusion.
Title: Re: Internet connection not working after Avast! Boot-Time Scan
Post by: igor on December 09, 2012, 01:39:38 AM
I don't think it's connected - the boot-time scanner wouldn't delete the tcpip.sys file (just like an ordinary scan wouldn't, only the anti-rootkit scan did).