Latest Version of Malwarebytes

BigBear68 said:

Thank you MoxieMomma for your input too,i followed both your advice and successfully upgraded to 2.1.4 with no problems.

Excellent!

Thanks for letting us know.

Cheers!

Interesting. Yet another scheduling issue. Win the change to BST(daylight saving time) over the weekend scheduled tasks run an hour later.

kado897 said:

Interesting. Yet another scheduling issue. Win the change to BST(daylight saving time) over the weekend scheduled tasks run an hour later.

There is a known issue with the scheduler not automatically correcting for DST.
It only affects users in Time Zones with DST or other time changes.

It will be fixed in a future release.

Until then, one workaround that will fix it is to delete the scheduled tasks and recreate them with a "starting date" of today and the desired scheduled time and task interval.
(If you use hourly update checks, it won't matter and you need not change anything. But if you want your scheduled (daily) scan to run at the original time, then this will fix the problem.)

You could probably fiddle with the task settings to fix your existing settings, but I found the other method was faster and guaranteed to work (at least on my rigs).

Thank you,

Thanks. I fiddled with the settings. We'll see tomorrow whether it picks up the correct time. I wonder why Malwarebytes doesn't use the Windows task scheduler. It would save all these issues.

kado897 said:

Thanks. I fiddled with the settings. We'll see tomorrow whether it picks up the correct time.

Yes, that ought to work.
To test it without waiting until tomorrow, you could just set a scheduled scan time for an hour or so from now and then check the History > Application Logs a bit after that, to see if it starts at the correct time?
If it's working properly, then you could change the scheduled scan time once again to the "desired" time.

NOTE: This is not new for 2.1, but if you enable the advanced scheduler setting to "check for updates before scanning", the scan start will be randomized +/- 15 minutes of the scheduled time. That's because scheduled update checks are randomized to balance server load. If you want the scan to start at the exact scheduled time, you'll want to disable that setting. Just be sure you schedule frequent update checks (hourly is the default), so that your scheduled scan will be likely to have the most current database.

I wonder why Malwarebytes doesn't use the Windows task scheduler. It would save all these issues.

AFAK, the DST bug is new to version 2.x
But I am not qualified to answer your question.
That might be a question that might be better directed to the product team here ?

Thank you

MoxieMomma said:

kado897 said:

Thanks. I fiddled with the settings. We'll see tomorrow whether it picks up the correct time.

Yes, that ought to work.
To test it without waiting until tomorrow, you could just set a scheduled scan time for an hour or so from now and then check the History > Application Logs a bit after that, to see if it starts at the correct time?
If it's working properly, then you could change the scheduled scan time once again to the "desired" time.

NOTE: This is not new for 2.1, but if you enable the advanced scheduler setting to "check for updates before scanning", the scan start will be randomized +/- 15 minutes of the scheduled time. That's because scheduled update checks are randomized to balance server load. If you want the scan to start at the exact scheduled time, you'll want to disable that setting. Just be sure you schedule frequent update checks (hourly is the default), so that your scheduled scan will be likely to have the most current database.

I wonder why Malwarebytes doesn't use the Windows task scheduler. It would save all these issues.

AFAK, the DST bug is new to version 2.x
But I am not qualified to answer your question.
That might be a question that might be better directed to the product team here ?

Thank you

Thanks for the link.

Everything seems to be working okay in the new version = still updating with popup :)

No way Jose I've waited almost a year to get them back
This is the first of the 2.0...'s that has actually produced a popup confirmation of an update via a schedule ,
Not since 1.75.. has it happened :)

Another item that is fixed now is if I started a manual scan mbam updated automatically and started scanning,
All version of 2.0... have asked if I wanted to update first = Da yes

So yea I'm a happy yard dog now