The actual file you are loking for is 9aa425.msi, a windows installation file and the detected file (binary,vista.vbs) is within that archive file and I believe the problem is that avast can't extract the suspect/infected file from within the .msi file without possibly corrupting it.
You don't say what the error was when you couldn't move or delete the file, I suspect it was something like this is an unsupported file type, or words to that effect ?
The file name is certainly a weird one, 9aa425.msi which looks like it was randomly generated as there are zero hits on google for that file name. I would have expected for an installation file more hits would have been returned.
A search for the binary.vista.vbs, does bring some hits which tend to indicate this is a good detection, See
Binary_vista_vbs information and a google search
http://www.google.com/search?q=Binary.vista.vbs.
So to me I would say that the detection is good but the only real option is to place the 9aa425.msi in the avast chest (or delete it but I hate deletion, no more options left):
You can add the file to the User Files (File, Add) section of the avast chest (if it isn't already there) where it can do no harm and send it from there.
A copy of the file/s will remain in the original location, so you will need to take further action and can remove/rename that.
Send it from the User Files section of the chest (select the file, right click, email to Alwil Software). It will be uploaded (not actually emailed) to avast when the next avast auto (or manual) update is done.
####
There is more you may need to do to clean up after this installation:
Program & Tutorial - Also useful as a diagnostic tool -
FileHippo Download - HiJackThis and post the contents of the HJT log file here. - HJT Information
HiJackThis Tutorial.
Download and run HJT and post the contents of the log file (cut and paste or attach the log file) into this topic, you may need to split it over two or more posts depending on how large it is.
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.