Some uninstall functions will get pinged, simply because of what they do and this remove.exe. The win32:CIH actions filled the first 1024 KB of the host's boot drive with zeros and then attacked certain types of BIOS.
So I don't know exactly what remove.exe does, as some removal tools may overwrite what was removed, but I rather doubt that it is a good detection, given the low number of hits on the VT Results and Prevx calling it a 'Medium Risk Malware' which is at odds with the severity of win32:CIH. Other than prevx only avast and gdata detect anything (counts as one), see below.
http://en.wikipedia.org/wiki/CIH_%28computer_virus%29If only GData and avast detect it - GData uses avast as one of its two scanners so counts as 1 detection and almost certainly an FP.
Even though Pondus has sent a sample, I would say you should also - Send the sample to avast as a False Positive:
Open the chest and right click on the file and select 'Submit to virus lab...' complete the form and submit, the file will be uploaded during the next update.
- In the meantime (if you accept the risk), add the full path to the file to the exclusions lists:
File System Shield, Expert Settings, Exclusions, Add and avast Settings, Exclusions Restore it to its original location, periodically check it (scan it in the chest), there should still be a copy in the chest even though you restored it to the original location. When it is no longer detected then you can also remove it from the File System Shield and avast Settings, exclusions lists.
