2 issues of avast antivirus

Hi

I have 2 computers on my desk
For a little period of time I am using both, one after the other on the same gringojack@aol.com line
I installed a 4.6 version of avast 4 home on each
On one of them I get a message on a red panel in the bottom saying that there is an error
I also have a fire wall that brings no problem, I think

I entered a registration # in each
Where this red error panel comes from?

thanks

Red popup is for update problems (the one above clock).
Check if that machine can connect to net without problems.

More information is needed to tangle this question, but if I would make a first guess:

Avast checks for updates as soon as the system is booted. After that every 4 hours (unless you change that in avast4.ini) My guess is that there is no connection to the net while Avast starts and then you would get the red box as RejZoR said.

If you mean there is a red stripe across the Avast blue ball next to the clock:
It means Avast isn’t running. Make sure any other AV is COMPLETLY removed before installing Avast on that system.

avast seems working good there is no red stripe on the the little blue ball and I am using the internet line, so it works
A wrong piece of info in the setup panel perhaps?

the other issue on the other machine, on the same internet line works fine

Please give us some more information.

What OS?
Does the redbox only appears after booting the system?
What are the settings for updates in Avast?

Change (or add) AlwaysConnectedWaitSeconds value into the [InetWD] section of avast4.ini file.
You could set the number of seconds to wait before attempting to update. The default is 30 but it may not be enough in some DSL systems. In this case, you can try increasing this e.g. to 60 (1 minute). That should be enough.
More details here: http://forum.avast.com/index.php?board=2;action=display;threadid=1647

hi tech
os is win xp pro

I m going to try the 60 seconds!

the smtp box is empty except port 25
the connection update has 2 unchecked boxes (internet)
the general update has 2 automatic check marks (update)

on both machine I only have ‘AssumeAlwaysConnected O’

Just add the line Tech suggested manually in that section.

Make this:
[b]AlwaysConnectedWaitSeconds=60[b]

it doesn t work any better when putting 60 seconds

After I tried to update thru the taskbar, I get a report ending with “Licence key for this product is temporarily disabled”

The 2 registration numbers are identical
Should I get a different one under an other name? ???

Did you use the Trial period (60 days) and now you’re using the Home version?
You can always try to register again, use the same email or another, copy & paste the registration number.

Into the firewall settings, you should check if the following programs should be allowed to connect:
ashUpdSv.exe (avast! Update Service)
avast.setup (avast! Update executable)

I have no such names

mine are:
ashserv.exe
ashmaisv.exe
ashwebsv.exe

Guess there is no problem since they are identical on both machines, and the other works fine!

In fact, if you don’t have avast.setup to connect you have:

  1. A firewall problem, bad configurated or, at least, is allowing everything to connect, a firewall hole or whatever.
  2. You can’t update in this computer.
    avast.setup is a temporary file that start (run) avast update. It’s necessary that it asks for an outbound connection when avast is being updated. Which firewall do you use?

hello Tech

Have no avast.setup file in my firewall, only the 3 I named, and they are allowed to connect.
After uninstalling, downloading and reinstalling an other instance, I entered a new registration number, for an other name. It seems to be working fine, no more red popup and I can update from anywhere in avast!

My firewall is McAfee.

Maybe misunderstood you about the avast.setup; where is it?

It’s a temporary file, it exists only while updating.
setup.ovr file is transformed into avast.setup file into the same folder (C:\Program Files\Alwil Software\Avast4\Setup).

I’m very, but very, surprised your McAfee firewall did not detect this! :o :o