Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Malwarebytes 3.0 with Local Security Policy - Software Restriction

  • Please log in to reply
1 reply to this topic

#1 gluino


  • Members
  • 4 posts
  • Local time:07:46 AM

Posted 30 December 2016 - 03:34 AM

After following the "How to create an Application Whitelist Policy in Windows" guide by Lawrence Abrams, using Windows Software Restriction Policies (SECPOL SRP).

On my Win10 system, in "Additional Rules", there were 2 pre-defined path rules, which were the ENV VARs for SystemRoot and ProgramFilesDir, as expected, and I added a 3rd path rule: "C:\Program Files (x86)" as recommended and eventually a 4th path rule: "c:\Users\myname\AppData\Roaming\Dashlane" in order for Dashlane to work properly.


But then I noticed that the sys-tray commands HIDE / OPEN Malwarebytes did not work when the Application Whitelist was in effect.


Do I need to add another path rule so that MBAM 3.0 will work normally?


Also noticed that MBAM always shows a start up toast notification warning "One or more Real-Time Protection layers are turned off.", if TinyWall is in normal mode.  It doesn't happen when TinyWall is in AutoLearn mode.  And after AutoLearn, it does not help TinyWall allow MB3 to start without the warning.  I might just uninstall TinyWall.

Edited by gluino, 30 December 2016 - 03:35 AM.

BC AdBot (Login to Remove)


#2 quietman7


    Bleepin' Janitor

  • Global Moderator
  • 51,953 posts
  • Gender:Male
  • Location:Virginia, USA
  • Local time:06:46 PM

Posted 31 December 2016 - 10:22 AM

You may want to ask in the Malwarebytes 3.0 Support Forum so the development team can investigate and correct the problem.

The Malwarebytes Tech Support & Help Forum team know the inner workings of the program and have direct access to the developers and research engineers. Your best option is ask and wait for them to figure out what is going on.
Windows Insider MVP 2017-2018
Microsoft MVP Reconnect 2016
Microsoft MVP Consumer Security 2007-2015 kO7xOZh.gif
Member of UNITE, Unified Network of Instructors and Trusted Eliminators

If I have been helpful & you'd like to consider a donation, click 38WxTfO.gif

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users