Custom scan never finishes and high processor usagee

[TD351]

I have just did a clean re-install of Windows 10 x64 Pro and Malwarebytes 3(version 3.0.6). I can run a threat scan with no issues, but if I try to run a custom scan it will hang on a file and never complete. Since I've had prior issues with Windows 10 file system errors after updating a new install I ran a system file scan and found some errors that it wasn't able to repair, but was able to repair the file system using DISM commands. I also ran a chkdsk on the C drive and found no issues, so I'm confident that my system is not the issue.

I saw some other posts about people having similar problems, but never found a solution other than setting Malwarebytes to not scan archives. Is this still the case?

Also when I run a scan it uses 100% processor and this makes it difficult to multitask while doing so. I'm using a Crucial SSD with a budget friendly processor (Intel G3258) that doesn't have hyperthreading, so I'm not sure if that may be my issue or not. It would be nice if there was a way to reduce priority of scans to help with this, but maybe there's another solution?

Thanks for your time.

Edited January 28, 2017 by TD351

[1PW]

Hello @TD351 and

Thank you for your report.

1.) Please help to complete all the needed information that may have been initially missed using: How to Report a New Issue.

2.) Please attach (do not compress/copy/paste) the output diagnostic report mb-checkReport.txt from mb-check-{version}.exe. 

After all the requested data is posted, the Malwarebytes' QA & Developer Teams, and staffers can commence their analysis.  Thank you always for your assistance.

[TD351]

Hello 1PW,

Thank you for your reply. I apologize for not including that information before. Having worked tech support, I should have known better.

I've not had any system crashes and am using Windows 10 x64 Pro, version 1511, build 10586.713. I came across the issue after re-installing Windows and can reproduce the issue by doing a custom scan of my C: drive or all drives and have reproduced this issue 3 times now. I have attached the logs and the mb-checkResult as requested.

Thank you!

logs.zip

 

mb-checkResult.txt

Edited January 28, 2017 by TD351

[1PW]

26 minutes ago, TD351 said:

I apologize for not including that information before.

 

Hello TD351:

No foul, no harm.  Please provide one additional data point at your leisure.  The next time you run an MB3 Custom Scan, please untick "Scan within archives" before the scan commences and reply to your topic with those results.  Thank you again for your time and co-operation.

[TD351]

I ran a custom scan with "Scan within archives" unchecked and again the scan hung and had to end task on MB3 to get it to stop.

I then updated my OS to Windows 10 x64 Pro, build 1607, version 14393.576 and tried another scan with "Scan within archives" unchecked and again it hung. I was able to reproduce the same results three more times. A threat scan still completes with no issues.

I'm a long time user of Malwarebytes, but I'm beginning to lose my confidence that this new version is actually protecting my PC. How can I verify that the real time protection is actually working? I went to  iptest.malwarbytes.org/ and the page loads and shows "If you are able to reach this page it means that IP protection is disabled on your machine". This concerns me. What other ways can I verify that the rest of real time protections is working? I have attached the mb-checkResult,txt and logs again since updating Windows 10.

Thank you for your time and assistance.

mb-checkResult.txt

logs.zip

Edited January 29, 2017 by TD351

[1PW]

Hello @TD351:

Thank you for updating W10 to the present day release level.

The second set of logs did show that the MBAMService was inexplicably stopped which could explain some aberrant behavior.  Please try a system restart and check for the correct state (running) of the MBAMService.  Then, if all else appears normal, try again browsing to http://iptest.malwarebytes.org and see if the expected "Website blocked" pop-up presents.  At this point, we should now allow Malwarebytes' staffers to analyze the data.

Thank you again.

Edited January 29, 2017 by 1PW

[TD351]

Hi 1PW,

I had went to bed, but woke up a little while ago and can't remember if I had done a system restart or not before trying to reach the http://iptest.malwarebytes.org the last time. Anyway, I have restarted my system, verified the MBAMService was running, that all real time protections are on, and have tried the iptest page again and get server not found this time. I had my router set to use OpenDNS servers but changed it to use my ISP's DNS settings and get the same result. Just in case I had not restarted my system before my previous reply I have attached the current logs and mb-checkResult,txt results.

Again, thank you for your help.

mb-checkResult.txt

logs.zip

[TD351]

Update:

I noticed that when doing a custom scan MB3 was hanging on files in the Windows.old folder so I deleted the old Windows installation(Build 1511) and custom scans now complete with no issues. So I guess this issue was of my own doing.

I'm still concerned about real time protection. The page does not load when going to http://iptest.malwarebytes.org/. Shouldn't I be getting a warming from MB3? How can I safely test the other real time protections?