We're having strange issue:
The "ransomware detection" setting is interfering with a local .NET process running on our machines. When the detection is switched on the processes run much slower, this is caused by long pauses in Gen0 and Gen1 garbage collections (of up to several seconds instead of a few microseconds).
Switching off the "ransomware detection" resolves the issue.
Nothing logged on Central when our local .net process is suffering, so I'm unable to find a legit reason for that.
What are our options here ( except disabling Cryptoguard) ? We ideally want to exclude coreclr.dll from Ransomware detection scope, but there's nowhere to do it.
[edited by: GlennSen at 8:27 AM (GMT -8) on 25 Feb 2023]