Jump to content

Recommended Posts

I've been using Malwarebytes for years, but just re-installed it on a clean Win7 installation after having things get a little wonky.

I'm aware of the usual speed of Malwarebytes, but my quick scan just clicked over the 10 hour mark for the initial scan. Is it possible that the initial scan is what is going slower? It has already found a few "objects" and I don't really want to uninstall & re-install if it's just a matter of changing some settings. I believeI have the most recent version [1.75.0.1300] and it updated immediately after install.

Suggestions appreciated.

 

Link to post
Share on other sites

Hi, Wolflingdaddy:

 

This is a VERY old thread.

Normally, it's preferable to start a new post for this sort of issue, as there would be little comparable (including the version of MBAM) from the original post until now. (The mod team will probably split off your post to a separate thread. :) )

 

Moreover, it sounds as if you are running Full scans?

FYI, Full scans are neither necessary nor recommended for routine use -- Quick scans are generally more than sufficient under most conditions.

More info here: What is the difference between the three scan types in Malwarebytes Anti-Malware?

 

Having said that, many factors will influence the time it takes to scan.

The number of files, registry entries, temp files; the number/size of archives (since version 1.75, MBAM now scans archives such as zip, rar, etc); hardware (e.g. amount of RAM, processor speed); software (e.g. conflicts with other real-time apps); file corruption; bad HD sectors; even malware.

There is more info >>HERE<<.

 

I'm not sure what you mean by "having things get a little wonky" - did you recently reinstall MBAM or Windows or both?

>>When you reinstalled MBAM, did you use the removal tool, as explained here: MBAM Clean Removal Process ??

>>Also, have you set mutual exclusions between MBAM and your antivirus - let us know if you need help with that?

 

If neither of these works to resolve your issue, please post back and let us know.

The next step will be to collect some basic system logs to help the staff to determine what the issue might be...

 

Thanks,

 

daledoc1

Link to post
Share on other sites

  • 5 months later...

Sorry it's taken so long to get back to this, but this is still relevant. Current version of MBAM running is 2.02.1012. Windows7HP SP1.

To answer most of your questions and to clarify...

 

I'm not sure what you mean by "having things get a little wonky" - did you recently reinstall MBAM or Windows or both? Yes, at that time I had reinstalled Windows and then MBAM.

>>When you reinstalled MBAM, did you use the removal tool, as explained here: MBAM Clean Removal Process ?? No, I did  not, just installed, updated and ran it. 

>>Also, have you set mutual exclusions between MBAM and your antivirus - let us know if you need help with that? No, I did not. I think I could handle that with a minimum of help. I'm not unfamiliar with all of this stuff.

 

I don't see any options about quick or full scans. I see Threat and Custom. Then there is Hyper, which is greyed out, probably because I haven't purchased the Premium.( If I can get these bugs worked out, I would be willing to purchase the software.)

 

 

 

 

 

 

This is a log from the only scan that has completed. Note that it took over 41 hours.

 

Malwarebytes Anti-Malware
www.malwarebytes.org
 
Scan Date: 4/6/2014
Scan Time: 5:02:16 PM
Logfile: mbam_040614t.txt
Administrator: Yes
 
Version: 2.00.1.1004
Malware Database: 
Rootkit Database: 
License: Free
Malware Protection: Disabled
Malicious Website Protection: Disabled
Self-protection: Disabled
 
OS: Windows 7 Service Pack 1
CPU: x64
File System: NTFS
User: TEST
 
Scan Type: Threat Scan
Result: Completed
Objects Scanned: 1478506
Time Elapsed: 41 hr, 14 min, 13 sec
 
Memory: Enabled
Startup: Enabled
Filesystem: Enabled
Archives: Enabled
Rootkits: Disabled
Heuristics: 
PUP: Enabled
PUM: Enabled
 
Processes: 0
(No malicious items detected)
 
Modules: 0
(No malicious items detected)
 
Registry Keys: 2
PUP.Optional.InstallCore.A, HKU\S-1-5-21-2588673942-1388852986-2506477935-1000-{ED1FC765-E35E-4C3D-BF15-2C2B11260CE4}-0\SOFTWARE\INSTALLCORE\1I1T1Q1S, Quarantined, [fc5f31f5ef8ca591aa39cda092706c94], 
PUP.Optional.InstallCore.A, HKU\S-1-5-21-2588673942-1388852986-2506477935-1000-{ED1FC765-E35E-4C3D-BF15-2C2B11260CE4}-0\SOFTWARE\INSTALLCORE, Quarantined, [0754f036e794d85ec1605d2736cd04fc], 
 
Registry Values: 1
PUP.Optional.InstallCore.A, HKU\S-1-5-21-2588673942-1388852986-2506477935-1000-{ED1FC765-E35E-4C3D-BF15-2C2B11260CE4}-0\SOFTWARE\INSTALLCORE|tb, 0W1S1S2Z1N1F0S2Z1J1B1O, Quarantined, [0754f036e794d85ec1605d2736cd04fc]
 
Registry Data: 0
(No malicious items detected)
 
Folders: 0
(No malicious items detected)
 
Files: 6
PUP.Optional.Installcore, C:\Users\Stephen Wolf\AppData\Local\Temp\HomePageDLL.dll.89271010, Quarantined, [a3b8121458230036426b9b573cc77e82], 
PUP.Optional.Conduit.A, C:\Users\Stephen Wolf\AppData\Local\Temp\is1275519350\89049890_stp\sp-downloader.exe, Quarantined, [68f3a77f94e79e98aa623dd812effa06], 
PUP.Optional.Conduit.A, C:\Users\Stephen Wolf\AppData\Local\Temp\e4j10AE.tmp_dir1390874482\user\mism.exe, Quarantined, [9dbe28fe5526c76fc36e1e01966af808], 
PUP.Optional.Conduit.A, C:\Users\Stephen Wolf\AppData\Local\Temp\e4j539.tmp_dir1390874938\user\mism.exe, Quarantined, [88d370b63d3e50e647eab768768add23], 
PUP.Optional.Conduit.A, C:\Users\Stephen Wolf\AppData\Local\Temp\e4j623.tmp_dir1390874414\user\mism.exe, Quarantined, [b4a727ff611ac472de538f9027d9e719], 
PUP.Optional.Conduit.A, C:\Users\Stephen Wolf\AppData\Local\Temp\e4j772D.tmp_dir1390874049\user\mism.exe, Quarantined, [0853081eb4c7bc7a8aa7c65919e7e41c], 
 
Physical Sectors: 0
(No malicious items detected)
 
 
(end)
Link to post
Share on other sites

A few things I just did/noticed. Windows7 build7601.

I did add exceptions to for both the program [just the exe] and the folder containing quarantined/infected files mutually for both my a/v [AVG Premium] and MBAM.

I downloaded the mbam-clean file, but haven't run it. I did notice that I appear to have two installations of MBAM on the computer. I didn't look into the details of that.

Link to post
Share on other sites

Hi:
 
Welcome back.
 
I think things might be a bit mixed up. :unsure:
This topic was started back in EARLY MARCH 2014, when MBAM was still on version 1.75.
In LATE MARCH 2014, MBAM 2 was released, with many changes both in the user interface (GUI) and under the hood.
 
So, my reply to you back then doesn't apply today, to the new version.
The scan types were renamed in version 2, & there are many changes to the features and settings and dashboard.
 

"Flash" is now "Hyper"
"Quick" is now "Threat"
"Full" is now "Custom"

Hyper scan is available only to paid, PREMIUM users and is not routinely needed or recommended -- if anything is found, a subsequent Threat scan will be needed anyway.
THREAT scan is the most important and most useful scan -- it is the one that ought be run on a regular basis (daily is the default setting now in 2.0).
Custom depends on what drives, folders and files are selected -- routine use of a "full" system scan is neither necessary nor recommended, as it's a task better suited to your antivirus.

As far as scan times, version 2.0 is more powerful and more thorough than version 1.x.
Scans may take a bit longer -- that is normal and nothing to worry about.
Leaving antirootkit (ARK) scanning disabled and disabling archive scanning can shorten scan times a bit.
There are many other factors that determine scan times.

It also appears that you did start a similar topic for a similar problem a few weeks ago >>HERE<<. :)
At that time, our forum Admin suggested posting back with some basic diagnostic logs.
That would be the same advice today.
These logs will help us to better help you with your issue.

EDIT: That scan log you posted is from several months ago, and shows an older version of MBAM (as well as at least PUP infections).
So, let's see where we are today. :)
Please read the following and post back attached to your next reply the 3 requested logs - Diagnostic Logs (the 3 logs are: FRST.txt, Addition.txt and CheckResults.txt)
 
Thanks,

Link to post
Share on other sites

  • 3 weeks later...
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.