More > JRiver Media Center 33 for Windows
Taming Windows Defender
Antognini:
Any idea why Windows Defender is causing JRiver problems? Can you at least characterize the issues?
Awesome Donkey:
--- Quote from: tzr916 on January 22, 2018, 09:09:13 pm ---I'm thinking you should also exclude not just files and folders but any MC Processes. To do that you MUST enter the entire PATH and process name into Defender. Examples:
C:\Program Files\J River\Media Center 23\MC23.exe
C:\Program Files\J River\Media Center 23\Media Center 23.exe
C:\Program Files\J River\Media Center 23\JRService.exe
C:\Program Files\J River\Media Center 23\JRWorker.exe
C:\Program Files\J River\Media Center 23\JRWeb.exe
--- End quote ---
It's probably not a bad idea to do, in addition to those I'd also add...
C:\Program Files\J River\Media Center 23\PackageInstaller.exe
C:\Windows\System32\MC23.exe
C:\Windows\SysWOW64\MC23.exe
--- Quote from: Antognini on January 22, 2018, 11:38:29 pm ---Any idea why Windows Defender is causing JRiver problems? Can you at least characterize the issues?
--- End quote ---
Nope. Could be quirks in its real-time scanning engine to false positives. Probably not the latter, that seems to be an issue with some third-party anti-virus applications (even though a good bit of MC's files have a digital signature).
My guess (in regards to the delay when starting MC I've seen before taming Defender) is it doesn't recognize a specific file (e.g. Media Center 23.exe) and is either actively scanning the executable(s) and/or uploading the file to the cloud for analysis.
mattkhan:
fwiw I found https://www.reddit.com/r/Windows10/comments/5gf38v/when_excluding_a_process_in_windows_defender_do_i/ provides a link to the official, updated, docs on this subject
https://docs.microsoft.com/en-us/windows/threat-protection/windows-defender-antivirus/configure-exclusions-windows-defender-antivirus
which includes the line
--- Quote ---When you add a process to the process exclusion list, Windows Defender AV will not scan files opened by that process, no matter where the files are located. The process itself, however, will be scanned unless it has also been added to the file exclusion list.
--- End quote ---
This also says you can use wildcards so c:\Program Files\J River\Media Center 23\* should be sufficient (if you're happy using wildcards)
I suppose you could just use that entry alone if you just want to give a pass to MC as the process exclusion also excludes any files opened by that process (whereas a file/folder exclusion excludes those files when touched by any process).
Awesome Donkey:
Huh, interesting. Using wildcards would certainly make life easier when doing exclusions. But looking at the wildcard examples the MS article lists here, this rule *should* cover all files and subfolders (unless I got it wrong);
C:\Program Files\J River\*\*
It can probably be used with an environment variable too. I'll go through these articles and test some stuff.
1maynard:
Good stuff Guys. Very helpful for computer dummies like me.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version