Ensure that you have the latest virus signatures and try a 'Select folder to scan,' selecting the c:\program files folder.
I believe the MSWORKS one was a subject of an FP so best ensure you have the latest VPS version before the scan.
What is in the c:\program files\support\Detection folder (looks like language support files for Teenage Mutant Ninja Turtles) ?
If so I would suggest checking the file at virustotal and see if the detection is good.
You could also check the offending/suspect file at:
VirusTotal - Multi engine on-line virus scanner and
report the findings here the URL in the Address bar of the VT results page. You can't do this with the file securely in the chest, you need to extract it to a temporary (not original) location first, see below.
Create a folder called Suspect in the C:\ drive, e.g. C:\Suspect. Now exclude that folder in the
File System Shield, Expert Settings, Exclusions, Add, type (or copy and paste) C:\Suspect\* That will stop the File System Shield scanning any file you put in that folder.
If 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.
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, add it 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.
I don't know why the avast files couldn't be found, but I would suggest a repair of avast. Try a repair of avast. Add Remove programs, select 'avast! Anti-Virus,' click the Change/Remove button and scroll down to Repair, click next and follow. This has in the past resolved this out of sync issue between reported and actual VPS version.
