Hi, as my colleague stated in your support ticket:
I have personally checked FindOnClick using Avast AntiVirus, Comodo AntiVirus, Norton AntiVirus, and McAfee AntiVirus, and all give FindOnClick a clean bill of health.
If you believe NOD32 is correct and everyone else is wrong, then that is your choice. If you really believe there are never any false positives and that anti-virus companies are infallible, then that is your choice. We know there is no virus and you can believe us or not. There is nothing else we can do except submit the file to NOD32 for analysis and inform them they've made a mistake (which we've already done) and repeat once again that we are 100% absolutely positive that there is no virus.
As for the inconsistent naming convention, that is perfectly normal. It's simply a temporary filename given to the file by the installer. The installer moves the file to the correct folder and renames it once it's copied all the files to the drive (so you can rollback the installation if it fails because it hasn't yet replaced the files). The file itself is FindOnClick.exe. There is nothing suspicious going on here.
Why is FindOnClick causing a fuss? It's not, NOD32 is. My guess
is that FindOnClick is using a technique they believe some viruses use (or may use). What technique? I don't know and it doesn't provide details. All I know for sure is we don't write or spread viruses, FindOnClick is not a virus, and it does not contain a virus.