I'm still getting FPs from Nod32 v4 with PrevxEdge. This is to do with the old sig files included with the current builds. I have several times had to contact Prevx on behalf of my customer to get a new Prevx licence because Nod32 has zapped the program. Nod32 is getting to be a lot of trouble.
I'm getting 0 false positives on the latest clients, but you've been told numerous times what the solution is.
He is prob doing a remote install via remote desktop. The version of ESET on the site is the problem. He probably downloads ESET, fires off an INSTALL, once ESET starts up, it gobbles up what's running before updating itself. So in his case, the ESET download version should be updated to address those FP's.
The situation is exactly as GrammatonCleric describes. I don't really appreciate the tone of your reply elapsed. Are you an Eset employee, or maybe a school teacher used to dealing with 5 year olds?
I'm not trying to be harsh, but as you know we are all here voluntarily, and I want to help people, I don't see why someone should be told the same answer 5 times. But in this case I'll take it back since it's different, there's nothing you can do in this situation, you just need to make sure eset is updated before doing anything. The best way to do that is to reboot straight after installing then the login update schedule should kick in. Either that or when the next build comes, make sure to install that one (updated sigs). Yes but you're not going to get the kind of support from phoning them/emailing them. They are paid for that support.