Protection settings not sticky

[Samoreen]

Hi,

Using Malwarebytes Pro (latest version) under Windows 7 Ultimate 64-bit as a complement to ESET NOD32 antivirus. So I don't need/want to activate the Filesystem protection option. However, it is automatically re-enabled when I reboot the system.

 

Bug or feature ?

 

--

Patrick

[daledoc1]

Hi, Samoreen:
 
Welcome.
Disabling the file protection module of MBAM PRO pretty much defeats the purpose of running MBAM PRO.
Doing so would disable one of the main protection components designed to prevent your system from becoming infected.
MBAM PRO is specifically designed and tested to run "real-time" alongside all of the major, popular antivirus (AV) programs, in order to catch the type of zero-hour and zero-day threats the AV might miss.
Having said that, some users find it helpful to set mutual exclusions between MBAM and their AV -- we can assist you with doing that.
 
If you really want to disable the file protection feature and it's not staying disabled upon system reboot, I'm not sure if that is a bug or not.
We'll need to wait for a staff member to weigh in.
While we are waiting, please run the following scanners and post back here with the resulting logs attached to your next reply.
They will help the staff to determine what might be going on.
 
Thanks,
 
daledoc1
------------------------

DDS-MBAMCHECK-FRST

STEP 1
Please run the DDS scanner and send back both logs as attachments to your next reply.

>>>If you are running Windows 8.1, please skip this step.

Download DDS from one of the locations below and save it to your Desktop:
dds.scr
dds.com

Temporarily disable any script blocker if your Anti-Virus/Anti-Malware has it.
How To Temporarily Disable Your Anti-virus, Firewall And Anti-malware Programs

Once downloaded you can disconnect from the Internet and disable your Ant-Virus temporarily if needed.
Then double click dds.scr or dds.com to run the tool.
Click the Run button if prompted with an Open File - Security Warning dialog box.
A black DOS console should open and run for a moment.

• When done, DDS will open two (2) logs:
  • DDS.txt
  • Attach.txt

• Save both reports to your desktop
• Please include both of the following logs in your next reply as an attachment: DDS.txt and Attach.txt
• You can ignore the note about zipping the Attach.txt file and just post it or attach it.

STEP 2
Please run mbam-check and send back the log as an attachment to your next reply.

• Download mbam-check.exe from HERE and save it to your desktop
• Double-click on mbam-check.exe to run it, it should then open a log file
• Please do not copy and paste the entire contents of the log into your next post; instead please attach to your next reply the CheckResults.txt log file which should now be located on your desktop.

STEP 3
Please run the FRST tool and send back both logs as attachments to your next reply.

Download Farbar Recovery Scan Tool and save it to your desktop.

Note: You need to run the version compatible with your system. If you are not sure which version applies to your system, download both of them and try to run them. The one that runs will be the right version.

• Double-click to run it. When the tool opens click Yes to disclaimer.
• Press Scan button.
• It will make a log (FRST.txt) in the same directory the tool is run. Please attach it to your next reply.
• The first time the tool is run, it makes also another log (Addition.txt). Please attach it to your next reply.

[Samoreen]

 

MBAM PRO is specifically designed and tested to run "real-time" alongside all of the major, popular antivirus (AV) programs, in order to catch the type of zero-hour and zero-day threats the AV might miss.

 

In which case I will keep the filesystem protection option active if this doesn't affect performance which usually happens when double checking executables. If you tell me that it's not the case, it's ok for me. No need to bother anyone with this. But the option is not sticky and the development team can reproduce this any time.

[Samoreen]

In which case I will keep the filesystem protection option active if this doesn't affect performance which usually happens when double checking executables. If you tell me that it's not the case, it's ok for me. No need to bother anyone with this. But the option is not sticky and the development team can reproduce this any time.

 

This might be related to the "Start protection module with Windows" option. I guess that if it is enabled, MBAM will disregard the state of the 2 protection options.

[daledoc1]

This might be related to the "Start protection module with Windows" option. I guess that if it is enabled, MBAM will disregard the state of the 2 protection options.

 

Yes, I believe that is probably the case.

 

We'll need to wait for staff to verify that.

 

BTW, as I mentioned in your other post, MBAM is undergoing significant updating with a new version, 2.00, due out of beta testing soon.

I don't think that there will be any significant changes to the consumer version of 1.75 moving forward.

So, if you have suggestions for new/improved features, it might be a good idea to post them in the new beta section of the forum >>HERE<<.

If you do post there with a suggestion, I would just be sure you make it clear that you are still running 1.75 and are proposing a suggestion for 2.00.

 

Thanks,

 

daledoc1