Sartori Posted March 26, 2014 ID:808458 Share Posted March 26, 2014 Hello I have MBAM 2.0 configured to not to start when Windows is Launched but its doing it anyway. I also have the self protection module enabled, could that be why its still launching? Thanks Link to post Share on other sites More sharing options...
John L. Galt Posted March 26, 2014 ID:808641 Share Posted March 26, 2014 It might be, try disabling the self protection module and see. Also, please report back as to whether that fixes the problem or not. Link to post Share on other sites More sharing options...
AdrianH Posted March 26, 2014 ID:808661 Share Posted March 26, 2014 This is a problem. Uncheck start with Windows and if the protection is checked, MBAM starts at next boot. Link to post Share on other sites More sharing options...
Sartori Posted March 26, 2014 Author ID:808673 Share Posted March 26, 2014 Yes, thats what's causing it alright. Not a huge issue really I guess Link to post Share on other sites More sharing options...
Sartori Posted March 29, 2014 Author ID:810196 Share Posted March 29, 2014 Okay, initially I thought that having the self protection checked was causing MBAM to launch with windows but now thats not the case. It starts no matter what....so yeah this is an issue. I like to have a clean boot and then launch what I want. Link to post Share on other sites More sharing options...
John L. Galt Posted March 29, 2014 ID:810302 Share Posted March 29, 2014 Have you tried a clean uninstall and reinstall 2.00? See https://forums.malwarebytes.org/index.php?showtopic=122284 Link to post Share on other sites More sharing options...
Sartori Posted March 29, 2014 Author ID:810339 Share Posted March 29, 2014 Okay, looks like that fixed it. I should have done that in the first place especially with a complete new upgrade like this.... Link to post Share on other sites More sharing options...
John L. Galt Posted March 29, 2014 ID:810341 Share Posted March 29, 2014 Glad it worked. And, it makes no sense that the developers are pushing this upgrade over the current 1.75 since so much has changed (IMO). If anything, the 2.0 installer should recognize 1.75 is installed, save the relevant info like license info, then uninstall 1.75, reboot and then proceed to install 2.0. I honestly believe that would solve a lot of the problems now cropping up in the forums with the upgrade process.... Keep monitoring it through the next couple of reboots- a couple of people have reported that it starts happening again.... Link to post Share on other sites More sharing options...
exile360 Posted March 30, 2014 ID:810505 Share Posted March 30, 2014 Glad it worked. And, it makes no sense that the developers are pushing this upgrade over the current 1.75 since so much has changed (IMO). If anything, the 2.0 installer should recognize 1.75 is installed, save the relevant info like license info, then uninstall 1.75, reboot and then proceed to install 2.0.That's actually what it does. It saves the license info, uninstalls 1.75 and installs 2.0. It does not prompt for a reboot unless it is required to remove/replace any relevant files or data (which sometimes is the case, but most often not). Link to post Share on other sites More sharing options...
John L. Galt Posted March 30, 2014 ID:810667 Share Posted March 30, 2014 Thanks for the info, Samuel! Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now