|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
virus on download!
i just downloaded the client and on instal my virus checker said it found a trojan in the infa red dll...
anyone else having probs? |
#2
|
|||
|
|||
My virus scanner reported a virus (one which google has no info on, basically seems to not actually exist) in the averapi_182.dll today, which I believe is a false positive after having scanned my entire system with antispyware/adware/virus software, as well as heuristics checkers. I simply set it on the exclude list and all is well again. My guess is you're encountering the same issue, but with a different file.
|
#3
|
||||
|
||||
I am running Avast! as my anti-virus program. Shortly after Avast! updated itself today (Jan 25, 2006) it deteted a virus in the file averapi_182.dll. The virus detected is Win32:Sinmsn-D [WRM]. Acording to the Avast! program this is a worm. I cannot however find any information regarding this virus/worm, even on the Avast! website (other than the fact it was added to the most recent signature set).
I have found that this file is very important to both SageTV and the client. I am not posting this to start a virus/worm scare. I suspect the A/V program is falsely detecting this file as malware (it can happen). I am curious if this has happened to anyone else. Even more so if your using a different A/V product. I did delete the averapi_182.dll file and replace it by rerunning the SageTV install. The file tiggered the A/V program again during the install. I am running Windows XP Media Center Edition (SP2) and SageTV 4.1.x. Thanks THe virus/worm name was Win32:Sinmsn-D [WRM]. I also could not find any information on this virus. I am using using Avast! as my A/V |
#4
|
|||
|
|||
Quote:
Jeff |
#5
|
|||
|
|||
Yep, that's the program I'm running too (Avast!), exact same "trojan" detected after today's VPS update. I believe it is a false positive.
|
#6
|
|||
|
|||
Yup. Same here. Avast seems to be hitting a false positive.
|
#7
|
||||
|
||||
e-mailed Avast about virus/worm detection
I e-mailed Avast (support@avast.com) about the recent update to the VPS detecting the averapi_182.dll file as a virus/worm. I don't know if or when they wll reply but I will pass on any reply I may get.
I didn't try to exclude the file last evening when this problem began to occur. I did try to exclude the dll this morning and it was still detecting it when I would start the SageTV application. I was doing this in a bit of hurry, so I will double check my efforts again when I have more time to do so. |
#8
|
|||
|
|||
Interesting. Since I deleted the file yesterday, and reinstalled sage 4.15 beta, I am now getting a Java exception error in the ...infrared...dll file (don't remember the exact file name) and sage client won't load. Its a access denied error to the file. The sagetv service is running fine and recording ( I know because the directory is filling up with new shows)... I am puzzled what to do next...
Jeff |
#9
|
|||
|
|||
Quote:
Dirk |
#10
|
||||
|
||||
Hello,
Same problem here. I let avast reboot and run a bootscan and sure enough it declared the above mentioned file as a virus/worm. I had avast put the file "in the chest". I am hoping when I get home this evening I can have it reinstall the file from the chest so as to avoid reinstalling sage. Anyone know if this is possible, or will I definitely have to do a full sage reinstall? In any case I will be sure and put this file on the exclusions list. Jesse |
#11
|
|||
|
|||
You should be able to either A) restore it from the chest, or at worst, B) run a "repair" version of the setup program (just run it with Sage installed still and disable avast! during the install, click repair option, and it will fix Sage *WITHOUT* destroying your settings) like I did .
|
#12
|
||||
|
||||
Thanks GT.
Jesse |
#13
|
||||
|
||||
That could be Avast's heuristics going overboard. I've seen it do it before for several other sorts of software... there was no virus whatsoever but it thought there was.
|
#14
|
||||
|
||||
I didn't get much of a reply from Avast! other than they will give the information I sent them to the developers. I did notice that Avast did have another update out this afternoon that so far seems to have solved the problem with averapi_182.dll being detected as an infected file.
Appearently my efforts to exclude the offendind file from Avast! were actully successful. I tried starting Sage (before I applied the new VPS) and it started OK without a virus warning. I removed the exclusion for the dll file after I applied the new VPS update and everything seems to work fine, so far. Just like before. Yeah, I got some kind of Java error after I moved the dll file to the chest. I also deleted it from the chest. To restore SageTV, I reran the install file and chose the repair option. It worked fine but I still had Avast! running and it triggered the virus warning during the install. This is the first time I've had a problem with Avast!. I have helped clean many infected machines with Avast! and it has always done a fine job. It even caught stuff other AV products didn't. |
#15
|
|||
|
|||
Quote:
I've used Avast! for about 10 months and this is the first false-positive it has detected on my machines or any of my friend's/family's PC's. A small annoyance, but the program is great, and it's free to boot! |
#16
|
||||
|
||||
Quote:
|
#17
|
|||
|
|||
I've run avast for a couple years now... this is the FIRST false positive I have had...
Jeff |
#18
|
|||
|
|||
WOW .. TY .... TY ... Tahnk You.
You guys are "the bomb" as the kids say. I was going nuts cuz Sage no longer would install. Searched the above *.dll and Voila. Since I am a firm user of Avast I assumed that was the problem. Cannot say if, when or how it happened but I did the repair on Sage reload and all is well. Once again thx for these great forums. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|