http://img519.imageshack.us/my.php?image=avastviruses1hc2.png
All the 'Unable to Scan: Decompression Bomb’s and the ‘Unable to scan: The system cannot find the path specified’
What do I do? Do I delete them all? I have no clue what they mean…
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, see http://forum.avast.com/index.php?topic=8943.msg73950#msg73950
See http://forum.avast.com/index.php?topic=35347.msg297170#msg297170 this topic for more information on why files can’t be scanned.
Files that can’t be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned.
Are you running a dual boot system as seeing windows in the E: drive is a little strange when there is a system volume information folder in c: ?
I don’t know if that might have something to do with the not found issue.
I have a 200 Gig C: and an 80 Gig E:, which is a slave to my 200 Gig. So I can let the decompression bombs stay? Or should I delete/repair them/do something else?
Yes but it is strange to see windows on a slave drive and doesn’t answer the question about dual boot ?
The term decompression bomb is really a poor one that is a throwback to the 80s and just means that it is highly compressed file format and to be scanned it has to be unpacked and that would create a very, very large file/s if it were to be unpacked and that is all, do nothing with them.
Umm…I didn’t know how to answer the dual-boot as I have no clue what that is. I have a friend of mine do everything for me. And while scanning on my screensaver just now, it found a virus in the same decompression bomb as one on that list…
I’m doing a boot-scan tonight, and probably a thorough scan tomorrow when I go play Fable II for a long period of time, so we’ll see what happens.
Firstly, if it isn’t scanning the decompression bomb file being reported as ‘unable to scan’ as in your last post how could it be finding a virus inside a file it isn’t scanning ?
Please post the details of the detection, malware name, file name and location, e.g. (Malware name, C:\windows\system32\infected-file-name.xxx) ?
Check the avast! Log Viewer (right click the avast ‘a’ icon), Warning section, this contains information on all avast detections.
OK, outside of dual boot it would be highly unusual to have the Windows folder not on the C: partition/disk. Since you are totally in the dark about dual boot (different versions of windows installed, like XP and Vista, etc.) I would think that it isn’t setup as a dual boot, which only make the location of Windows in E: more strange.