Cannot start a scan while another one is already in progress.

[JoeyG]

1. Brief description of the issue.

When I right-click any file to scan it with MWB 3.0.6.1469, I get the message seen in the screenshot every time.

2. Any screenshot(s) of error messages ...

Attached

3. If the system crashed, ...

No. I can close the error message and everything's fine. Scheduled scans or "Scan Now" requests (from the main interface) work fine.

4. Operating System Details

Windows 7 Professional SP 1 x64. It generally works fine, and - by the way - I can do a right-click scan with my Norton Internet Security v. 22.8.1.14 just fine.

5. Details on how you encountered the bug and any steps that can be taken to reproduce it.

See number 1.

6. Do you get the same result more than once if you follow the same steps?

Yes, I get the error message every time.

7. A copy of the contents of C:\ProgramData\Malwarebytes\MBAMService\logs in a ZIP file.

Attached.

Thank you for your help.

P.S. Is there any way to reset the "Scan Detections" line on the Dashboard back to 0? Thanks.

logs.zip

[dcollins]

If you click the scan tab on the left side, what does the screen say?

[JoeyG]

Thanks for your reply.

Is this what you mean? (See attachment)

[dcollins]

Yep, this is most likely the left over result from a scheduled scan (there's a default 2am scan that will run). Clicking close on this scan result will allow another scan to start. I'll pass this along to our dev team

[JoeyG]

Yes, it did. Thanks very much.

[drtgnmstr]

I am having the same problem on Windows 10 but the correction does not help.  I still can not scan an individual file.

I tried starting a threat scan and clicking close when it completed but that did not help.

[drtgnmstr]

I found that by changing MBAM.exe to "run as administrator" seems to have taken care of the problem.

 

[dcollins]

@drtgnmstr that shouldn't be necessary, but glad to hear you got it working. If you have a moment, can you walk me through what steps you were using to see this issue?

[drtgnmstr]

Quote

 

dcollins,

I would open file explorer and right click on any file or folder, then select "scan with Malwarebytes".  Then the message pops up.

Frank

[Porthos]

@dcollins To add this bug happens to me as well. Easy to reproduce just let a scheduled scan run and then try to do a right scan on any thing.

24 minutes ago, drtgnmstr said:

I would open file explorer and right click on any file or folder, then select "scan with Malwarebytes".  Then the message pops up.

 

[dcollins]

2 minutes ago, Porthos said:

@dcollins To add this bug happens to me as well. Easy to reproduce just let a scheduled scan run and then try to do a right scan on any thing.

 

Yep, but opening up Malwarebytes and clicking Close on the scan result window should allow the scan to continue.
 

@drtgnmstr is saying that doesn't work for them.

[Porthos]

2 minutes ago, dcollins said:

Yep, but opening up Malwarebytes and clicking Close on the scan result window should allow the scan to continue.

Yes it does let the scan work after closing that leftover window for me. It only manifests on explorer scans. It does not affect the next scheduled scan.

To me its just an annoyance/bug.

[dcollins]

Just now, Porthos said:

To me its just an annoyance/bug.

Me too We have noted this situation and it's being reviewed

[Porthos]

2 minutes ago, dcollins said:

Me too We have noted this situation and it's being reviewed

I usually do my right click scans with the VirusTotal extension.

Edited March 13, 2017 by Porthos

[drtgnmstr]

It just seems strange that the earlier workaround was not working for me but changing to run as administrator did.

As Porthos said it is mostly just an annoyance and I seem to have gotten around it.

 

[deltam]

I can confirm this is a problem. I use the context menu to scan an individual file all the time and for the past month I've had to exit Malwarebytes and reload it in order to do a scan. I finally just did a search to see if anyone else was having the same problem. According to Malwarebytes dashboard, there is no scan in progress.

[dcollins]

@deltam while there may not be a scan in progress, if you open up Malwarebytes and click on Scan on the left side navigation, what screen do you see?

[drtgnmstr]

I see the select a scan method screen

[solveunow]

Just signed up with the forum so that I can reply to this.

I have the same "another scan is in progress" or such.  Using the Start Menu and running Malwarebytes [AS ADMIN] works without exiting Malwarebytes for me.  But this is a PITA.  Sometimes I'm receiving/transferring files on remote computers and need this to work, don't have time for this crap.

Also since I'm paying for this SERVICE yearly (not sure if this is an issue also with the free version) I need to know that this will work along side my other protection.  Was getting ready to contact Malwarebytes until I saw this thread & also the ADMIN worked for me.  I've also been having an issue (sorry, wrong thread, just throwing this out anyway) of Malwarebytes using crazy processor/CPU power but on 2 of my units - never figured it out so just reset the both of them.

[deltam]

On 3/26/2017 at 0:30 PM, dcollins said:

@deltam while there may not be a scan in progress, if you open up Malwarebytes and click on Scan on the left side navigation, what screen do you see?

If I click on SCAN within Malwarebytes, it does start a scan. I can then cancel it and do a right-click scan on a file. Or exit Malwarebytes and restart it, then I'm able to right-click for a file scan. But, the pattern it seems is that after every scheduled scan (which runs daily - and is a default setup from Malwarebytes) I can not right-click and run a file scan. However, after resetting Malwarebytes (exit and restart) AND prior to the scheduled scan, I'm able to right-click scan.

[solveunow]

When I right-click on a file/folder it sometimes tells me "another scan in progress" or such.  I didn't do anything but exit that specific window, go to Start and then select Malwarebytes [right-click, run as ADMIN] exit out of the Malwarebytes window, and then select my file/folder to scan...  and it works.

BTW:  Win10x64Pro, fresh install about a month ago because Win10 isn't the best for my old equipment.  But is mostly working AOK except for MS Win issues.  I also sometimes have problems that MB doesn't update automatically but not sure if this is MB or WIN?

[Jamustin]

I'm having the same problem with Win10/64bit. It used to work to close out after a scan, sometimes just opening MAB was enough. Now that doesn't work. Running as admin did nothing. The only thing that worked to reset it for me was going into Services and restarting MAB from there. Hope a fix can happen soon.

[dcollins]

When you see this issue, can you please follow the instructions to grab your service logs. Since these logs have a lot of information, if you could let us know approximately what time you tried to start a scan, that would help as well.

1. Navigate to C:\ProgramData\Malwarebytes\MBAMService
   • The ProgramData folder may be hidden. You might need to turn on showing hidden files/folders or type the path manually.
2. Right click the logs folder and choose Send to -> Compressed (Zipped) folder
   • This will create a file on your desktop named logs.zip
3. Upload the logs.zip file

[deltam]

Devin, I did a context right-click scan on a zip file named: svg-support.2.3.7.zip around 11:55PM (MST) that failed due to the same error this thread is about. Something changed in Malwarebytes as this has never happened before. I was always able to right-click and do a scan. I use it all the time. I'm not sure when it started but it always fails (see my reply on March 28). There's a pattern to it.

logs.zip

[dcollins]

@deltam was that on 4/6, just to confirm?

And just to help clarify the known situation we are looking at resolving. When you get this message, if you open Malwarebytes and go to the Scan tab, you may see the following screen. This is caused by a scheduled scan running, and no action being done on Malwarebytes since then (IE: haven't opened it and then dismissed the box). We are looking at ways to resolve this.