Scheduled scan time doesn't match actual scan time

Avast Free Antivirus / Premium Security
1

I have Program version 12.1.2272 (build 12.1.3076.6). I am running it on a Dell desktop under Windows 10, version 1511, OS build 10586.494.

Everything has been recently installed / upgraded, so I am pretty sure I have the current version of everything.

This is a new machine, and I installed Avast on 7/4/16, and started running scheduled full system scans on 7/5/16.

The scans are scheduled to run at “1:00:00 AM”, or 01:00 on the schedule screen. My scans take about 22 to 25 minutes to complete.

Here are the dates and times that are reported in the Scan History screen. All events are for the “Full system scan” that I scheduled.

7/5/16 1:00:00 AM
7/6/16 1:00:00 AM
7/7/16 1:00:00 AM
7/8/16 3:10:00 AM
7/9/16 1:01:02 AM
7/10/16 3:28:27 AM
7/11/16 1:54:44 AM
7/12/16 4:48:53 AM
7/13/16 1:11:22 AM
7/14/16 1:52:38 AM
7/15/16 5:13:41 AM
7/16/16 2:24:41 AM
7/17/16 5:20:13 AM
7/18/16 1:00:00 AM
no scan on 7/19…??
7/20/16 2:22:54 PM…note, now in the afternoon…
7/21/16 12:20:04 PM

Any idea what is going wrong, or how I can get the scheduled scan to start on time?

Thanks…Dave

2

Welcome to the forum. :slight_smile:
My first question is why are you running daily scans ???
Avast monitors everything you do on your system and on-line.
Once you know your system is clean, why run scans ???

3

Why have the option to schedule daily scans then? :wink:

Maybe he has set his daily scan to be more comprehensive than the real-time scanner. Who knows …

4

If it makes you happy, go ahead. it’s your time you’re using not mine. :slight_smile:

5

He is not using his time, since the scans are set to run at night. Presumably when he is not using his machine.

I myself run a daily full scan when I’m eating dinner, and the PC would otherwise be idling. So also … not competing with my usage of the machine.

Avast has added the option to schedule a scan. If that is such a weird thing, why not question that instead? :wink:

6

Hello djw86,
thank you for reporting this issue, it is internally tracked as QASP-685 and we have successfully reproduced it with Avast v. 12.2.2272 (build 12.2.3076). Is it still present with the latest release (Avast v. 12.2.2276, build 12.2.3126)?
Also, could you please send us SupportPackage?

Thank you!