WinXP Boot delayed by avast

[wilbertnl]

Hello All,

I'm using Avast! home edition for a little while now and lately I notice that after logging in XP I have to wait for Avast before I can use the computer. There is no network and also applications are on hold until Avast finishes whatever it is doing.

It looks like Avast is connecting to the server to find updates, and it keeps the rest of the system on hold. This is a new behaviour, I didn't notice this a month ago. The system is freshly re-installed, no weird hidden startups here.
Sometimes it takes minutes before the lock is released.

I'm using XP with SP2-RC1, firewall enabled. I have a broadband connection.
Any suggestion is very welcome!

[.: Mac :.]

I'm using XP with SP2-RC1,

this looks like the problem as I still use SP1 and there is no delay for me

[bob3160]

Let's hope this is a subject that will be addressed quickly since the final release of XP sp2 is right around the corner. :'(

[.: Mac :.]

im sur e it will be fixed in the next release

[Lisandro]

Wilbertnl, I make some shots:

1. Try Startup Delayer to control the sequence and the time you want your programs to start up. Choose the best sequence for you! (http://www.r2.com.au).

2. Check the option 'Show detailed information...' into the Advanced tab of the Standard Shield settings. You will see 'what' avast is doing... After that you can disable that option.

3. Could be some new issue of SP2?

[drahnier]

I can confirm the delay but am under the impression that it is somehow by intention. I could be wrong, though.

If avast! is running on XPSP2 and configured to have a permanent connection it is trying to update its virus definition data base (or even itself) at startup in an attempt to contribute to SP2's security enhancements. But, as I said, I might be wrong. avast! also has to communicate its status with the new XP Security center (and this may take some time?).

Perhaps one of the avast! guys could shed some light on this behavior.

[Lisandro]

Configured to have a permanent connection it is trying to update its virus definition data base (or even itself) at startup in an attempt to contribute to SP2's security enhancements. But, as I said, I might be wrong. avast! also has to communicate its status with the new XP Security center (and this may take some time?).

You can change the delay period before checking for an update in a permanent connection. See AlwaysConnectedWaitSeconds value in file avast4.ini (http://forum.avast.com/index.php?board=2;action=display;threadid=1647)  

[drahnier]

Configured to have a permanent connection it is trying to update its virus definition data base (or even itself) at startup in an attempt to contribute to SP2's security enhancements. But, as I said, I might be wrong. avast! also has to communicate its status with the new XP Security center (and this may take some time?).

You can change the delay period before checking for an update in a permanent connection. See AlwaysConnectedWaitSeconds value in file avast4.ini (http://forum.avast.com/index.php?board=2;action=display;threadid=1647)  

That tread is worth to be brushed-up a little bit and made available as a technical reference paper (a nice pdf document).

[Baldain68]

SP2 delays boot because the new Windows Security Center forces updates upon boot for any anti-virus software that it recognizes. Try changing the auto update feature.

[wilbertnl]

SP2 delays boot because the new Windows Security Center forces updates upon boot for any anti-virus software that it recognizes. Try changing the auto update feature.

And Avast! is not recognized, so far.

[wilbertnl]

I can confirm the delay but am under the impression that it is somehow by intention. I could be wrong, though.

I didn't look into the code  , but to me it looks like a deadlock: Avast is holding on while waiting to get an connection for updates, and the firewall is not started for that reason, so no network available...

I have a network icon in the system tray, and in above described situation the icon doesn't show up. Indicating that network is not available yet. Sometimes I get the error message that the firewall service couldn't start. I strongly believe that Avast! is holding a lock on services that should be starting, because it aims to update itself first.

[Vlk]

Some of the things that've been said in this thread are not true.

1. The WSC does not force the antivirus to update on boot.
2. Avast is (or should be) recognized by WSC, provided it's its latest version (4.1.389).
3. The updating process in avast is completely asynchronous. The system loads in it's entirety, and then, after some period of time, updating is attempted. No other component is waiting for the update to take place.


Do all of you XPSP2 guys experince this problem? The thing is, I'm not seeing it on our test machines... The only thing that changed in the latest build is that upon startup, avast reports it's status to the WSC. It's possible that this process is taking a long time to finish (maybe it's taking a long time for WSC to start - for some reason) -- I don't know... We may try to put the reporting in a separate thread, so that it doesn't influence processing of other things...

Vlk

[wilbertnl]

2. Avast is (or should be) recognized by WSC, provided it's its latest version (4.1.389).

If you want me to post a print screen with Avast version info (4.1.389) and warning of the Security Center, with "Virus Protection not found" I will do that.

[Vlk]

If you want me to post a print screen with Avast version info (4.1.389) and warning of the Security Center, with "Virus Protection not found" I will do that.

So it doesn't recognize avast at all, or it just says it's turned off?

BTW the startup delay should be solved by tomorrow's update. I'd call it a work around instead of a fix - as it's evidently WSC's fault... Maybe they'll sort it out before SP2 goes official... I'll report this 'feature' to them.

Thanks
Vlk

[drahnier]

I have two mschines here running XPSP2RC1, and avast!, altest version.

avast! is recognized by WSC on both machines just fine. But: Both machines experience the startup delay.