First I have the full version of Internet Security 7. I have a license that covers 2 pc’s. The problem I’m having is on my desktop.
I have the Full Scan set to run nightly. I have the scan set to delete first and then move to the chest if it can’t be deleted. The past 2 nights, it has found 9 files that appear to be various types of malware. Avast doesn’t appear to be deleting the files or moving them to the chest. Is there some setting somewhere that I neglected to turn on to do this? When I check the log, the files are showin in red. It doesn’t appear that any action has been taken.
Do I have to highlight the items in the log file and manually delete them? Or should it be automatic?
After the scan>>click on scan logs tab>>click on the show log>>select action>>hit apply>>and then wait for a few seconds and see if it performs the action select or not…
dont forget to give us the name of infections found on next post…
Deletion isn’t really a good first option (you have none left), ‘first do no harm’ don’t delete, send virus to the chest (a protected area) and investigate.
I’ve attached a .jpg of the scan log. I tried to highlight any of the files in the list and I couldn’t. The default action is ‘move to chest’. But since I couldn’t highlight anything, the apply button is always grayed out/not available.
Detections in Memory -
My guess is that you are doing a Custom scan in which you have elected to scan Memory and that all these detections are in memory or are listings of files that can’t be scanned. Since they aren’t physical files they can’t be moved to the chest, deleted, etc. so there is no action that can be taken, hence the Apply button being greyed out.
The detections in memory are frequently other security applications loading unencrypted virus signatures into memory. Having set off a scan of memory by an antivirus application looking for virus signatures, don’t be too surprised if it finds some in memory.
The first group are detecting MBAM signatures in memory.
The locked files you can do nothing about, the decompression bomb, again nothing to do or worry about.
Decompression Bomb, a file that is highly compressed, which could be very large when decompressed. This used to be a tactic long ago to swamp the system, also see:
Also see this very old reply from one of the avast developers.
[quote author=igor link=topic=8943.msg73950#msg73950 date=1100877654] A decompression bomb is a file that unpacks to an enormous amount of data - thus “flooding” the unpacking engine. It’s quite hard to detect such files reliably, so it’s possible that it gives some false alarms oca
Yes, I understood the locked files and the bomb messages that aren’t actually anything to worry about. My concern was the files marked as a virus or trojan. It looks like it is actually Malwarebytes Anti-malware sofware that it’s finding. I ran a quick scan of that and noticed the log file was mbam-something. Made me go ‘hmm’. Anyway, thanks for your help.
It isn’t malwarebytes that it is saying is infected as such, just that it the Process responsible for loading the unencrypted virus signatures into memory.
Also if you happen to have the MBAM interface open it loads mbamswissarmy.exe I believe and this too loads signatures into memory.