I have a quick scan scheduled daily at 6 AM and a full scan scheduled at 3 AM on Monday morning. This posed no problems in Avast 2014 Pro. I put in the update for Avast 2015 Pro and now my scheduled daily scan runs at 12 midnight and my weekly scan tried to run at 9 PM Sunday night. I checked the scheduling and it still shows my previous settings. What would make the scheduled scan run at a different time?
My apologies for the double post. When I clicked on the Post button the Forum page would not reload. I had to close the tab and open the Avast Forum again in another tab.
Similar situation here, within the last few months Avast scan seems to run randomly through the day, where the scheduled scan was working fine up to that point. On my Desktop machine it switches (again seemingly random) between running the scan at the indicated time local or UTC time. (i.e. it seems to random pick what time zone it wants to use, but runs the scan at the “appointed time”)
Ok, I changed both machines’ schedules to run a quick scan at noon, neither did; at one minute after noon I changed both schedules to 1805, and they both started right at 1205. Not really expecting the same to happen tomorrow.
So Desktop did a shutdown after it’s scan, and I started it up a little while later… and as 1805 swings around, it runs again…
Laptop has not re-run.
Just no predicting when the thing will run, it would seem.
And no word from support on it? Seems like it’s been being reported on and off for years.
There is apparently a problem with the scheduling. It’s been reported.
Curious why you want to run a scan daily???
Anything new, changed or updated is checked by the on demand scanner.
I’m adding my name to the list of folks with problems with the scheduled scan not running at its scheduled time. I had mine set for 22:00 and it fired itself up at 13:00 consistently. Going to set it for 13:00 and see what happens. I’d like to see this fixed though, having to work around an error in a service I pay for doesn’t seem right.
I reported this “ages” ago (many times) with zero feedback…got finally tired of reporting with zilch feedback. >:( Also, another bug is Avast’s UI also pops up on screen after scan…scheduled scans used to stay minimized when done if all OK. Also, some of the times you get a false “Threat Detected” even when Scan shows fine in history.
Bottom line, all the above seem to be faulty with Avast on scheduled scans.
So, only thing I can tell you on scheduled time…this happens with the “standard/default” scans.
I found if you create a Custom Scan (even if same settings as one of the default ones) you can schedule and it’ll run on schedule.
I do a scan with Avast & MBAM Pro every morning at 4am & 5am before I wake up on all my PCs…and they work on time.
You can see that while Avast & MBAM active shields work fine together I don’t want the scanners running at the same time.
P.S. For those that have MBAM Pro and are/will do the same…make sure in MBAM Settings of the Scan you uncheck “check for updates before scan” or it will also not run on selected time…BUT unlike Avast, MBAM does acknowledge this is a known bug. If you are updating MBAM database throughout the day this is not big deal.
It did not, so far only on my win7 desktop, the seemingly random (although I have a pretty good guess) switching between system time and UTC continues.
I will try the laptop now and see if it’s behavior is altered.
I’m going to put my two cents worth in.
I’ve been using Avast for some 4 years now and run a scheduled Full System Scan at 02:00 every day. This might sound excessive as others have pointed out but since I use laptops exclusively running a scan that reads all the data stored on your hard disk/s can give you forewarning of a disk that’s on its way out and allow you to get all your valuable data and software off before it goes legs up permanently. I do also do a full system backup every 2 weeks to an external drive but you can still save up to 2 weeks of work knowing you have a disk on the way out. It also minimizes downtime as it gives you time to get a replacement disk ready.
Anyway, back to the problems of the scans not running at the correct time. This has only been a problem for me since it was upgraded from the 2014 version to the 2015 versions and as far as I can tell it’s using UTC, GMT, Zulu, whatever you want to call it time and the log files state the UTC time and date not the local time and date.
I telephoned the call centre about it and as expected they told me to uninstall and then reinstall the software using a fresh download as Wi-Fi isn’t 100% reliable and the original update could have been corrupted. It’s pretty hard for a Wi-Fi link to corrupt a file when our in house network is all CAT5 or CAT6 cable running at 1000/100 Mb/s but the technical support person at the other end didn’t seem to understand that people do actually use extremely reliable, much faster and secure cable networks to connect to the internet.
Anyway I gave it a go just in case and as expected it didn’t fix the problem.
Having said all that, I never had any problems on the two machines I have used Avast on over the years until it upgraded from the 2014 version to the 2015 version, so for me at least it would appear to be some problem in the 2015 release.
I’ve had the problem on and off, but since the 2015 release it’s been constant.
It sounds like, from your description, they are only interested in getting you off the phone, not helping, typical unskilled call center stuff. They get to record a call, and a solution, mark it closed and put a smiley face on their metrics; not doing anything and not helping.
Just tried it. Doesn’t fix it. I’m running Avast Pro Antivirus under Windows 8.1. I have had this problem since November or so; the scheduled scan feature is completely useless.
