Avast Frustration

Hey there!

Long time security software enthusiast here but I am running intro trouble with Avast so lets see what we can get fixed :). I am having a couple issues but I believe they are from the same root issue which I can not solve.

  1. Avast constantly tells me that its host is unreachable. I am constantly running into host unreachable issues and I am unable to download the latest VPS update. Streaming updates seem to be coming in normally but I am unable to get the VPS to connect to the host. I tried to update the VPS manually download VPSUPD.exe but when I get to the download being 66.9 of 69.3MBS the download just stalls out and quit.

  2. Because of this I am unable to get my Internet Security edition of Avast to become active and installed.

Here is the strange thing. I have installed Avast on two machines, both with different installers and both have had this issue. The even stranger thing is when I came home this morning one PC decided to finally connect to the update server and I was able to install the latest VPS update and activate my security suite purchase but the other still says host unreachable. Both are Windows 8.1 machines, but have Webroot SecureAnywhere also installed as a backup layer of security but Webroot has not blocked anything from installing. Even if Webroot is possibly the issue it still does not make sense if they are both setup the same way that it would allow access on one machine and not the other.

Any advice would be appreciated!

Do you have outbound blocking on your firewall?

Windows Firewall only, and I have already gone through and added AshUpdate, AvastSVC, AvastUI, AvastEMUpdate all to the Windows Firewall whitelist.

But could be generating a conflict with Avast.
Can you try disabling (or better uninstalling it) and then installing Avast from scratch to test?
Installation from scratch:

  1. Download the latest version of avast! Uninstall Utility and save it.
  2. Download the latest avast! version and save it.
  3. (Optional) If you want, save your avast! settings for later restoration (Settings > Maintenance > Back up).
  4. Uninstall avast! from Control Panel (if possible) and reboot.
  5. Run the avast! Uninstall Utility saved on 1 in and follow the instructions. Reboot Windows in Safe Mode, uninstall avast! and then reboot in Normal Mode again.
  6. Install avast! using the setup saved on 2. Register your free copy or add the license key for the paid versions. Boot.
  7. Check and post the results.

Please, be patient, boot when it’s said to boot…

Why Using Multiple Antivirus Programs is a Bad Idea https://blog.kaspersky.com/multiple-antivirus-programs-bad-idea/

And you should uninstall ( not disable ) Webroot SecureAnywhere before installing Avast! https://www.avast.com/faq.php?article=AVKB11#articleContent
and scrool down for the link for Webroot.

Greetz, Red.

I feels so dumb, my old antivirus was Panda Cloud Antivirus. When I uninstalled it the Panda URL filter did not get uninstalled and it just so happens that the URL filter had Avast on its blocklist and it was not throwing any notifications. The streaming update server was not on its blacklist so that was what was throwing me off. Thankfully Webroot had nothing to do with it and now I can fully enjoy my Avast full suite!

My apologies for having this dumb mistake take up your time!

You have another problem comming if you dont remove Webroot … or why run avast when you already have webroot AV

Webroot SecureAnywhere is similar to Malwarebytes with the ability to be a companion to a currently installed AV :slight_smile:

Yes, they say that ??? I ran Webroot SpySweeper for many years along with Avast, but when Webroot dropped it in favor of SecureAnywhere, I had to stop using it. They even sent me a mail explaining that it could be ran along with my favorite AV so that I could renew my subscription, but in reality it is a full blown AV, and you do not need 2 AV modules in your system. Sooner or later they will conflict with each other.

I guess you found out the hard way, that what they claim isn’t a fact. :frowning: