Has anybody else been having problems with McAfee and their ClamWinP ??
For a couple of weeks now McAfee has been finding a virus in :
ClamWinPortable\Data\db\daily.inc\daily.ndb
and keeps quarantining it.
Now, before anyone jumps on me 
1. I am sure that ClamWin is NOT infected with a virus and I am not reporting it as such, I am sure it is a false positive.
2. I am sure this is a problem affecting ClamWin, not just CWP.
It is detected as "New Script.c"
I think the file has something to do with ClamWin "unpacking" its updates.
Is anyone else seeing this?
Who should we tell and how?
My thought would be that it should be brought to the attention of the Clam/ClamWin people so they could verify and then notify McAfee.
Anybody know who to contact?
I've waited before asking this because I thought someone else would report it and it would get cleared up. But it occurs to me that since ClamWin is so slow that I probably use it more than anyone else.
I update it at least once a day and run it at least every other day.
I have seen this situation on 3 machines (1 home, 2 at work) all fully patched XP machines w/ VirusScan 7.1
Suggestions?
Tim
(\__/)(='.'=)(}>
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
It's technically a mcafee issue as it's detecting in another antivirus products definitions files. This is actually relatively common when you have multiple antivirus products. Anti-spyware apps have this issue, too.
I can't test mcafee (I stopped using it years ago when it got as bad as norton with bloat) so I can't confirm what you're seeing, but I'm guessing it's the issue I mentioned above.
Sometimes, the impossible can become possible, if you're awesome!
Thanks for the reply John, and for not jumping on me
My question would be how to do it?
Do you [or anybody else] know if McAfee has an "easy" procedure for saying "Your product "X" is finding a false positive in product "Y"'s file "z". Could you please fix this?"
I really don't like getting into multi email back and forth conversations with big companies. My hope was if there was an easy way to let Clam know they could pick up the ball and run with it. This is one area where I'm feeling a little lazy and want to just exclude the file from McAfee's detections.
Tim
(\__/)(='.'=)(}>
Things have got to get better, they can't get worse, or can they?
Is there some whay to have it exclude searching that directory from searching?
"... respect, all good works are not done by only good folk. For here, at the end of all things, we shall do what needs to be done."
Don't be an uberPr∅. They are stinky.
Consul,
Of course I could exclude the directory or even the file in question, in fact I mentioned that in my reply. But that does not solve the problem.
I have just discovered over at the ClamWin site that others are having the problem as well.
http://forums.clamwin.com/viewtopic.php?t=1217
However the tread seems to have ended at the end of July and the problem is still here. I'm going to send them a message to that effect.
And I'm still trying to find a way to send a False Positive Report to McAfee, yes, I'm SEARCHING
Tim
(\__/)(='.'=)(}>
Things have got to get better, they can't get worse, or can they?
I'm seeing the exact same thing on a public machine running VirusScan 8.0i.
---
"The fact that an opinion has been widely held is no evidence whatever that it is not utterly absurd; indeed in view of the silliness of the majority of mankind, a widespread belief is more likely to be foolish than sensible."
-- Bertrand Russell --
---
The fact that an opinion has been widely held is no evidence whatever that it is not utterly absurd; indeed in view of the silliness of the majority of mankind, a widespread belief is more likely to be foolish than sensible. Bertrand Russell
You will continue to see this until McAfee fixes their issues. Nothing can be done on our end.
Sometimes, the impossible can become possible, if you're awesome!
It appears that for the moment McAfee has fixed the issue, dat 5098 is no longer finding a problem with ClamWin
Tim
(\__/)(='.'=)(}>
Things have got to get better, they can't get worse, or can they?