I recently did a complete clean reinstall. I have Malwarebytes Pro (paid version) set to scan at 5:30 am daily. However, it now will start a scan after a reboot. I can't find any setting for this???
Jack
I think this has to do with Malwarebytes now using the "RunOnce" registry key. This causes programs to run whenever the computer reboots or a user logs in.
Run and RunOnce Registry Keys (Windows)
I first noticed this a couple of weeks ago when I installed Malwarebytes 1.70 beta. (Never had this issue in prior versions.) CCleaner > Tools > Startup > Windows tab showed a new RunOnce entry. Once I disabled it the startup scans stopped. If you don't have CCleaner you can still access it through msconfig > startup tab. (Just as a side note, Adobe Flash Player Update has used RunOnce for a long time and I got tired of it scanning every time I started my computer.)
I don't find that anywhere. There's nothing in the Run Once registry listing. I don't see it in msconfig, ccleaner, Startup or Win Patrol.
Last edited by fireberd; 28 Dec 2012 at 16:22.
Only other suggestion I have is to contact Malwarebytes. Sorry I couldn't be more help, Jack.
Malwarebytes : Comprehensive Support for our Home Users
I've run the malware clean utility, rebooted, and installed the latest version. It has not popped up and ran a scan after reboot (tried several times).
I got the utility and link to the new version HERE
The new version has a new icon for Malwarebytes.
If its still OK tomorrow, I'll mark this solved.
Thanks/Jack
What about your Update settings. I have my scheduled to check for updates every hour and run a Flash Scan if it finds an update. Check your MB log files and see what it is doing.
Jim
I only have it set to check for updates at 5:30 am (daily) and to run a quick scan (daily) at 6:00 am. I don't have the option checked to run a scan after update.
This is something that happened after a clean reinstall. As I noted I uninstalled and then installed a newer version of Malwarebytes and so far no popup scan after a reboot/restart. I'll see what happens after a day.
Jack
I do believe that when installing the older version the option of scanning at boot was in the installation process and not in the program itself. This is just going by memory of my 3 brain cells.
The installation of the new version seems to have fixed the problem. I'm marking this solved.
Quote
