Jump to content


  • Content Count

  • Joined

Everything posted by msherwood

  1. Were you able to try disabling real-time scanning in MSE and did that work for you? Thanks for sharing and confirming the workaround. To confirm, are you saying you had to disable real-time scanning in MSE and disable MBAE on all machines or just some where disabling real-time scanning in MSE didn't work? Have you tried our suggested workaround of disabling real-time scanning in MSE?
  2. We can just now confirm a workaround is disabling Microsoft Security Essentials' real-time scanning (in normal or safe mode). We're still troubleshooting and will provide updates here as we learn more.
  3. Really appreciate your offer, @goatmale. No need to open a support case (unless you want to). We'll be posting our updates here. Thanks for sharing, @sueska_mb.
  4. Thanks for sharing your details. We are still trying to track this down. We also have a line open with Microsoft and we're actively discussing it with them.
  5. We're actively troubleshooting right now. Locking this thread and directing everyone here:
  6. We're hearing reports of conflicts between Malwarebytes Anti-Malware and / or Malwarebytes Anti-Exploit and Microsoft Security Essentials (MSE) or Microsoft System Center Endpoint Protection (SCEP). We have created a KB article to help resolve this conflict: https://support.malwarebytes.com/customer/portal/articles/2650097--malwarebytes-and-microsoft-security-essentials-conflicts?b_id=6442 If needed, a copy of the KB article's solution steps are included below. Solution:
  7. Same here. I'm going to open a ticket with IPS now. Thanks for alerting us!
  8. Going to test this with you. Sending you a PM now. Can you respond back to that?
  9. Thanks for always checking on our stuff, @Gt-truth! Similar to the other tools thread, it's simply not a priority right now for us.
  10. Hi @Gt-truth. We have discussed this idea a few times in the past but have not yet dedicated resources towards it. Right now it's not something we're going to focus on.
  11. Welcome to our forums! It appears the link within the app is double broken (extra slash and using an old URL format). You can see it here: Side note: we are not actively maintaining StartUpLite.
  12. Thanks for the suggestion, @IgorDotNinja! Right now we've paused development on FileASSASSIN. If we start up again, we'll review your suggestion a bit more.
  13. Are you talking about the toolbar? That's a different setting in the ACP and they use the concept of small, medium and large (toolbars). It's also an all-or-none setting where if you adjust the "small" toolbar it affects all aspects using the small toolbar (e.g. mobile editor for post replying, PMs in full view). The challenge is the PM toolbar forces a smaller bar even though it might not need to do so. When we last looked at this (also around the v4 update), we could not adjust it. We'll look at this again.
  14. You did! We looked at this during the initial move to IPS 4 but opted to not do it as we wanted to keep as many variables set to default as possible so we could better learn the new software. There's a built-in setting to expand the layout but that didn't quite meet our needs when we last looked at it. We'll look at this again and report back. cc @AlexSmith
  15. Ah, got it. As @Aura said, we don't recommend using JRT on a daily basis or from a prevention standpoint. Well, unless you're getting infected every day! Yep, @Aura once again is correct! Great to hear! Thanks for letting us know. We too are glad @thisisu made JRT!
  16. You bet! Thanks for sharing your results. Yeah, we have discussed this a few times but decided against it as we didn't want to disrupt the automated process. What would you prefer it do?
  17. We've deployed JRT 8.0.9! You should receive the new build via the updater within JRT or you can download it directly. Release notes: https://forums.malwarebytes.org/topic/189059-junkware-removal-tool-jrt-809-released/ @tacua - please try the new version and let us know if it's working for you.
  18. We've completed our in-depth testing and it's ready! We'll be uploading JRT 8.0.9 a bit later today. Watch for the announcement here. Also, here's a quick overview of what happened and how we addressed the issue. With the latest builds of Windows 10, Microsoft made a small change to their restore point creation API that can potentially cause a restore point to be abandoned if the requesting process exits before Windows has finalized the restore point. The operating system notifies older builds of JRT (and even some Microsoft utilities) that a restore point is ready *slightly before*
  19. Hello! Today we completed a ton of testing on the new build of JRT. This initial testing went well and we have one more round scheduled for tomorrow. If that goes well, we should be able to get this deployed later in the day.
  20. Thanks for your feedback, @David H. Lipman. Our legal team is reviewing this and I'll share the details once we know more.
  21. Yeah, it's a System Restore issue. We now have more safeguards in place as well as messaging when it fails. JRT is working fine. We have a fix in place and we started QA testing this evening. Windows 10 version 1607 build 14393.222 is now included in our testing Assuming this goes well, we're targeting a new build to be deployed on Monday (10/3).
  22. We've updated our Terms of Use, Guidelines, and Privacy Policy. As you'll read, our Terms of Use and Guidelines are identical. We did this to streamline them and to help avoid confusion. Enjoy! Terms of Use: https://forums.malwarebytes.org/terms/ Guidelines: https://forums.malwarebytes.org/guidelines/ Privacy Policy: https://www.malwarebytes.com/privacy/
  23. Sorry for the late note back on this. We have pinpointed the issue and it's related to the System Restore API and it simply not working as it should be in both Windows 10 version 1607 build 14393.105 and .187. We are compiling a fix for this and hope to start testing it in-depth tomorrow. Other than sometimes not creating a restore point in Windows 10 version 1607 build 14393.105 and .187, JRT is working just fine. If you want or need a restore point created before using JRT, the workaround is still manually creating a restore point before using JRT.
  24. @Gt-truth - we do not have plans to update the UI of MBAR. Right now the technology in MBAR and MBAM 2.2.1 are at parity. Unless you have a specific need to run just our anti-rootkit technology, we recommend you use MBAM.
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.