Free addition of Avast finds adware and suggests I move it to the Chest. I do that, then after the scan is complete I get the Actions list telling me Avast could not move the Adware to the Chest. Why not?
What is the infected file name, where was it found e.g. (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. C:\Program Files\Alwil Software\Avast4\ashLogV.exe
avast will give the reason if it can’t be moved, etc. what reason was given (file in use, unsupported operation, etc.) ?
I suggest a boot-time scanning (maybe files are in use or access is blocked).
See also: http://www.digitalred.com/avast-boot-time.php
Thank you for answering so quickly! I apologize for not doing the same. The files are Win32:Adware-gen C:\System Volume Information.…\ctbr.dll. The first time I ran into this the error code(failed attempt to put in Chest)was 12. I ran it a few days later and this time the error was the Chest was full. I took care of that problem and have not had one since. In other words it is still finding the adware but now they are in the Chest. Can these files be deleted?
Thank you,
Jeff
First the chest full is a bit of a misdirection in this case, as it isn’t likely to be full there is another consideration and that is the file is larger than the maximum file size to send (Program Settings, Chest). So you can adjust the sizes or in this case it shouldn’t be an issue to delete it when it is next detected by avast (though don’t get in the deletion habit, it should always be investigated before any deletion).
My opinion of any suspect file in the C:\System Volume Information folder is it is better in the chest than to find in the future if you use system restore you could be infecting your system.
The ctbr.dll is however associated with the crawler toolbar and that has been in the past considered adware.
Do you mean that running avast at boot time you couldn’t send the files to Chest?
If a virus is replicant (coming and coming again), you could follow the general cleaning procedure:
You can disable System Restore on Windows ME, XP or Vista. System Restore cannot be disabled on Windows 9x and it’s not available in Windows 2k. After disabling you can enable it again and create a clean restore point.
System Restore cannot be disabled on Windows 9xIf I'm not mistaken, System Restore wasn't available in Win 9x ???
Absolutely right, it wasn’t on win98 (winME yes). However, by default the quote is true, you can’t disable what you can’t enable as it isn’t installed ;D
Thanks for the correction Bob 
I just didn’t want a new user to start looking for something that doesn’t exist. ;D