Avast 5 scheduled scan time varies

Avast Free Antivirus / Premium Security
1

Greetings everyone. I am using Avast 5 Pro and it works great but has a small issue that is perplexing. I have the Avast scheduler set to do a full system scan at 1am. The scan does run but the scan start times in the scan log varies by several hours. From my scan logs, some examples of scan start times are as follows:

4/30/2010 5:14:10 AM 4/29/2010 3:11:51 AM 4/28/2010 1:00:00 AM 4/27/2010 1:00:00 AM 4/26/2010 5:47:43 AM . . . My Windows 7 Pro OS is in sleep mode at 1AM so the Avast scheduler does have to wake the system. Perhaps that is part of the reason for this variation. Any information on why this is happening would be appreciated.

Thanks in advance for your help. Regards.
Daryl

2

OK I was wondering, because the scheduler runs fine. It’s a sleep mode issue, at least here on Win7/64 waking up the system to run a scan doesn’t work, never did…there are options in power management to allow that (wake timers), but this doesn’t change anything. Just don’t count on that :wink:

3

How about the scan statistics - number of files, size of processed files, etc. - does it vary too?

4

Thanks for the reply Logos… I am running Windows 7 Professional 64-Bit and the system does wake. Not sure why your’s is not. I too have tinkered with the advanced power settings with no change noticed on this issue. Do you have the wake timers enabled on your system?

5

Thanks for the reply igor… the scan statistics are similiar for all the system scans. Avast is scanning ~62.5 gig in 15-20 minutes. Over 255,000 files in 23,000 folders.

6
Do you have the wake timers enabled on your system?

yeah of course I have, that’s why I mentioned it. This said I haven’t tried the feature (the avast feature) for a while, may be it works now…An old “bitlocker” issue with systems not shutting down properly has just been solved (through Win update), so may be wake timers work too now, could be related, gotta check that…

ps: bitlocker keys being not checked when resuming from sleep mode, I shouldn’t have expected any change after the bug fix. It still doesn’t work…at the pre-set times. So may be it does work like the OP mentioned later or earlier. But I only tested that with a pre-set time and a custom scan, and deleted the scan as soon as I realized that the system didn’t wake up accordingly.