More > JRiver Media Center 33 for Windows
Taming Windows Defender
RD James:
If you are going to do this, is it really necessary to exclude anything more than the "C:\Program Files\J River\Media Center 23\Media Center 23.exe" process?
As far as I can see, everything to do with playing back media, importing, tagging files etc. is all done via that.
JRWeb.exe is the web browser, and that probably should be scanned by Defender.
JRWorker.exe seems related to podcast downloading - so I can't imagine there is any performance impact for it being scanned. Though it's probably safe, I always err on the side of caution with anything network-related.
That said, since those are launched as child processes of "Media Center 23.exe" wouldn't they also be excluded?
If you're creating a process exclusion, Defender also asks whether you want that process to be added to the Controlled Folder Access exclusion list, if you have it enabled.
These two entries are linked, so if you remove one it will prompt and ask if you wish to remove the other as well.
It is a real nuisance to set up in the beginning, but CFA offers some serious protections against ransomware or other malware.
Though I think there are some areas where CFA could be improved, I feel a lot better knowing that only whitelisted applications can make changes to my document and media folders.
--- Quote from: Awesome Donkey on January 23, 2018, 04:35:01 am ---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.
--- End quote ---
If you're using the Fall Creators Update (1709), I believe that this would have to be set via the Group Policy Editor, which means that you need the Pro version of the OS.
I don't see any way to enter a custom path for file/folder exclusions any more, only process exclusions - and those only support wildcards at the end of a path.
RoderickGI:
"C:\Program Files\J River\*\*" and "C:\Program Files\J River\*" are equivalent anyway.
Manfred:
Great work.
Shouldn't that be part of the Wiki?
RD James:
--- Quote from: RoderickGI on January 23, 2018, 03:00:49 pm ---"C:\Program Files\J River\*\*" and "C:\Program Files\J River\*" are equivalent anyway.
--- End quote ---
I believe they are functionally different, but practically the same in this case.
If I’m reading things correctly:
\J River\* includes all contents of the J River folder and its subfolders.
\J River\*\* excludes the contents of the J River folder but permits everything contained within its subfolders.
I’d still feel a lot more comfortable excluding a single process than a directory and everything contained within.
There doesn’t seem to be any reason to exclude more than "C:\Program Files\J River\Media Center 23\Media Center 23.exe" and that is what works best if you have Controlled Folder Access enabled.
RoderickGI:
Hmmm, your interpretation could be right there RD.
Just for reference, my Norton 360 automatically created rules for the following;
C:\Program Files\J River\Media Center 23\Media Center 23.exe
C:\Program Files\J River\Media Center 23\JRWorker.exe
C:\Program Files\J River\Media Center 23\JRWeb.exe
So I would think those should be the minimum, with the others mentioned optional.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version