Main Area and Open Discussion > General Software Discussion

MBAM: how is it starting automatically with windows??

<< < (3/3)

MilesAhead:
You could use AutoRuns or WinPatrol to find where it's being launched during startup.


AutoRuns is more comprehensive.  WinPatrol is easier and catches most of the startup stuff, but not all.

MilesAhead:

MBAM told me she did it on purpose because I was flirting with SAS.
-superboyac (November 17, 2014, 12:17 PM)
--- End quote ---

It's okay to flirt with SAS.  just don't flirt with disaster.  :)

tomos:
well under Windows 7 I'm still using Codestuff Starter for startup stuff (hasnt been updated in a while) -
it doesnt allow me to disable MBAM,
but it does show 3 x mbam exe's under Processes:

gui
scheduler
service

Then under Services there's the

Scheduler
Service

40hz:
Malwarebytes suggests the following:

Posted 08 April 2014 - 04:21 AM

If you've disabled Malwarebytes Anti-Malware from starting with Windows but it still starts up please try the following.

Delete Autostart Entries Using Autoruns:

    Please download Sysinternals Autoruns from here and save it to your desktop.

 

If using the paid PREMIUM version of the product please make sure you also disable Self Protection.

    
* Make sure you disable the program Self Protection if you've enabled it.
* From Settings -> Advanced Settings -> uncheck the "Enable self-protection module" and close the program
    
* On Windows Vista or Windows 7/8 Right-click over Autoruns.exe and select "Run as administrator"
* On Windows XP Double-click Autoruns.exe to run it.
* Now, in Autoruns, click on the Logon tab and look for any Malwarebytes Anti-Malware entries.
* If you find one, right-click on it and select Delete then click Yes when asked to confirm. Once that is done, reboot your computer and see if Malwarebytes Anti-Malware still starts when you've set it not to do so.
For those curious, this happens because the old start-up entry for Malwarebytes Anti-Malware 1.75 is sometimes left behind in the registry after it has been uninstalled. Malwarebytes Anti-Malware 2.0 does not use the registry to start with Windows, but this old entry may cause it to start.

--- End quote ---

Looks like Miles earlier suggestion to try to hunt it down with Autoruns is a good place to start. :Thmbsup:

Navigation

[0] Message Index

[*] Previous page