I am running Windows 7 Ultimate Service Pack 1, 3.10GHz, 2.00 GB RAM.
Usually it’s speed is pretty good until recently it started to run really slowly, so I performed a few scans, one in Malware Bytes, which detected and successfully removed them. I also ran scans in Avast Ant-Virus Free, which detected a number of viruses also, however was unable to remove them all, as for many it simply didn’t give me an option to do so, and as you can see the list is quite long, all below what you can’t see are 'error: archive is password protected:
Hi So… Did you notice:
Process 3376 is mbam, residing in memory. I’m pretty sure that “men|” would expand to “memory”. What avast is detecting are signature strings that mbam is using. No cause for worry, but you should not have another antivirus resident when running a scan. Stop mbam, and avast will not detect those strings anymore.
The remainder are compressed files that are password-protected. Since avast does not know the passwords, it’s telling you it can only see gibberish in them. But, I must admit, I do not know if avast would know how to open .dds and .lua files if they are not password-protected.
zulu does not detect anything here; Google search provided a link to this site with only one result.
I suggest submitting the two above files to virus total dot com here: https://www.virustotal.com/ where 40+ virus scanners will have a look at them.
As they were found in the Recycle Bin, question is, did you put them there? Paste the resulting url’s from each scan in your reply. You can restore these files (copy/paste) from quarantine in malwarebytes to your desktop to submit, throw away when done.
I see the mbam database version is from 5/12/2012, out of date in any case.
I stopped MalwareBytes and did the scan again, and it still picked them up.
because you have selected "scan memory" and if you search the forum you find a million cases
unless you have some special need or know something the avast guys dont know… use the default scan settings
so do not use the “scan memory” setting and problem is gone
files that can not be scanned, are just that, does not mean they are infected
avast is juste reporting a scan error and the reason why, no more no less