on one of my machines (9586) Avast out of the blue deemed all or a potion of Lanatics VO.41 as a threat and disabled the program and sent it to the virus vault causing a large qty. (106) of compute errors. I have entered the program into the exclusion list which at this point fixed the issue and reloaded opt. apps. I have to assume that an update created this problem as I have used Avast for well over a year now without any trouble. I apologize to all the wing-persons affected

---

Report this directly to the lunatics as well as Plato.g here. Lunatics have their own support forum on the mean site.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Always exclude the BOINC- and also the BOINCDATA-directory from the virus scan. There is always the possibility of a virus scanner getting mad... :/

---

Aloha, Uli

I also have Avast and I also got the message a few days ago.

The thing is, in my case the problem is in the Lunatics executable.





On the other hand, it is file for ATI and I don't use ATI gpu so I could not care less.

---

This has been reported before and is known as a false positive.
Nothing we can do about it.

---

With each crime and every kindness we birth our future.

I have just (re-)uploaded the master copy of MB7_win_x86_SSE_OpenCL_ATi_r1843.exe from my development machine (used to compile the 64-bit installer, as shown) to https://www.virustotal.com/

The file is 918,016 bytes, and datestamped 11 May 2013 at 21:37:51 UTC.

The results of the meta-scan do show several warnings, one of them being from McAfee.com - but most of the reputable names in the AV industry show a clean report in VirusTotal.

However, the McAfee virus database does not contain the C53789ADE641 variant reported by VirusTotal, and a fresh scan of the same file by an updated copy of McAfee Security Center (AV engine version 1903.0, build 16.8.708) reports zero threats.

As Mike says, AV updates occasionally trigger false positives on existing files, until the signatures are fine-tuned by a subsequent update. Given that the file has been in widespread use here for over a year with no confirmed reports of malicious payload, my advice would be to re-scan the file after the next signature update of your chosen AV solution, just to be on the safe side, but take no further action beyond your usual vigilance.

on one of my machines (9586) Avast out of the blue deemed all or a potion of Lanatics VO.41 as a threat and disabled the program and sent it to the virus vault causing a large qty. (106) of compute errors. I have entered the program into the exclusion list which at this point fixed the issue and reloaded opt. apps. I have to assume that an update created this problem as I have used Avast for well over a year now without any trouble. I apologize to all the wing-persons affected

All is well with my issue concerning Lunatics/Avast but I really need to start proof reading my posts and utilizing spell check LOL

---