Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: kpfuser on January 19, 2005, 11:56:33 AM

Title: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 19, 2005, 11:56:33 AM
I need to write an advanced rule for the above firewall. For this I must locate avast.setup. A search of the entire C drive via the WinXP search utility showed that no such file exists. A search of past posts in this forum uncovered a known issue on this matter and that avast.setup is a temporary file. This brings up the following questions:

1. In which folder is avast.setup created?
2. How long does it stay there before it is deleted?

Thanks in advance.
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 19, 2005, 03:20:52 PM
1. In which folder is avast.setup created?

C:\Program Files\Alwil Software\Avast4\Setup\setup.ovr is 'transformed' into avast.setup

2. How long does it stay there before it is deleted?

Until the update is finished (and you can see it into Task Manager).
Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 19, 2005, 03:42:18 PM
Thanks!

I will see if I am fast enough to catch it next time before it vanishes. Last time I allowed the connection first on a one-time basis, collected the info on the respective connection, and by the time I got around to writing the rule avast.setup had vanished. Next time I will put the requested connection on hold till I can put together my rule with avast.setup present in its folder.

Thanks again.
Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 19, 2005, 09:01:02 PM
Well, it worked out OK in the end but not as I mentioned earlier. If  the request of avast.setup to connect is left unanswered, an advanced rule cannot be written because no other action will be allowed by the firewall except answering (yes/no) the request. Following Technical's info, the temporary file avast.setup will remain in its folder till the update takes place. Thus saying "no" to the pending request should keep avast.setup in its folder long enough to make writing the firewall rule possible. This is indeed the case and the rule was duly written. The downside: During six consecutive reboots, avast.setup asked to go to a different IP address each time, three of which cannot be found in the respective list of 16 IP addresses given in the FAQ files. In a nutshell, in the case of avast.setup, writing advanced rules for the Sygate firewall is possible but tedious due to the multiplicity of non-contiguous IP addresses avast.setup tries to connect to.  It should be added to the wish list of this forum that Alwil should purchase a block of IP addresses for their needs rather than the crazy quilt of disjointed IP addresses it now employs.
Title: Re: avast.setup & Sygate firewall revisited
Post by: xyzzy on January 19, 2005, 09:41:48 PM
The question is when Alwil abandons idea of avast.setup as disappearing and reappearing file...
X.

Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 19, 2005, 09:56:25 PM
xyzzy,

I just posted in their wishlist thread in this forum asking for what you said and for a more manageable block of IP addresses. Maybe you could post your views there too.
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 20, 2005, 02:41:20 AM
I posted there too... Hope that helps...
Title: Re: avast.setup & Sygate firewall revisited
Post by: General Failure on January 20, 2005, 11:31:43 AM
Why did you need this rule?

I'm using Sygate 5.5 and automatic updates work like a charm.

Bye

GF
Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 21, 2005, 01:30:12 AM
General Failure,

I need advanced rules because this allows for better control of SPFPro. By allowing only the connections I need and blocking all other connections I can operate without ever seeing a single intrusion attempt, let alone a major attack. Unfortunately, writing advanced rules for avast.setup has become nearly impossible. To explain, writing such rules as detailed in previous posts in this thread turned out to be useless. This is so because next time avast.setup wants to connect to one of the IP addresses included in the rules, the respective rule is not activated at all and SPFPro either asks for permission again or refuses to connect depending on whether it is put in 'ask' or 'deny unknown' mode. So I am back at the drawing board. It seems that the remaining options are to

1. run SPFPro in 'ask' mode always so that I can allow avast.setup to connect wherever it wants manually each time., or

2, write the advanced rules for avast.setup without reference to any application, which would make them applicable to any executable in my pc.

Altough both of the above options sound generally OK at this point, they lack the neatness and assurance of air-tightness that comes from the knowledge that only specific executables are allowed to connect to specific (for each executable) IP addresses and in the direction (inbound or outbound) needed only. It is rather unfortunate that my experience with avast has to begin on such a sour note.
Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 21, 2005, 11:49:27 AM
Addendum.

Option 2 of the previous post does not work either. SPFPro just keeps either asking for permission to allow avast.setup to connect, if it is in 'ask' mode, or denying permission outright, if it is in 'deny unknown' mode. It just doesn't seem possible to anticipate and preselect a reply to a request of avast.setup. It is as if the firewall sees avast.setup as a new file each time the latter is created. Oh what a mess!
Title: Re: avast.setup & Sygate firewall revisited
Post by: kubecj on January 21, 2005, 12:36:52 PM
Isn't this just a overkill? It should be enough for avast.setup to give it full control once. Don't tell me that sygate doesn't allow that. The list of the ip it may contact changes constantly without a warning, so allowing avast.setup to access only some sites will degrade it's performance (without any gain)

avast.setup is temporary because it changes on every program update. I don't think there's a serious need to change that.
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 22, 2005, 01:50:01 AM
kubecj, Sygate only asked me once to connect... I allowed avast.setup and no more asked... Nice for me.
Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 24, 2005, 02:11:29 AM
Quote
Isn't this just a overkill? It should be enough for avast.setup to give it full control once. Don't tell me that sygate doesn't allow that. The list of the ip it may contact changes constantly without a warning, so allowing avast.setup to access only some sites will degrade it's performance (without any gain)

Well, I set out to do exactly this.  In fact, with the help of Technical, I did it . I am not quite sure what you mean by "full control once" above. What I did was to allow avast.setup to connect to each relevant avast server not once but each time avast.setup wished to do so.  However, when

Quote
avast.setup .... changes on every program update.

or, as it seems, before every attempt at virus or system update, how can you expect such rules to work next time avast.setup mutates?

So all I can do is operate the firewall in 'ask' mode so that each time avast.setup asks to connect I can click 'yes.' However,

Quote
Sygate only asked me once to connect... I allowed avast.setup and no more asked... Nice for me.

does not coincide with my experience. To be sure, avast.setup does request a connection (as well as receives a return visit from an avast server) early on as soon as a dialup internet connection is established. Thereafter it appears that avast.setup has subsided for good. However, common sense should indicate that it can hardly be so. Indeed 4 hrs later avast.setup will be at it again. Now if this happens that you are not at your pc (as it happened to me 2 days ago), you will be presented with so many superimposed unanswered requests to connect that it will be a major chore, let alone annoyance, to answer them one-by-one with a yes or no so that they will disappear. A terse message that an error was encountered which may cause some avast files to be corrupted will be added for good measure too.

To summarize, running avast and Sygate together means that (1) you cannot run the firewall in 'deny unknown' mode (unless you switch back and forth between this and 'ask' mode), (2) you cannot leave your pc connected to the internet over long periods of time (such as may be needed for a large download) if you are not present, and (3) avast dictates to you on such matters rather than vice versa.

All this makes the statement

Quote
I don't think there's a serious need to change that.

somewhat debatable, in my opinion at least.
Title: Re: avast.setup & Sygate firewall revisited
Post by: kubecj on January 24, 2005, 09:34:07 AM
(3) avast dictates to you on such matters rather than vice versa.

All this makes the statement

Quote
I don't think there's a serious need to change that.

somewhat debatable, in my opinion at least.

We simply reserve the right to plan our bandwith. So we're forcing the client (avast.setup), to download from the sites we say, not from the sites you choose.

Regarding 'asking', I think Sygate should ask you only after program update, and most users don't have that set to automatic. Copying ovr->setup should be irrelevant to Sygate (and its constant problems)
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 24, 2005, 03:29:39 PM
(2) you cannot leave your pc connected to the internet over long periods of time (such as may be needed for a large download) if you are not present

In fact, I'm permanently connected and have no problems with Sygate (free version).
avast.setup asked me to connect in the past and never more.


(3) avast dictates to you on such matters rather than vice versa.

AVG does the same... or even worse: the free users can connect only one server.
But, on contrary, the paid version users can choose which servers and in which order they must be connected, better than avast does  :-*
Title: Re: avast.setup & Sygate firewall revisited
Post by: igor on January 24, 2005, 04:00:24 PM
But, on contrary, the paid version users can choose which servers and in which order they must be connected, better than avast does  :-*

I really wouldn't say it's better. I mean - the users don't know anything about the servers; some of them may be down, unreachable, slow... so users' choice of the servers to use may be far from optimal.
On the other hand, kubec can easily see the current state of the servers and "tune" the settings as needed.
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 24, 2005, 05:05:59 PM
On the other hand, kubec can easily see the current state of the servers and "tune" the settings as needed.

Who's there on his vacations?  ;D
Title: Re: avast.setup & Sygate firewall revisited
Post by: kubecj on January 24, 2005, 05:08:02 PM
What?  ::)
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 24, 2005, 05:14:47 PM
What?  ::)

Poor Kubec, he does not have vacations  ::) :'(
Thanks for the good hard work boys.
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on January 24, 2005, 11:04:16 PM
I hate to be the one to keep this thread alive, but I'm also experiencing problems with avast and spf (both free versions).

I've been browsing this forum for information and it appears to be a common issue among users with this setup. I'm not saying it's 50/50, but frequent enough to get a fix for I would think.

Anyway, I've setup an advanced rule to allow everything related to avast that I can find. I open up avast and it still shows the last update was 1/20/05. Before then it was back in December, and since then I've uninstalled, reinstalled, prayed, screamed, and managed to get it updated a little.  :)

When I forced an update, sygate prompted me again, which I found odd because I thought I gave everything permission. But, I gave it permission again making sure to check the "remember my answer" checkbox before doing so. I saw a brief display of avast updating itself. I get into the app again and lo and behold...still shows 1/20/05! The avast web site says 1/21 is the current version.

Does anyone have a solid solution for this? I'd really appreciate it.  :)
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 25, 2005, 01:48:05 PM
I hate to be the one to keep this thread alive, but I'm also experiencing problems with avast and spf (both free versions).
Does anyone have a solid solution for this? I'd really appreciate it.  :)

It's not a shame thing to keep this thread alive...
Just that I do not experience any trouble with Sygate and I'm receiving avast updates without trouble.
Rule based firewall could bring some trouble if 'anything' is wrong... For instance: other Windows applications and drivers must be correctly set: ndisuio.sys; alg.exe... etc.
A way of testing is disabling the firewall... if the avast update comes normally, so it's the firewall.
I indeed see that a lot of times Sygate does not bring the pop up message of connecting to focus, it won't be the most in top window. Other firewalls never do this (like ZA, for instance). Probably because Sygate uses a 'real window' and not a pop up message like the others.
Other times, only after boot I could 'see' the question for connection  :-[



Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on January 25, 2005, 04:21:39 PM
I neglected to point out that one of the things I tried was to set sygate to allow all traffic. That didn't work. I also uninstalled sygate...didn't work either. What I can't understand is why the rule I created wouldn't be the ultimate solution.  ???
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 25, 2005, 08:51:43 PM
What I can't understand is why the rule I created wouldn't be the ultimate solution.  ???

Can you post the rule?
Are you allowed to update? I mean, your avast registration key allows you to update?
See 'About' dialog when the update will expire...
Title: Re: avast.setup & Sygate firewall revisited
Post by: gbark on January 26, 2005, 02:14:43 AM
I've been monitoring this thread for a while and have decided to jump in.  I've re-read the posts and didn't see this possibility noted.

IIRC Kerio has a mechanism that will detect if/when an application has been modified since the last time it's hash was calculated. I'm thinking that, perhaps Kerio is seeing each new iteration of Avast.Setup.exe as a different program (something in it's hash being different for some reason - creation time?) and therefore blocking it.

I use Outpost Pro 2.5 firewall and I've had a devil of a time getting Avast v4.5 to work smoothly. I can still check my logs and see that Avast has been blocked from an automatic update at one point in time and allowed exactly 4 hours later - without any activity on my part at all. Sometimes the rules work; sometimes they don't.  ???

It wasn't until I set up Outpost to ignore changes to Avast.Setup.exe's hash (Component Control, in Outpost terminology) that things started working more often than not.

Another thing not mentioned and may be a factor is if your Kerio configuration is blocking local loopback addresses. Adding loopback rules to Outpost's Avast rules was necessary for me because I block loopback as a default rule. My logs show Avast.Setup using the loopback address for something. I suspect that when setup.ovr is "mutated" into Avast.Setup.exe the loopback address is used.

At any rate, although my logs show blocked connections, they also show allowed connections, and Avast is (almost) always up-to-date whenever I check it. Perhaps these ideas will be of some help to you.

Best of luck. Avast is worth whatever effort it takes to get it to work; including manual updates (which I did for a while while I figured it out.)  :)
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 26, 2005, 02:20:04 AM
Thanks gbark... very illustrative.

It wasn't until I set up Outpost to ignore changes to Avast.Setup.exe's hash (Component Control, in Outpost terminology) that things started working more often than not.

Yes... this happened for me and I allow 'all' connections from avast.setup and had no trouble.
Unfortunatelly, I do not use Outpost anymore  :-[
Title: Re: avast.setup & Sygate firewall revisited
Post by: gbark on January 26, 2005, 02:44:58 AM
Technical,

I've always thought that I'd like Kerio if I ever had to drop OPP. I like KPF's more "graphical" interface, but OPP has its plug-ins and is so configurable that I doubt I'll ever switch.  ;)
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 26, 2005, 02:47:35 AM
I've always thought that I'd like Kerio if I ever had to drop OPP. I like KPF's more "graphical" interface, but OPP has its plug-ins and is so configurable that I doubt I'll ever switch.  ;)

My problem was about budget  ;D
I'm using Sygate Personal Firewall (free)  :)

I feel like you... Outpost is very configurable... It's hard to left it behind  :'(
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on January 26, 2005, 04:14:12 AM
Can you post the rule?
Are you allowed to update? I mean, your avast registration key allows you to update?
See 'About' dialog when the update will expire...

For posting the rule, is this what you're looking for?

<begin>
Rule Summary:
This rule will allow both incoming and outgoing traffic from/to all hosts on all ports and protocols.  This rule will be applied to all network interface cards.   The following applications will be affected in this rule: avast! antivirus service,avast! e-Mail Scanner Service,avast! service GUI component.
<end>

And I checked the About screen. It shows my registration key, expiration says "never", and updates expiration says "March 1, 2006".

I appreciate everybody's input on this. I hope this information helps bring me closer to a solution.  :)
Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 27, 2005, 02:00:29 AM
Oh my! Just a couple of days absence and now this flurry of posts! Well let me only say my bit on

Quote
Rule Summary:
This rule will allow both incoming and outgoing traffic from/to all hosts on all ports and protocols.  This rule will be applied to all network interface cards.   The following applications will be affected in this rule: avast! antivirus service,avast! e-Mail Scanner Service,avast! service GUI component.

Imagine something in your pc masquerading as (or hitching a ride on) avast.setup or any of the other avast executables. Why, you gave it permission to connect to (and be contacted by) any IP address on the internet! Hardly the best way to deploy a firewall. And this is  in a nutshell another aspect of my avast vs Sygate experience, i.e., in order to appease avast, one is forced to do something or another (in the above case degrade security)  that he would not do of his own accord.

Please note that the (too) wide permissions given by the above rule can be also achieved essentially by allowing manually the avast executables to connect where they want after clicking 'remember my choice and don't ask me again' before clicking 'yes.' This is so  because of an uncomfortable quirk of Sygate to act as if a given permission applies to any future request by the same executable.

It is this very quirk of Sygate  that made me operate it via advanced rules only, which had given me impressions of peace and quiet till avast put paid to them. Oh well, one can find solace in the realization that we, the non-Zone Alarm devotees, like to tinker (a.k.a. interact, configure,...) with the firewall rather than stick to a 'set and forget it' policy. So, in this respect , avast gives us all the interaction with the firewall we bargained for and then some!
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on January 27, 2005, 05:49:16 AM
kpfuser, I've been out all day, so just now getting back to your reply. And btw, thanks for that too!  :)

I see your point about the potential of something sneaking in along with avast components. I'm sure it's just as possible with a many, many other programs as well, with or without a firewall in use. The fact that this situation involves a firewall probably lends itself to a little more scrutiny, too.

I am, however, making a desperate attempt here to continue to use avast, and encouraged by reading the success of other users. When I see a product I like, I stay loyal to it until it lets me down or I find something else better to try. It seems as though this situation has come up often enough (not just in this forum, but in searching on the web) that the good folks at avast could come up with a solution.

This is why I decided to take the advice found by others here about using advanced rules.

So...Technical? Do you have any tricks in your magic bag that might make this problem go away?  ;)
Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 27, 2005, 09:44:17 AM
davincim,

Don't take anything I have said in this thread as a recommendation to switch to a different antivirus solution. I am also impressed by the volume of good press that avast gets and, after switching from Norton, I do intend to give avast a long and thorough try. Whatever my gripes may be about how avast interacts with Sygate, let us not forget that this is a secondary issue compared to the basic ones, i.e., the extent and quality of antivirus protection, the frequency and ease of updates, the range and scope of available scans, the demand on system resources, etc. So, just like yourself, I consider avast my antivirus product of choice. However, if we don't gripe, what are forums good for? Maybe for exchanging slaps OK but not on the back.

Now, regarding

Quote
So...Technical? Do you have any tricks in your magic bag that might make this problem go away?

I am all eyes. I love miracles too but, in case one is not forthcoming, I suggest that you consider the following:

1. Give up on the idea of handling the problem through an advanced rule, as I have done already myself. After all, if you are using the free version of Sygate, the number of advanced rules you can write is limited (see a comparison of Sygate free and paid for versions). So save the rule for a case that can be handled neatly without having to open your pc to the world.

2. Operate your pc in 'ask' mode and click 'yes' (but not 'remember my choice.....') any time avast wants to connect somewhere  or be contacted by an avast server. You will have to click 'yes' twice early on and  in quick succession each time you connect to the internet and every 4 hrs thereafter, if you stay connected that long.

3. If the above shoe doesn't fit, try turning off the automatic update feature altogether and do a manual update each time you connect to the internet. It only takes a few clicks and the longest time to complete I have seen so far is 7s.

4. Continue hoping for magic.
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on January 27, 2005, 02:40:18 PM
But that's just it, I can't even get it to manually update.  :'(

I try from the system tray icon and from the application itself, and nothing is initiated when I select either the iAVS update or program udpate. It used to last month when I first installed it, but now it just ignores me.

And even more frustrating is when I'm in the program trying to update it and quit out of the application, it just hangs there for a while (avast interface doesn't go away). Eventually it does (under 60 sec. I'm guessing), and sometimes Windows pops up its annoying offer to report a problem.

My life gets more complicated.  :P
Title: Re: avast.setup & Sygate firewall revisited
Post by: lee16 on January 27, 2005, 02:59:36 PM
davincim,

Does a repair of avast help your problem? (Control panel>Avast>Change>Repair)

--lee
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on January 27, 2005, 04:25:23 PM
It's possible the first time I did it was the reason I was successful in getting a more recent update. I'll give it another try. Unfortunately, I can't post feedback until much later today...got to go to work.  ;)
Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 27, 2005, 06:53:55 PM
davincim,

Why don't you give the second option of my last post, i.e.

Quote
2. Operate your pc in 'ask' mode and click 'yes' (but not 'remember my choice.....') any time avast wants to connect somewhere  or be contacted by an avast server. You will have to click 'yes' twice early on and  in quick succession each time you connect to the internet and every 4 hrs thereafter, if you stay connected that long.

a try? You should untick your advanced rule first. If anything goes wrong now, it should be a more complex problem than how to configure Sygate to handle avast. In any case, you seem to have gotten yourself into a rather sophisticated mess the resolution of which should teach us all a thing or two. So good luck to you and let us turn it over to the 5-star generals of this forum.
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on January 27, 2005, 08:02:19 PM
hi kpfuser,

I'd rather sygate remember my choice because neither myself nor the rest of my family would want to be bothered by the regular pop-ups. And because it's avast that I trust, I don't mind giving permission to connect to the "mothership"  ;) on a regular basis. I reserve the "what about this one?" for programs I don't use very often, or when I think they need to make a connection.

Your input is very much appreciated though!  :)
Title: Re: avast.setup & Sygate firewall revisited
Post by: kpfuser on January 27, 2005, 11:38:06 PM
devincim,

OK my friend. Have it your way.
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on January 30, 2005, 06:59:50 AM
Okay, I tried the repair utility and it seems to have made a slight change, but only temporarily.

First, the version of database is dated 1/28 -- the date I performed the repair. Do they happen daily?

Second, when I manually try to update I don't get the window showing the process of updating. In short, nothing visible happens and the date stays the same.

And lastly, when I did the repair it hung up on the services screen. I had to hit "cancel" to close down the window. I've done two repairs since I've had avast and both times this has happened. So on the plus side it manages to update the database, but on the down side it doesn't completely repair or at least know when to quit the repair utility.

Avast support team: any ideas?  ???
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on January 30, 2005, 01:25:51 PM
First, the version of database is dated 1/28 -- the date I performed the repair. Do they happen daily?

Version is 504-4 released on 1/28/2005. Ok, you're updated.
The updates could be (generally) twice a week but if a virus is spreding in Internet you can have daily updates or even more than one by day.

Second, when I manually try to update I don't get the window showing the process of updating. In short, nothing visible happens and the date stays the same.

On the Update (Basic) settings, choose 'Details' and check the option to see the progress of the update.
The date won't change as you're updated...

And lastly, when I did the repair it hung up on the services screen. I had to hit "cancel" to close down the window. I've done two repairs since I've had avast and both times this has happened. So on the plus side it manages to update the database, but on the down side it doesn't completely repair or at least know when to quit the repair utility. Avast support team: any ideas?  ???

This is strange... you should be able to finish the repair option.
Did you have any other antivirus installed in your system? Which one?
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on January 31, 2005, 04:40:26 PM
Technical,

No, I'm not using any other virus app. I'll do as you suggest about turning on the "details". Thanks!
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on February 01, 2005, 04:22:27 PM
Okay, having the details show isn't what I was looking for. When I bring up the context menu from the system tray I select the option to update the database and the program. When I do that not even the details showed anything. I was expecting the small window to pop-up to show its progress.

Upon reviewing the avast web site it appears that another update has been made (31.1.2005), but my program only shows 28.1.2005.

Let me make sure I'm covering all the bases to make sure somebody doesn't see something:


That's all I can think of.
Title: Re: avast.setup & Sygate firewall revisited
Post by: davincim on February 02, 2005, 02:25:09 PM
Bump...
Title: Re: avast.setup & Sygate firewall revisited
Post by: christianha on April 07, 2005, 11:19:42 AM
I use a Sygate Personal Firewall and have given avast.setup all rights for accessing and downloading from Internet.
I have startet my Laptop 4 hours ago. From this moment on avast.setup needs 99% of CPU Usage.
All other Programs are permanently slowed down very much.
Word doesn't work anymore and Photoshop hang up at startup.
If I switch to manual Update, nothing changes.
after windows startup avast.setup again does something and blocks my cpu up to 99%....

This happens since the last update I made on 4.4.2005.
From this moment on something happens on my Laptop.....
My Profile from Mozilla Firefox got lost, all Favorites were lost and things like this.
After a complete Systemscan for Viruses and Worms from an other machine via Network, no Virus was found. Avast shot my complete system.

Now I need help....
Title: Re: avast.setup & Sygate firewall revisited
Post by: Lisandro on April 07, 2005, 02:02:17 PM
I use a Sygate Personal Firewall and have given avast.setup all rights for accessing and downloading from Internet.
I have startet my Laptop 4 hours ago. From this moment on avast.setup needs 99% of CPU Usage.

Did you allow avast.setup to connect the Internet into Sygate seetings?
This is the application to update avast!
Can you manually update avast? Did you set it to automatically update? How do you connect (dial-up or permanent connection)?