Free Version Commandline Changes

[sbwhiteman]

Using the free commandline version, before version 1.45 it was possible to run an update and have it terminate without user intervention after the update (mbam /runupdate). Is it no longer possible to do this?

Thank you.

[RubbeR DuckY]

Because the scheduler requires the same command line parameters we had to remove support for that.

mbam.exe /update

It is still supported in the free version, as are many other various command line parameters.

[sbwhiteman]

Because the scheduler requires the same command line parameters we had to remove support for that.

mbam.exe /update

Is still supported in the free version, as are many other various command line parameters.

Thanks RD for the quick reply.

Just so I'm clear, using the commandline free version (and the Windows Task Scheduler) one used to be able to automatically update and have the program terminate (mbam /runupdate) and then run a quick scan (mbam /quickscanterminate), all without user intervention.

Now, after mbam /update, the user must intervene to either close the program or run the scan. If after updating, a scan is run by the Task Scheduler, you receive the error message that "Malwarebytes is already running."

So is there now no way to automatically update then run a quick scan, without user intervention, in the free version?

Thanks.

[dwnld99]

I agree,

I

[htplbc]

Because the scheduler requires the same command line parameters we had to remove support for that.

mbam.exe /update

Is still supported in the free version, as are many other various command line parameters.

What other command line parameters were changed? And it was /fullauto one of those.