Recently (as of 9/23/09), my AVG Free Anti-Virus has been saying that my Diablo II.exe is a trojan virus. It is the first time that has ever happened and I have not tampered with the file in a month. I am thinking that today's AVG update caused some kind of conflict with the .exe but am not sure. I have done many fresh reinstalls but to no avail. Would anyone happen to know what is going on?
Cheifaxe
USWest
1. Re: Diablo II.exe... a trojan? 09/23/2009 04:12:48 PM PDT
Yup same here..... I'm guessing it's a problem with AVG if you tried reinstalling and got the same error. I was putting off the reinstall fix cause I'm lazy. This happened to me once before where AVG was saying WoW was a virus.... might have to get rid of it again.
Joeycrack514
USEast
2. Re: Diablo II.exe... a trojan? 09/23/2009 04:13:11 PM PDT
yo me too i just got this problem today!!!!!!!!!!!!!! i go to play, and my diablo 2 errors up immidatley and avg deletes it and says its a trojan.. i tried re installing 3 times , ignoring the trojan, healing it with avg ect... nothing is wroking... it keeps just saying theres a backdoor trojan or osmmething like that from my AVG.
Datth
Blizzard Poster
3. Re: Diablo II.exe... a trojan? 09/23/2009 04:42:50 PM PDT
It looks like an AVG update flagged some of Diablo 2's files as a trojan. It seems to be a false positive but you'll want to check your executable's modified date to make sure it didn't get changed today. If it's older, it's fine. If you reinstalled, patched or restored the game today, you'll have a modified date of today so the checking-the-date idea won't apply in those cases.
So what is a solution to this problem, I've tried everything under my cpu to fix it. I've looked all around AVG's website and they dont have anything about contacting them without paying 1oo plus bucks.
Bird2811
USEast
5. Re: Diablo II.exe... a trojan? 09/23/2009 07:04:00 PM PDT
How is it that every time people have a common problem, you don't have it?
Five or so people having the issue makes it common? Thousands(?) of people get restricted on an hourly(?) basis. That is a common problem.
EDIT: After updating my virus definitions (Last update was yesterday?) and rescanning, it flags it for me as well. Looks like all we can do is wait for AVG to update that.
I managed to bypass the error by opening my AVG Anti-Virus, double clicking the Resident Shield option, and turning it off (unchecking "Resident Shield Active" box) the OR click on Manage Exceptions > Add Path and link it to your Diablo II directory (so your path will be as such: C:/Diablo II NOT C:/Diablo II/Diablo II.exe). This will cause AVG to overlook all files in that directory.
Sixen
USWest
13. Re: Diablo II.exe... a trojan? 09/23/2009 10:12:28 PM PDT
Well, also I've found I can't host again today. and i know how to forward the ports, I've done it before and it's forwarded correctly.
Is it possible that this avg thing could be messing that up too?
I guess it's a possibility, but I doubt that the two are related. Do you have a Static Internal IP?
Q u o t e: Originally posted by Matrix121391
I managed to bypass the error by opening my AVG Anti-Virus, double clicking the Resident Shield option, and turning it off (unchecking "Resident Shield Active" box) the OR click on Manage Exceptions > Add Path and link it to your Diablo II directory (so your path will be as such: C:/Diablo II NOT C:/Diablo II/Diablo II.exe). This will cause AVG to overlook all files in that directory.
Well, I wouldn't suggest the user completely have AVG overlook the d2 directory. If they use some kind of third party mods/programs that happen to contain viruses, then they would be in the d2 directory and not be found. Perhaps just adding the executable and not the entire path.
Go to Tools > Advanced Settings > PUP Exceptions > Click "Add Exception"
EDIT: I've made an informative thread for any users that are going to come asking about this tomorrow...
http://forums.battle.net/thread.html?topicId=20140804515
[ Post edited by Sixen ]
The Chat Gem Lives!
http://www.Sixen.org/
Datth
Blizzard Poster
16. Re: Diablo II.exe... a trojan? 09/24/2009 08:13:29 AM PDT