Scan failed with error code: 8

[Steve_Shields]

I have a user that has malwarebytes pro installed and updated to the latest version. When she runs a scan it gets all the way to heuristics normally, then it blazes through them in the blink of an eye (normally they take the longest) and gives the attached error. I tried uninstalling and reinstalling, and it has nothing to do with the root kit. I could not find anything on google that matches that exact error. Please advise.

 

 

[John L. Galt]

Hi,Steve_Shields, and
 
I know that you said you tried uninstalling and reinstalling, but please try using the removal tool in step 1 below to see if that might clear up the issue.

• Please uninstall your current version of MBAM and reinstall the latest version. MBAM Clean Removal Process 2x
• If that does not correct the issue then please read the following and post back the requested logs. - Diagnostic Logs
• NOTE: There is an FAQ section with valuable information located here: - Common Questions, Issues, and their Solutions

Thank You

[Steve_Shields]

John,

I know it's been a while but the cleaner had worked for a time. However one of the users I ran it on is getting the error again. I have attached the requested logs. Thank you for your help.

Addition.txt

CheckResults.txt

FRST.txt

[Steve_Shields]

Any ideas guys?

[1PW]

Hello Steve_Shields:

 

I am only marginally qualified to open/read your attached CheckResults.txt file, and although the re-installation of MBAM 2.0.2.1012 was properly re-activated to the Consumer-Premium mode, no indications are present that the associated databases were ever updated since re-installation.

 

Thus posing the question if a subsequent Threat Scan would again encounter a true "Scanner Failed with Error Code: 8" event?

 

An imminently more qualified Malwarebytes staffer will soon join this thread.

 

Thank you.

[Steve_Shields]

1PW She said everytime she tries to run the scan that error pops up. Can anyone help with this issue? Please and thank you.

[Ried]

Hi Steve,

 

As we are now working together in the HelpDesk, I'll close this thread.