Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[astromo]

Following on from where the aggravating AV fun & games that MC32 leaves behind, today I struck a bump in the road thanks to Norton 360.

Norton 360 specifics:
   Program version (AV module):   24.6.9241.854
   Virus deinitions version:         240731-0

I've been running MC33 (thanks to Jim, Matt and the rest of your capable crew BTW) for the last 2 weeks with no dramas. Security flags were raised by Norton but easily batted away with an accept/reject green/red button when queried by a software generated dialogue box.

Today, that changed and N360 got very nasty.

Specifically, it took exception to the install file. Then after I disabled N360's protection, it came back for a routine scan and quarantined with a high risk flag:
   

Code: [Select]

C:\Windows\System32\mc33.exe

Code: [Select]

C:\Windows\SysWOW64\mc33.exe

Code: [Select]

C:\Program Files\J River\Media Center 33\MC33.exe

Code: [Select]

C:\Program Files\J River\Media Center 33\Drivers\JRiverASIODriver64.dll

Code: [Select]

C:\Program Files\J River\Media Center 33\Plugins\hh_portable.dll
For info, I'm attaching the security report generated by N360 (if that helps at all?).

I've also used N360's on-board false positive reporting function and provided the following note:

I have been using this software [referencing the submitted JRiver MC33 file] for years and trust the source. It is software supplied by:
https://jriver.com/index.html
This item is being falsely flagged as suspicious.

This software has strong community support and very active engagement from the developer. Security software plagues the platform. Refer here:
https://yabb.jriver.com/interact/index.php/topic,86096.0.html
My guess is that this because it is highly geared to networking media files and security software finds that suspicious.

Please do your due diligence. I'm confident that there is no issue with the file submitted. Please whitelist the application and update your definitions to suit.

For those who use N360 and possibly want tips to navigate the install hassles by taking advantage of my experience, the steps that I took are set out here:
1. Set up exclusions for the files that N360 falsely deems to be "high risk" by by opening N360 and navigating to:
      Security > Scans > Exclusions
   and add the files noted above.
2.   While you're there, also exclude the install file MediaCenter33[Build No.]-x64.exe wherever you've located it following download.
3. To avoid issues with N360's behavioural protection, you'll need to go here:
      Security > Scans > Antivirus > Exclusions
   and add the files covered above in steps 1 and 2, as well.
4. Then, navigate to:
      Security > Advanced > Antivirus
   and disable Auto-Protect for 10 minutes.
5. Run the MC install file and allow in & out firewall traffic and provide other N360 permissions to suit.

I expect that I'll have to nurse installs manually using the steps noted above until (if?) Norton sort their malware definition files out. All rather annoying, considering relatively hassle free operation up until now.

Now, back to enjoying MC's advantages. All I wanted to do was watch the News live to air via MC's TV functionality but unfortunately, I had to deal with Norton's nervousness. Possibly they did a root and branch reset following the Crowdstrike debacle, for safety's sake? Anybody's guess..  ?

[JimH]

As you know, we don't recommend using anything but Windows Defender.