** INTRODUCING: NEW BETA VERSION OF AVAST - NOW 6.0.1364 **

[YoKenny]

nope...that feature is broken in 1289... :'(

It worked fine in 1289 and also works in 1352 but I did not like it so I disabled it like DavidR
has shown.

[warlock]

Nothing to do with Avast, it's a windows problem, do you have Vista or 7? There is a different fix for each.

Win7

In that case, open this Microsoft KB article, and click on the "Fix it" button.

[DavidR]

nope...that feature is broken in 1289... :'(

Then why post this in the ** INTRODUCING: NEW BETA VERSION OF AVAST - NOW 6.0.1352 ** it has nothing to do with the beta build and as mentioned others have no problem with it in 6.0.1289.

Your signature also misses a crucial point what Windows version you are using and  if 32/64bit as fully up to date windows could mean anything from win2k upwards all of which could be fully up to date and run avast6.

[jrace]

***
I think it has something to do with the def update process. I just compared my Windows event log and avast setup.log and got these results:

***
16.11.2011 12:30 PM avast update
16.11.2011 12:31 PM reboot --> ERROR
17.11.2011 12:15 PM avast update
17.11.2011 12:24 PM reboot --> ERROR
18.11.2011 05:03 AM avast update
18.11.2011 08:18 AM reboot --> ERROR
18.11.2011 08:21 AM reboot OK
18.11.2011 10:23 AM avast update
18.11.2011 12:51 AM reboot --> ERROR
18.11.2011 01:05 PM reboot OK
18.11.2011 01:24 PM reboot OK
18.11.2011 02.25 PM reboot OK
18.11.2011 02.50 PM reboot OK
18.11.2011 06.10 PM avast update
18.11.2011 07.50 PM reboot --> ERROR
18.11.2011 11.25 PM reboot OK

I get always that event log error 6008 during the next reboot after avast has updated itself. I don't get those errors at any other times when rebooting my computer.

Comming back to that "system was not shut down properly warnings", I monitored my system for the last 24 hours and came exactly to the same findings and obviously to the same conclusion.
There must be some relations between avast! update and the "system was not shut down properly warnings".

[true indian]

@davidr

Just forgotten: Thanx for the welcome message on boot screen back! 

DJBone

[John_M]

FYI:  Avast AIS Beta 6.0.1352 is blocked by ClamAV when being downloaded through my Untangle box.

Virus Blocker signatures were last updated:    2011-11-19 9:50:44 am

Log File:
2011-11-19 10:42:46 am  blocked  xxx.xxx.xxx.xxx:1481  (HTTP) http://files.avast.com/files/beta/6.0.1352/setup_ais.exe  virus found  173.193.138.138:80
2011-11-17 10:25:08 pm  blocked  xxx.xxx.xxx.xxx:1275  (HTTP) http://files.avast.com/files/beta/6.0.1352/setup_ais.exe  virus found  85.17.24.203:80

[Dwarden]

i have question, is there way how force (setting in .ini) engine to do update on lower priority ?
i seen several times avast updating with not nice cpu spike

[Asyn]

i have question, is there way how force (setting in .ini) engine to do update on lower priority ?

No.

[Jekku]

***
I think it has something to do with the def update process. I just compared my Windows event log and avast setup.log and got these results:

***
16.11.2011 12:30 PM avast update
16.11.2011 12:31 PM reboot --> ERROR
17.11.2011 12:15 PM avast update
17.11.2011 12:24 PM reboot --> ERROR
18.11.2011 05:03 AM avast update
18.11.2011 08:18 AM reboot --> ERROR
18.11.2011 08:21 AM reboot OK
18.11.2011 10:23 AM avast update
18.11.2011 12:51 AM reboot --> ERROR
18.11.2011 01:05 PM reboot OK
18.11.2011 01:24 PM reboot OK
18.11.2011 02.25 PM reboot OK
18.11.2011 02.50 PM reboot OK
18.11.2011 06.10 PM avast update
18.11.2011 07.50 PM reboot --> ERROR
18.11.2011 11.25 PM reboot OK

I get always that event log error 6008 during the next reboot after avast has updated itself. I don't get those errors at any other times when rebooting my computer.

Comming back to that "system was not shut down properly warnings", I monitored my system for the last 24 hours and came exactly to the same findings and obviously to the same conclusion.
There must be some relations between avast! update and the "system was not shut down properly warnings".

Thanks for the info, jrace! That's what I thought.
The stable build 6.0.1203 was the last one which didn't have this issue. It's been there since.

@Vlk: Does this information and our findings help you at all to locate the problem/bug?

[Dwarden]

i have question, is there way how force (setting in .ini) engine to do update on lower priority ?

No.

then it would be nice to add this feature ... it's bit problem when you do something and get stutter and lag due avast updating on 'background'

[DavidR]

i have question, is there way how force (setting in .ini) engine to do update on lower priority ?
i seen several times avast updating with not nice cpu spike

Not to lower the priority, but to delay the update check. Try a forum search for AlwaysConnectedWaitSeconds and you will find lots of hits on how to delay it.

[Asyn]

then it would be nice to add this feature ... it's bit problem when you do something and get stutter and lag due avast updating on 'background'

I never had any issues when avast! updates.
Also this is OT here..!!

[Dch48]

I only get some hesitation when Avast updates at boot time, especially on the single core XP machine. It's much less noticeable on this one. When it updates during normal usage, I never notice anything until the popup tells me it has updated again.

[Dwarden]

I never had any issues when avast! updates.
Also this is OT here..!!

it's not OT as i never had such issue in past ... thus why i mention it in the beta thread ...

@DavidR - it's not related  to AlwaysConnectedWaitSeconds ...

i simply want set Avast to use low or lower priority for anything related to activity in updates ...

[DavidR]

Of course it would be related, delay the update check until it is well after the boot and additional cpu activity for the auto update (which is limited in its resource use, but not priority) wouldn't impact so much on boot time.