Apup 1.05 and McAfee
james.faction
02 Oct 2008
McAfee antivirus decided to detect 1.0.5 as a "generic dropper" and delete it.
My solution: Disable McAfee while running the updater.
This is more of a workaround than a solution.
I have since been able to add apup.exe to the exceptions list for our organisation. Again though, this isn't ideal, although it works.
Edited by james.faction, 02 October 2008 - 03:16 AM.
My solution: Disable McAfee while running the updater.
This is more of a workaround than a solution.
I have since been able to add apup.exe to the exceptions list for our organisation. Again though, this isn't ideal, although it works.
Edited by james.faction, 02 October 2008 - 03:16 AM.
James
02 Oct 2008
Thanks for the report.
It is especially irritating that McAfee do not check their updates against APUP before releasing them.
(Source: http://www.siteadvis...autopatcher.com)
--
It is especially irritating that McAfee do not check their updates against APUP before releasing them.
McAfee SiteAdvisor, however, still says we are clean.
Quote
In our tests, we found downloads on this site were free of adware, spyware, and other potentially unwanted programs.
--
Cristiano
03 Oct 2008
i've tested apup 1.0.5 with mcafee viruscan 13.0.218 DAT 5397 engine 5200.2160 and i don't see that issue
[]s
[]s
