My OS: Vista U
I installed a virtual machine(Virtual PC 2007) in my OS and this program created 2 new file named *.vhc and *.vmc.
What a pity!
??? ??? ???
Avast delete these files without any prompt tone!!!
So many important files in my Virtual machine!
How did avast delete a file without the “caution a virus has been detected!”?^^
-AnimeLover^^
avast doesn’t delete or take action autonomously, it scans and alerts to infection and the user has to choose what action to take.
The only exceptions to that would be if you have the avast Pro version, and then you would have to set up what action you want to take on detection.
Having important files in a virtual environment is no different to having important files in a normal environment, if you don’t want to loose them you have to back them up.
No, avast does not take automated actions with the Home (free) version.
Edited: David was faster.
Thank you all and may be I clicked the wrong choise when the first “caution a virus has been detected” show.
You’re welcome.
but I still have a question that why Avast! think the virtual machine file as a virus?
It just a big file.
My be the Avast team need to make some efforts to avoid the mistake.
If the file was infected by a virus, how can I repair it?
The virtual file is somewhat large and complex and I guess it is possible that a string could match a signature. Many suggest that you exclude the virtual drive file from on-demand scans, which presumably was when this was detected ?
It is also possible that there might have been a virus in the virtual environment, the problem is that the actual image is one file when scanned by the on-demand scanner so it can’t differentiate from a file within a virtual drive image.
You could add the following “.vhc" and ".vmc” (without the " quotes " ) to the avast Program Settings, Exclusions, Add, see image. That would exclude those file types the wildcard * means you don’t have to name the file or folder or drive they are in.
Avast delete those files which are infected by virus
check you VPC to make sure it is normal
I think there is a big problem in you VPC ,not in Avast
forgive my poor English… ;D