Bitdefender and RtW2

[unspacy000]

I use Bitdefender for my anti-virus protection.

When I downloaded v1.00, I had no problems.

I updated directly to v1.02, managed to get through everything, and after about a week Bitdefender decided that RtW2 was suspicious, needed to be quarantined, and deleted. Since it looked like the only issue Bitdefender raised was the trustworthiness of the program's creator, I restored it all and put and exception on it.

I recently downloaded and unzipped the v1.03 update. I ran the .exe, and Bitdefender stopped it. Bitdefender failed to delete it or something since it's still on my desktop, and it has given me this message:

Successfully blocked infected file

19 minutes ago



Feature:

Antivirus



The file C:\NWS\Rule the Waves 2\RTW2.$$A is infected with Gen:Variant.Graftor.600768.The threat has been successfully blocked, your device is safe.

I'm trying to figure out if this is an actual virus or just Bitdefender complaining about RtW2 being updated by its mysterious, untrustworthy creators, but all the information on Gen:Variant.Graftors seem to be how to remove them style help guides rather than what they do.

[garychildress]

I have Webroot anti-virus software and it's having issues with RTW2 also-only it says it's detecting some sort of adware program in it (adware.gen or something like that). Apparently most programs are fine with RTW2 but we're the lucky ones who's virus programs are acting up over it. I sent a support ticket to Webroot and hope they'll clear up the problem one way or another. I'm interested in hearing the outcome of their analysis (they had me run a log collection program to send them the relevant info on the issue). Anti-virus software can be a real PITA sometimes!

[williammiller]

Unfortunately Bitdefender and Webroot are the two anti-virus engines that seem to have issues with RTW2 on a regular basis...we locally scan the game files w/multiple AV engines before release - however we also upload them to VirusTotal as well, and typically 0-2 AV engines will show a false positive out of about 70 different AV engines used in the scan.

Ive sent samples to each AV engine that gave a false positive, but when we get a new update released some of them again re-flag it...sigh..so it's a never-ending cycle: release->reflagged!->send sample again->repeat.