After just updating to 4.8.1229, my PC is taking a lot longer to start up. Normally, my PC takes under a minute, but now it hangs for about 3/4 minutes at the stage where the wallpaper is showing but none of the onscreen icons are loaded. Once, it has loaded the icons but then waited 3/4 minutes whilst loading network and avast.
Are there any bugs/conflicts with this latest prog build?
Geoff
PS I have XP and Online Armor
That would seem to be overly long, what other security software do you have running on boot ?
What is your internet connection type (broadband) ?
If so avast could detect a connection and check for updates, though that shouldn’t have changed from the earlier program version.
When did you install online armor ?
I have no other security software running on boot. I have Broadband, and installed Online Armor about a month ago, with no problems - til now. I must emphasise that this problem started IMMEDIATELY after updating the avast program - and ever since.
I have just found this message, of which the first post exactly describes the same problem I am having
http://forum.avast.com/index.php?topic=34587.0
so I must read the rest of this thread. Hopefully it indicates a problem shared by others and maybe there is a suggested solution
Geoff
This is a known issue with Online Armor that is currently under investigation of the OA guys (seems like they need to fix it on their side so far).
Cheers
Vlk
That is rather surprising given that:-
Can you please give me the link where you found out that it is “currently under investigation of the OA guys”
I doubt there is a link, I would imagine that it is through contact between Alwil and OA.
I notice that Avast now slows the startup quite a bit. I did a lot of tweaks to speed up the PC (like stopping the index service) and they all helped. The broadband is slow to connect (it takes a long time for the data light to start flashing and the browser to come up).
I think what happens now is Avast is the first thing to run. It looks for a daily update. After finding (or not) and installing it, Avast lets the rest of the startup work.
The dilemma is; should I move Avast startup priority down and worry about something getting on the system before Avast is thoroughly up and running? Or put up with a slow startup? Problem is, I cannot for the life of me remember how to change the prioity list. Good old Google then.
M
I posted about this problem on another thread, and this is the most rediculous reply I’ve read in a long time. To blame Online Armor and say “they need to fix it on their side” is totally unresponsive. What about fixing it on Avast’s side, too?
Indeed, what has Avast done to interfere with OA, or any other firewall if it comes to that?
Will you read what the man said!
It seems does not imply blame it simply implies the current status of investigation.
If you have any experience (worthy of the description) of this forum then you will know the the avast team are more open than most in these issues and in the experience of most of us are willing to own up when it their problem.
There have been reports here of Online Armor and avast! ‘interfering’ with each other particularly at startup for some time. To get the lot you’ll need to search for both “online armor” and “online armour”.
I doubt it’s the firewall of OA or COMODO that conflicts with avast! More likely the behaviour analysis/HIPS.
Hi…
I’m not sure if it will work in this case but you could try uninstalling avast with the uninstall utility and then download and install a fresh copy.
You can find the utilty here…
http://www.avast.com/eng/avast-uninstall-utility.html
Best Regards…
I just can’t follow the logic. OA and avast co-exist perfectly on my PC. I then update avast with a prog update, and immediately my startup times go from under 1 minute to over 5 minutes. I don’t see how avast can dismiss it as an OA problem, when logically it has to be avast!
Don’t see any logic in that.
OA may simply contain a bug, which manifests itself only in specific circumstances. The avast! update may have changed the circumstances on the computer somehow (without doing anything wrong or bad, just different) - so the bug, previously hidden, appears.
[I don’t know anything myself about this particular problem, just explaining what Vlk said.]
A software conflict (or any conflict, for that matter) involves at least two parties. To say that the bug is in OA, and that the avast! update exposed it, is simply arrogance. I commend OA for trying to address the problem (according to Vik) and condemn avast! for not doing so (no one on this thread has claimed they are). Many people will have to face the choice of either keeping OA and ditching avast! or keeping avast! and ditching OA. I personally will keep the old avast! engine (4.8.1201), and will continue to update the database, until avast! v5 comes out. If at that time the problem hasn’t been fixed (either by OA or by avast!, I don’t care who), I will get rid of avast! and keep OA. You (avast!) should stop playing the blame game and try to fix the problem yourself, otherwise you’ll lose some customers and get a bad reputation.
Sorry, but you are not the one to say where the bug is - you don’t know it.
It’s up to the programmers (of both avast! and OA) to find out, possibly together - which I believe is happening. So, I’d ask for some patience… let’s hope the problem will be resolved soon.
These are the developers of avast, do you not beileve that haven’t investigated what the problems is. How else do you think they would make this statement in an open forum.
If the problem is one one side it should be down to that side to fix it, not for the other party to try and work around the problem. They don’t know the code within OA that may be responsible, so how could they apply a fix in avast to compensate for the unknown.
Alwil have identified problems in other software, Zone Alarm and Agnitum’s Outpost firewall (my own firewall), 2 name just two and that has brought about fixes in those firewalls. Alwil have been very open in these forums, you only have to check these forums, I’m just an avast user like yourself who happens to have been on the forums for four and a half years so I can personally attest to what I have seen.
If there is a problem and it is one of avast’s making, it has been a) acknowledged and b) promptly resolved with the help of avast users.
Just be careful that by condemning avast! for not doing anything to solve this problem based on your own interpretation of the straightforward comments by others in this thread, you are not yourself accused of “arrogance” and/or “playing the blame game”.
The written word can be a frustrating means of dialogue at the best of times but made all the more cumbersome when things that are not there are read from between the lines.
I don’t understand what you’re talking about. I’m in touch with Mike Nash (the CEO of Tall Emu - the makers of OA) and I didn’t state anything that wouldn’t be true.
Sir, I’m not playing any blame game, I’m just reporting what has been concluded by both avast and OA development teams working together on resolving the issue. Next time please refrain from using such an arrogant tone before checking the facts.
Thank you
Vlk
I had the same issue with OA and Avast. Neither program is to blame, but both are to blame, if you can follow the logic. 
OA has HIPS and when Avast starts, OA will allow it if you have given permission. When Avast updates, then because both security programs try to start first, OA sees a change in AVast and will block it until you allow it, HOWEVER, windows hasn’t started to the point that it will allow OA to notify you, hence the computer stops.
You can update Avast, then tell OA to go into training or learning mode while you reboot, or go into Avast and tell it to load last. Either way, it should allow OA to see the updated Avast and then ask you if it is kosher.
I’m not sure if Comodo has the same issue as it didn’t choke when I had it installed, but I know that OA does. However, that is why my brief stint with a HIPS FW is over. I do not have the patience to fuss with all this security BS and have gone back to basic security, such as a FW that is just a FW and, so far, an AV that is just an AV.
Just my enormous knowledge at work :
Colin