Goetia Posted June 26, 2014 ID:846571 Share Posted June 26, 2014 Before MalwareBytes Anti-Malware 2.0, threat scans would normally take 8-30 minutes to complete. However, as of the update, scans now consistently get caught on single files, and scans are taking longer and longer to complete. Scans went from taking one to two hours to complete to three, and now this scan has been going on for four hours and thirty minutes. Please help me, my computer is old, and I cannot have intensive programs like MBAM take up valuable memory for extended periods of time. Thank you. Link to post Share on other sites More sharing options...
daledoc1 Posted June 26, 2014 ID:846590 Share Posted June 26, 2014 Hi and : First: Multiple factors contribute to scan times.These include:Size of diskDisk typeDisk speedDisk cachingCPU speedController type and speedOperating System usedAmount of files (including temp files!)Amount of foldersAmount of archived files such as zip, rar, sfx, etc. (if this is enabled)Rootkit scan or not (if this is enabled)PUM/PUP scansOther security programs running at the same time that may potentially be monitoring all file accesses by any other process.Drive integrity - if a drive is failing it can take a long time to ignore and bypass sectors on a disk or simply fail period and hang the scan.Other ongoing disk I/O processesSystem being infected can also affect speed of scansAlso note that changes in the MBAM database can also cause scan times to increase or decrease, so that's another factor to consider.Sometimes a conflict with your antivirus may be possible as well. You may want to try adding exclusions in your AV - the files that need to be excluded can be found HERE. Let us know if you need more help with that. Next, sometimes slowdowns are not due to conflicts between MBAM and the AV, per se, but rather to older hardware, insufficient RAM, cluttered disks, excessively tight security settings, or other factors. You might want to have a look at this FAQ article >>HERE<< to see if the steps there resolve your issue. Next, you might want to disable both archive and rootkit scanning, to see if that improves things -- let us know if you need help changing those settings. If none of these resolves your issues, routine troubleshooting would start with these steps:Please uninstall your current version of MBAM and reinstall the latest build - MBAM Clean Removal Process 2xIf that does not correct the issue, then please read the following and post back the 3 requested logs - Diagnostic LogsNOTE: There is an FAQ section with valuable information located here - Common Questions, Issues, and their SolutionsThanks, Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now