L
Lucvdv
How is AVG's response when something like this is reported?
Where do you best report it?
Not finding a report page on their web site or a better e-mail
address, I sent a renamed copy of the falsely detected file by mail to
(e-mail address removed).
No response yet, but I only mailed it a little over 24 hours ago.
I just started trying out AVG antivirus, and in my first scan I
immediately found no less than FOUR issues:
1) A false positive
2) Copies of the same file were sometimes recognized as a virus,
sometimes not, apparently depending on their location.
This is an OCX file I'm using in software projects, it deleted all
copies it found in the project setup folders, while leaving the copy
in windows\system32 alone.
3) It didn't move the (falsely) detected copies of the file to the
vault, but simply deleted them without any warning.
4) When I tried to mail a new copy of the same file out after
temporarily disabling disk file checking and outgoing mail checking
(leaving only incoming mail scanning enabled), it moved it from the
outgoing mail to the vault when I clicked "Send".
The file is called SMTP.OCX, a somewhat older version of an SMTP
engine that's been available for years (http://www.ostrosoft.com/).
AVG detects it as I-Worm/Holar.
The real I-Worm/Holar *does* drop a file with the same name, but
according to MacAfee's virus database that file is only 1/4 the size
of the one AVG detected on my system.
Googling for "AVG false positive" I found a web-forum message where
someone accuses AVG of "finding" many more viruses than its
competitors, because it finds so many false positives.
Is there any truth to this?
Anyway, if it kills files just because the filename is the same as
that of a file dropped by a worm, while the version dropped by the
worm isn't even viral if taken on itself, I don't think AVG is the
right scanner for me.
Where do you best report it?
Not finding a report page on their web site or a better e-mail
address, I sent a renamed copy of the falsely detected file by mail to
(e-mail address removed).
No response yet, but I only mailed it a little over 24 hours ago.
I just started trying out AVG antivirus, and in my first scan I
immediately found no less than FOUR issues:
1) A false positive
2) Copies of the same file were sometimes recognized as a virus,
sometimes not, apparently depending on their location.
This is an OCX file I'm using in software projects, it deleted all
copies it found in the project setup folders, while leaving the copy
in windows\system32 alone.
3) It didn't move the (falsely) detected copies of the file to the
vault, but simply deleted them without any warning.
4) When I tried to mail a new copy of the same file out after
temporarily disabling disk file checking and outgoing mail checking
(leaving only incoming mail scanning enabled), it moved it from the
outgoing mail to the vault when I clicked "Send".
The file is called SMTP.OCX, a somewhat older version of an SMTP
engine that's been available for years (http://www.ostrosoft.com/).
AVG detects it as I-Worm/Holar.
The real I-Worm/Holar *does* drop a file with the same name, but
according to MacAfee's virus database that file is only 1/4 the size
of the one AVG detected on my system.
Googling for "AVG false positive" I found a web-forum message where
someone accuses AVG of "finding" many more viruses than its
competitors, because it finds so many false positives.
Is there any truth to this?
Anyway, if it kills files just because the filename is the same as
that of a file dropped by a worm, while the version dropped by the
worm isn't even viral if taken on itself, I don't think AVG is the
right scanner for me.