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
