bru Posted July 15, 2014 ID:853084 Share Posted July 15, 2014 I understand a scheduled scan won't run exactly at the time selected. There is a time window in which it can run. Even knowing this I think have run into an issue with my scheduled scan and was hoping someone could let me know if my thinking of what is happening is correct. I have my scheduled scan set for 10:00 PM daily. I also have it scheduled to be run within 23 hours if missed. It ran fine for a few weeks (at 9:48, 10:06, etc.). At some point I must not have had my computer on at 10:00 PM so it missed the scan. No big deal as sure enough the next day soon after I turned on the computer it ran the missed scan. Let say it was at 10:00 AM. Problem is as 10:00 PM rolls around it does not do the scheduled scan. The computer was on long enough that if it was going to run it would have. I believe it is because it already did a scheduled scan (albeit a missed one) during the day. Then the cycle repeats. The next morning it will run the missed scan and again the nightly scheduled scan will not run. Is this how it is supposed to work? How can I get it back to running the scheduled scan at the right time (my computer is usually on). Should I run a manual scan at the scheduled scan time? Link to post Share on other sites More sharing options...
Firefox Posted July 15, 2014 ID:853094 Share Posted July 15, 2014 Hello and Welcome back... I believe this has been reported and is a bug with the scheduler that is being fixed in a future build. FWIW I have once computer doing the same thing, instead of it running my scans at noon, its running them at 8AM. You could always do a clean reinstall of Malwarebytes, and it should fix the issue. In my case I really don't care what time it does the scan so long as it scans once a day. Link to post Share on other sites More sharing options...
bru Posted July 16, 2014 Author ID:853320 Share Posted July 16, 2014 Hello and Welcome back...I believe this has been reported and is a bug with the scheduler that is being fixed in a future build.FWIW I have once computer doing the same thing, instead of it running my scans at noon, its running them at 8AM.You could always do a clean reinstall of Malwarebytes, and it should fix the issue. In my case I really don't care what time it does the scan so long as it scans once a day.OK thanks. What I am experiencing might be different. Since it does not run the scheduled scan it runs it the next day because it is missed. It will happen at a different time depending on when I turn on the computer. What is strange is that the scheduled scan did run at the right time for quite a while until 10 days ago when the computer was not on for the whole day so it could not run. And then due to it being set to run within 23 hours if missed it ran at a different time and now it will not run at the orginal scheduled time. No matter what I do. I ran a manual scan at the scheduled scan time but sure enough the next day it ran a scan as soon as I turned on the computer since the scheduled scan was missed. So it is related to the scheduled scan not running and having "if missed" set. It causes me problems because the scan runs as soon as I turn on the computer so it gets bogged down just as I need to use it. Indeed a bug as you say. Hope it gets fixed. Link to post Share on other sites More sharing options...
exile360 Posted July 17, 2014 ID:853955 Share Posted July 17, 2014 Our QA team is investigating this issue. I suspect it is occurring because every time a scheduled task runs, Malwarebytes Anti-Malware sets the scheduled time for the next occurrence to run which I believe is based on the time the last instance ran in relation to the interval configured for it to run (e.g. every day, 24 hours apart in your case) and that rather than setting the time for the next occurrence to be relative to the originally scheduled 10PM timeframe, it is instead setting it based on the time that it actually ran when it recovered, resulting in that recovery time becoming the new baseline time for the scheduled scan's interval. If I am correct (which is what our QA team is verifying), then we will get this issue fixed in one of our upcoming releases. Thank you for bringing this to our attention. Link to post Share on other sites More sharing options...
throkr Posted July 31, 2014 ID:860885 Share Posted July 31, 2014 Any new information about when this issue will be fixed ?Thank you ! Link to post Share on other sites More sharing options...
exile360 Posted August 4, 2014 ID:862333 Share Posted August 4, 2014 Our QA team was able to replicate it. It should be corrected in our next release. Link to post Share on other sites More sharing options...
throkr Posted August 30, 2014 ID:873090 Share Posted August 30, 2014 Thanks for this info. Link to post Share on other sites More sharing options...
Recommended Posts