virus found in the DivX Connected™ Server 1.4.0 Build 54 Beta
Hi,
my anti-virus (avg) found a virus (Trojan horse Generic11.UYS) inside of DivxConnected.exe file,
is it a reel virus ?
even if i close my AVG, windows vista don't allow me to execute it ...
it said you don't have permission... (im full admin...)
version DivX Connected™ Server 1.3.1 Build 10 can be installed without problem...
thanks
Dominic
or the older .54 version?
The 1.4.0.59 should not be tripping the warning. Let me know if it is.
Final version just solved it.
My Avast also detected a virus yesterday and I freaked out thinking something else infected DivxConnected.exe hehe... I forced an update and re-installed the Server software and everything seems cool...
To force an update, open avast! (go to Start Menu> All Programs> avast! Antivirus> avast! Antivirus) then Tools> Updating and do both iAVS Update and Program Update.
You could add an exception to the folder scanning in the AV software...
Why don't you release it? Is it that unstable?
The fact that those running AVG cannot run 1.4 is an issue that sucks.
1.4 is just too cool...
Hoping that you will release the solution, very soon...
Thanks.
We have found that AVG and NOD32 were detecting a "phantom" trojan horse virus that did not really exist in our software. NOD32 has since issued an update which no longer flags our 1.4.0.54 beta server. Our newest build does not trigger AVG's anti-virus. We will test any new builds against these programs before releasing them so this should not be an issue in the final update.
The type of virus scan that is being done in these cases is an aggressive heuristic method that attempts to identify unknown potential viruses based on patterns in the code.
That type of virus detection is not 100% accurate. In order to be effective at identifying new viruses, it must sometimes flags programs that do not have viruses.
We have run the same scan on our latest build and it does not detect any viruses. The changes that we made to the code were very minor bug fixes.
We have submitted our executables to the virus scan company and are awaiting their reply, but our engineers are certain that this is false positive.
We will ensure that the next beta or production release will not cause this issue.
Me too. Avast quotes a Trojan from today.
I have Avast too. And it found virus on early vers. but now i have update it and now is no problem.
Stopping on-access protection for the 30 seconds it takes to load DIVXConnected.exe works in the interim. Don't forget to restart anti virus!!
Strangely my Avast didn't report it until yesterday too - one thing was that it did catch a real virus from a separate source just prior to this, so I've been assuming it's the learning heuristic that's causing problems - why some people are getting it and some aren't. Some code in Connected must be too similar to something inside some real virii, so once it's been exposed it looks for this chunk - and gets it wrong.
Fingers crossed they put it on the whitelist soon - or we get another build that changes it slightly yet again, and it gets out of the spotlight ;-)
Robin
I use Avast and was having the same problem until about a week ago and it stopped detected the server as a virus.
Well, it recently started detecting it as a virus again.
What now?