It is indeed a false positive - ESET tends to flag all of our new builds (which is reasonable because of us being a security program which does make some pretty low level modifications ) You can probably just add it to the internal ignore list for now - this is just RC1 so it will only be seen by a small number of users and probably isn't worth submitting yet as there will be changes in the next few RC rounds.
If you were the first Prevx user in the world to install a new version of Eset a millisecond after it was released Prevx would throw up a FP on the Eset too.
A note on this: we do have measures in place to prevent FPs on legitimate software like ESET but Threedog is correct in saying that brand new versions (i.e. if ESET were to completely overhaul their product so that we would be unable to see that it is similar to a previous version) would generally be flagged. We don't mind that other AVs detect our components. In the interest of full disclosure, we actually detected some of our new secure browser components automatically (and I'd be worried if we didn't) The changes which security products make to the system are near-impossible to differentiate from actual malware and vendors tend to be willing to accept a few FPs for significantly improved security provided by heightened heuristics around system modifications.
Ummmm I've excluded all 5 or 6 directories from scanning and it will NOT let it install meaning Prevx rc1 NOD is preventing after excluding and restoring etc.. Any Ideas please?
Tyvm Triple and one more question if you don't mind? Since Nod av has its own protection module did you have to put prevx from high back to minimum or standard? I am on Vista hp 32 Btw, usual install for prevx puts at minimum because of other security protection modules.. Thanks in advance and again ty for helping.