Author Topic: OPENFAN.EXE (Read 3054 times)

Saxifrage · « **on:** November 14, 2006, 05:33:13 PM »

avast 4 deems this as a virus, but not until today.... have had avast for about 1 year)
It's a program for silencing my cabinet fan.
My gut reaction was to put it in the chest, for later restoration(which I did), but after restoration I haven't got the administrative rights to run the program anymore...
(I have admin rights)

This is the scan of the file openfan.exe from within the chest:

Scanning of selected files

Action was completed successfully!

Virus has been detected!
File Name: openfan.exe
FileID: 9
Virus Description: Win32:Small-CPI [Trj]

Has It suddenly been infected, or is it something with avast 4?
Btw, there aren't any other probs with my machine. It's always very tightly run.

Saxifrage from Denmark

DavidR · « **Reply #1 on:** November 14, 2006, 06:34:30 PM »

Ensure you have the latest VPS version, there has been one released recently and check again.

You could also check the offending/suspect file at: VirusTotal - Multi engine on-line virus scanner
Or Jotti - Multi engine on-line virus scanner if any other scanners here detect them it is less likely to be a false positive. You can't do this with the file in the chest, you will need to move it out.

If it is indeed a false positive, add it to the exclusions lists (Standard Shield, Customize, Advanced and Program Settings, Exclusions) and 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 Standard Shield and Program Settings, exclusions.
Also see (Mini Sticky) False Positives, how to report and what to do to exclude them until the problem is corrected.

Saxifrage · « **Reply #2 on:** November 14, 2006, 07:18:25 PM »

tHX DavidR
- Ultra fast responce, i'm glad.

Solved my problem nicely.

DavidR · « **Reply #3 on:** November 14, 2006, 08:44:28 PM »

No problem, welcome to the forums.

Which part resolved the problem, update VPS or confirmation it is a false positive and adding it to the exclusions ?

Saxifrage · « **Reply #4 on:** November 14, 2006, 09:17:19 PM »

Hi again.

It was the latter that clinched it.

Saxifrage

DavidR · « **Reply #5 on:** November 14, 2006, 11:58:52 PM »

OK, if you send it to avast (as in the False Positive link) so they can analyse it and correct the VPS.