Jump to content


  • Content Count

  • Joined

Everything posted by msherwood

  1. Thanks @Aura and @David H. Lipman. We've shared all of the above with IPS.
  2. We are tracking this but need your help. If you're seeing any types of slow downs, please share the link and what you were doing (e.g. searching "malware stuff", browsing a specific section) here.
  3. Closing this per our PM conversation. Result: @att.net addresses are currently not receiving emails from us. He's going to stick with @outlook.com for now.
  4. I sent a new test directly from me. Please respond to that.
  5. I just sent you a test email. I also edited your post so your email isn't public.
  6. Hello @Phone Man. Have you double-checked your spam filters and folders? I don't see any errors on our side.
  7. You mean a new URL required a new saved login... weird! ^ both of these are as expected.
  8. A few quick things on this... Firstly, our recommendation is still what's posted in the first post of this thread and the KB article (both have the same details). Secondly, we have extensively tested this within our environments and we are not seeing issues after applying the suggested fixes. Lastly, we're going to have a couple of experts join this thread and further investigate the outstanding issues. Thanks again for being patient with us as we work through this.
  9. Let me ping them again and see what's up. Thanks for the reminder!
  10. Our testing is showing that this is no longer happening. However, we do recommend adding the exclusions to MSE.
  11. https://www.askwoody.com/2016/microsoft-pulls-ms-3197868-the-win7-security-rollup-that-blew-apart-malwarebytes/ If you were affected by this or are currently experiencing issues, please see this KB article: https://support.malwarebytes.com/customer/portal/articles/2647220-what-can-i-do-if-i-have-been-affected-by-the-kernel32-dll-false-positive-?b_id=6442
  12. We are seeing hanging issues with and no exclusions. If we enable the exclusions, no hangs. Anyone else seeing different results with
  13. @kmsheehan, @vchhuor and @oreonutz - thank you all for offering assistance to others and sharing details.
  14. We have received a handful of reports of Compatibility Assistant within Windows 10 telling users "Malwarebytes Anti-Malware doesn't work on this version of Windows." See Windows 10 build 14965 and Windows 10 build 14971. We are seeing the following: MBAM 1.75 EXE fails with compatibility warning MBAM 1.8 EXE (Enterprise build) fails with compatibility warning MBAM EXE fails with compatibility warning MB EXE installs properly At this time we do not have a workaround for those installers which are failing. We are in contact with Microso
  15. @RedCountyPete, @CoxGreen and @Stave - thanks for sharing more details around this and your specific situation. We are still investigating the root cause. We'll update this thread when we know more.
  16. We've completed thorough testing on the following setups with file and process exclusions in place: Windows 7 x64 Sp1 Pro – 1.7 Managed Client (MBAM and MBAE) and MSE Windows 7 x86 Sp1 Pro – standalone MBAM + standalone MBAE and MSE We were able to successfully scan and use the machines as you normally would. Please add the following files as both Excluded Files and Excluded Processes inside of MSE. Managed client: C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe C:\
  17. Yes, for those with x64. My message was a quick copy/paste to get it posted. I'll come back and edit here in a bit.
  18. We think this is different. We've been tracking this and other compatibility messages (which all are not true) the last few weeks. This one is new from this week. Give us a few to get back to you on this one. Edit: moved this here from the MBAM/MSE thread.
  19. If you're not having success with the exclusions, here's what worked for us within MBAM 1.80: 1 - Boot into safe mode with networking 2 - Open MSE – Go to Settings -> Excluded Processes and add the following: C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe C:\Program Files\Malwarebytes Anti-Malware\mbamscheduler.exe C:\Program Files\Malwarebytes Anti-Malware\mbamapi.exe C:\Program Files\Malwarebytes Anti-Malware\mbamdor.exe C:\Windows\System32\driv
  20. We can now confirm that excluding "c:\program files\microsoft security client" from MBAM 1.8 works. We are continuing to actively investigate.
  21. As a long-term solve, we agree. This suggestion is only a workaround for right now. Thank you for sharing. We are still actively investigating the root cause.
  22. We have no new updates at this time. Our suggested workaround is still disabling real-time scanning in MSE.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.