Malwarebytes 3.0 stuck scanning filesystem.

[CRUCIAL]

When I attempt to run a custom scan on Malwarebytes 3.0 the scan always stops on the same file. The stopped scan can not be paused and Malwarebytes can not be closed with ending the task and still will stay running, only fix is to restart PC.

A regular threat scan does not stop and "No Threats are Found". No other issues on PC. New PC build, new installation of Malwarebytes so there shouldn't be any issues. The options I have selected for the Custom Scan are:

Scan Memory Objects

Scan Startup and Registry Settings

Scan within archives

Scan for rootkits

Treat Detection as malware

 

The scan stops on this file in the filesystem on my C:/ drive:

C:\USERS\CRUCIAL\APPDATA\LOCAL\MOZILLA\FIREFOX\PROFILES\QPPLGRA.DEFAULT\CACHE2\ENTRIES\E8E87163C21785BD2FBAFC0793350B2E28A1233A

 

It seems to be a file related to Mozilla Firefox. There seem to other instances of Malwarebytes stopping on scans of the filesystem, is this a bug or possibly an infection? If I cannot scan for rootkits and scan the filesystem then my system is not protected as Malwarebytes claims. Unfortunately I don't have much experience in this field so it will be difficult for me to troubleshoot this issue any further on my own.

 

 

[TheThornWithin]

I am NOT an expert. Only answering because no one else has. But I do know this:

The file you are seeing displayed on your monitor is typically not the actual file that Malwarebytes is "stuck" on.

Are you are running a Custom Scan? If so, does that include scanning within archives and for rootkits? Try disabling those two options and rescan.

[Telos]

@CRUCIAL It s recommended to periodically clean your Firefox cache. To do so:

Recommended settings after cache cleaning...

Sometimes the cache just gets too large. This may help your pc browser performance as well as your MBAM scan issue.

[Firefox]

At times the scans get stuck due to data corruption on the hard drives.  You can try running a chkdsk on the hard drive in question to see if that clears up the issue.