arbrich

I have been waiting for a couple systems to auto update to the new Component package update 1.0.160 automatically. I know you said that it may take a few days but my one system got hung again, stopped scanning and could not stop the MBAM Service to restart it and had to restart the computer but it is still on 1.0.141 after 2 weeks. When can I expect auto updates ?? I do not want to have to manually upgrade 100 different systems. Thanks, Rich

Will the new Component package update 1.0.160 automatically install or is this a manual install for each client ?

Yes, please confirm we DO NOT need SEP 12/14 Exceptions for every SEP install. Thanks

Hi Guys, just checking to see if any update on this with testing etc.. Thanks

OK, Do you have a time frame ? And please let us know if we can help test.

Another thing I am really interested in is WHY does this issue not seem to crop up in 3.06 ?? We have multiple users that we are not upgrading until this gets resolved that DO NOT have this issue. MAlwarebytes Version: 3.0.6.1469 Component Package Version: 1.0.103 Update package - 1.0.2195

OK, I got my hands on SEP 14 MP2 today. I have done the following installs with MABM 3.1.2 to keep testing and will keep you posted: 1) SEP Full install - Wind 10 Pro, with SEP Exceptions 2) SEP - Virus and Spyware Protection ONLY - Win 10 Pro, NO SEP Exceptions 3) SEP - Full Install - Win 7 Pro, NO SEP Exceptions dcollins please update us if you make headway with Symantec

ThirdEye, Please follow up with us on this to see if this "trick" works consistently. Need to see if it holds after reboots / Windows updates, etc.... Also with multiple OS - Win 7 / Win 10 and multiple versions of SEP - 12.1, 14, 14MP1. Especially if it works without adding all of the exceptions which is a huge time consuming invasive task with multiple machines.

I doubt Symantec is going to make any changes for you but I applaud you reaching out to them to resolve. From a customer's perspective MBAM worked fine for a long while (years) hand in hand with Symantec (that is an MBAM selling feature) and now it does not after MBAM pushed out an upgrade. In many cases the Symantec Software install did not change but MBAM did and now it doe not work. My feeling is just like everyone has to work around Microsoft and all their changes MBAM should work around Symantec in the same way.

I had to reboot another PC 4 times after applying exclusions to SEP to get MBAM to finally start normally. Now the disturbing point. My maint machine without a restart the MBAM Web Protection and Malware Protection turned itself OFF and locked up running apps again. I notice that the Report logs do not show that the nightly scan ran last night leading me to believe that the protection failures were initiated by the auto scan starting last night and NOT completing. (which I had seen in 3.06 and Windows 7 previously) the Service then got hung again and only a reboot got things going again. Oh and by the way another 3 customers called with the same issues. The only way is to TURN OFF Anti Exploit Protection after restart to stop these calls until this issue gets resolved.

Just tried it and turned SELF Protection module On again and after first reboot - WebProtection and MalwareProtection OFF again, tried quitting MBAM and service hung - trying to stop, rebooted again and it came up so I turned SELF Protection module OFF again.

dcollins - cannot see all the exceptions and extensions can you slide the bar over and upload again ??

dcollins, Thanks for the info. shepcon, I will try this on my end if you can do the same please report back and let us know what you find. Thanks

Yes, I have turned off the Self Protection Module on a couple machines and am waiting for results since it is so intermittent. We have also turned Anti-Exploit OFF on a couple machines to see how we do. We figure we were just using SEP alone prior to this so giving anything a shot at this point.

I will be happy to supply Sep 12.1.6, 14, 14MP1 client installs - Buy the way I have a couple machines with older versions of SEP 12.1 doing exactly the same thing. Just spent another 45 minutes fixing another customer machine.

I agree with Shepcon this is a bad problem and interaction with SEP and we need a fix as it is affecting every PC we work with that has SEP. I will help test anything you have.

It feels like a timing issue as sometimes you can boot and everything is fine and other times some Protections start and others do not start and then only ones active are Anti-Exploit and Anti-Ransomeware however many application will not run and MBAM gets stuck and the Service will NOT stop if you quit MBAM or try to shut it down from services.msc control panel. Then after a restart and MBAM starts running normally many times it will start running a scan thinking it missed they last one or in fact was stuck and had not scanned previously.

They are the same logs I sent you in the other thread that I opened:

We have put those exceptions in and it has not helped. We are getting multiple calls daily with this issue and we cannot stop the MBAM Service, have to restart the machine and have resorted to Turning Anti-Exploit Protection OFF so people can work. WE have the same issue with SEP 12.1.6, 14, and 14MP1 and it is intermittent. It was suggested in another thread I opened to the Turn OFF Enable Self Protection Module so we are trying that. This has been a nightmare for us and our customers.

I am having the exact same experience on multiple PCs with Windows 7 and Windows 10. Been fighting this since 3 got released. Shepcon are you running Symantec Endpoint Protection by any chance as I seem to have that as a common factor with many PCs although not all ??

Since it happens intermittently - I do not know. I can turn it OFF on my system and see if it helps but I will not know until it decides to lock up again (or not) I am having this same issue at many customers we are fielding multiple calls a day and have to spend time restarting machines sometimes 2 or 3 times. Service gets hung and there is no other way get out of it other then restart Only commonality is Windows 7, Windows 10 and Symantec Endpoint Protection 12.1, 14, 14MP1. We did not have these issues for years then when 3 came out we have been fighting with it ever since. We have resorted to turning Anti-Exploit Protection OFF so people can work. I would love to discuss over the phone so we can get our arms around this. I have new customers who I pushed to buy MBAM telling me they want a refund etc....

Her you go. FRST.txt mb-check-results.zip Addition.txt

OK it ran this time - Here is the dump MBAMService.exe_170614_154157.dmp

I downloaded and did it all last night and today so unless you posted a newer version today I did use latest.

I ran that one as well it was actually #5 but the screen shot you have above was for mbamservice_crash.bat wich is #4. I did just run it again and I get NO dump file with that one as well. I attached a couple screenshots to try and clarify the confusion.