avast wont store a malware to chest do 2 storage space

is this related to the other problem? its a laptop with vista home on it. this is the malware Win32:Alureon-ER [Rtk]

edit, i updated it with the update provided in the other thread an it said avast home is already up to date

Why can’t it be moved to the chest (file in use, etc.) ?

  • If you have Win2k, XP, vista or Win7 (all 32bit), you could enable a boot time scan. Right click the avast icon, select Start avast! Antivirus, a memory scan will take place followed by the opening of the Simple User Interface, Menu, ‘Schedule boot-time scan…’ Or see http://www.digitalred.com/avast-boot-time.php. Don’t opt for deletion (you have no options left), always send to the chest and investigate.

Look in the C:\Program Files\Alwil Software\Avast4\DATA\report\aswBoot.txt file, check this file using notepad and copy and past the info on the detection.
Or use a command line, Windows, Start, Run and type, C:\Program Files\ALWIL Software\Avast4\sched.exe /A:*

It wont move to chest. I know how to scedual a boot scan. No matter what avast keeps saying file is too large to move to chest. all I can do is delete or no action so delete it is. but it just reroots it self in a new location. So I need help trying to get rid of this virus an malware. an it is vista home WIN:32

If the file is larger than the maximum file size to send to the chest, then you can change the settings.

From the avast Program Settings (right click the avast ‘a’ icon), Chest, increase the ‘Maximum size of file to be sent’ value to cater for the size of the file.

You didn’t say what the file name and location was ?

If it keeps coming back, there is likely to be an undetected or hidden element to the infection that restores or downloads the file again. What is your firewall ?

If you haven’t already got this software (freeware), download, install, update and run it and report the findings (it should product a log file).

Don’t worry about reported tracking cookies they are a minor issue and not one of security, allow SAS to deal with them though. - See http://en.wikipedia.org/wiki/HTTP_cookie.