This content has been marked as final. Show 31 replies
The trusted list is more for Windows applications and what are commonly called PUP's (Possibly Unwanted Programmes) and you can't in fact ask VirusScan to ignore an object it finds as an infection.
We are hoping that feature will be re-introduced sometime very soon, but can't promise anything as it's only a rumour.
You can, however, submit the file to Avert and hopefully they will send you an extra.dat to cover the detection.
In order to do that you would probably first have to disable VirusScan, then submit the file.
Double-click the taskbar icon to open Sec. Center
Click Advanced Menu (bottom left)
Click Configure (left)
Click Computer & Files (top left)
Disable VirusScan in the right hand module and tell it for how long.
Reinstate the files using the Restore tab on the left.
Then submit your files:
Send a file to Avert for analysis:
Email file to: [EMAIL="email@example.com"]firstname.lastname@example.org
When submitting samples via E-mail all samples must be packaged in a .ZIP file. When creating this .ZIP file, it is important to understand that the .ZIP can be no more than 3 megabytes in size and can contain no more than 30 files. Additionally, any .ZIP file created must be password-protected using the password "infected" (minus the ""). Failure to follow these guidelines will cause your submission to be rejected.
How to Install an Extra.DAT
Thanks for the steps. Currently the alternate steps are fine with me. I would try to send the file and get an extra dat .
My sons favorite online game made an update the other week and now one of the .DLL's is being flagged as a virus (trojan -a). As per your comment, I sent the file to webimmune, but they came back and confirmed that its is a virus (I don't think so - I suspect the vendors last update made it look like it could be). How do I add the program to the trusted list now as it looks as if I can't get a additional extra.dat file
Follow the steps above. There is no way to add to a trusted list in the home edition.
In my case its was ok, beacuse I disabled the virus scan for 15min, recovered the file which was flagged by mcafee as PUP, installed it and then reactivated the viruscan.
But in case of dmatth2, its unsafe to deactivate the viruscan engine and play online games. So here I really feel that McAfee products are very tightly coupled and cannot be configurable as per the user needs...
So I would hope that Mcafee prodcucts being really good and trusted, would also become more configurable and would also bring down their non-compatability list, in the future releases.
It's the subject of many a complaint from us Moderators, believe me. The last I heard was that they were considering re-introducing that ability to the home products.
Thanks .That is what is required...we need to keep on telling the same thing untill its heard by the other end.
And not only Program adding to the trusted list...this is somewhat ok because if its really a virus the user should also not be allowed to add it...thats where the safety is... sometimes I saw that ppl allow the virus themselves and then complain... my system is gone...
But then in that case we should not display the trusted list as such that the user thinks that they can do some customization on that. Believe me I have spent more than an 1 hr to add a program to list before posting the query in this forum.I think a list of Do's and dont's should be added to the user guide.
But I would like to focus more on the Compatibilty side...you know once i searched in google "IE 8 compatibility" and to my surprise 90% of the links spoke abt McAfee not compatible...I could see a list of products with witch Mcafee is Incompatability. And that is growing day by day. A really good product should not have so much of restrictions...i feel.
Anyways I still feel McAfee can outshine among others with a little bit of tweaking..so please try to forward these concerns to the appropriate person.
When IE8 is final, McAfee will be ready. Not much point in being compatible now only to get it broken the next beta version, which is what happened with beta 2.