NB Sagetvservice.exe detected as a trojan Feb 04, 2017

[Galaxysurfer]

hi,

Just did a fresh install of win10 pro & loaded SageTVSetup_9.0.13.536_R1.010.exe downloaded from sagetv forum link to bintray.com after replacing my expired ESET with KIS 2017. Unfortunately KIS has determined that sagetvservice.exe is PDM:In32.Trojan.Generic. not sure if it is a falseflag or not. Will try reinstalling it. Scanned *.exe file & it came out clean. it wasnt till KIS scanned applications that it flagged it. I was in process of updating, installing plugins. Maybe it is case of legitimate infection. Just giving you a heads up.

Galaxysurfer

[Galaxysurfer]

Definitely an infection since sagetv wont let me uninstall it. Luckily I had an older untainted version of my c drive that I reloaded. so someone please check on the efficacy of the windows files at bintray. My infection source could have been elsewhere but better to be safe than sorry.

Galaxysurfer

[Galaxysurfer]

KIS 2017 still flagging sagetv as malware

can someone here talk to kaspersky?

[wubdich]

I downloaded and installed 9.0.13.536 a few days ago - uploaded and scanned my SageTVService.exe with Virustotal (http://www.virustotal.com) - none of the 57 AV-Scannes detected maleware ... see attached screenshoots.

[trallyus]

my copy of bitdefender detected one of the sage tv installation files and flagged it as well but it was a false positive like the last time when a game i played got flagged and i reported it after virus signature updates that showed it clean the week before

[Galaxysurfer]

Sent link to downloads to kaspersky as an incident report telling them it scans clean before installled as well as passes malwarebytes 3.0 so i'm confident i'm not really infected. It is overactive KIS2017 that is flagging & deleting program.

I even have antimalware protection in my router so issue is with Kaspersky. Hopefully now they will put it on safe list.

[Galaxysurfer]

In the end I didnt change over from old antivirus suite to KIS2017 come renewal time. I went back to ESET which I like for it's ability to easily add port rules for our server/client setups. From poking around forum it seems this is an ongoing saga with Kaspersky. Seems to come down to the software design how it searches for infection etc.