Scan already in progress issue

[Pat_inUK]

I have the same problem with a clean install of the latest build, following use of mb-clean.

For what it's worth, it's the only problem I have with Malwarebytes but as it's a function I've previously used a lot, it's a bit disappointing.

[Pat_inUK]

Thank you, but let me clarify a bit. It worked with
Malwarebytes version: 3.0.6.1469
Component package version: 1.0.96
Update package version: 1.0.1771

It does NOT work with
Malwarebytes version: 3.0.6.1469
Component package version:  1.0.103
Update package version: 1.0.1771

Although, to be honest, I'm totally confused.  If I look in Settings/About, it gives a different Component Package Version from a scan report conducted later. For instance, Settings/About states Component Package Version 1.0.103, but the report of a scan conducted just now states package version 1.0.96

Screenshots attached to show what I'm wittering on about!

[Porthos]

1 hour ago, Pat_inUK said:

but the report of a scan conducted just now states package version 1.0.96

That scan shows the date of scan 3/30/17. Try again

[Pat_inUK]

ooops - sorry! Every time I sort the reports to list newest first, they revert to oldest first when I take another look. However, at the time, one computer still had 1.0.96 and on that I could scan an individual file. It's since auto-updated to 1.0.103 and I still can. Time for another clean install on the computer (my main one of course!) that's being awkward, I guess.