My company doesn't use CrowdStrike. I believe they were considering it until the big outage back in 2024, then they backed off.
Regardless, whether it's CrowdStrike specifically or any other anti-virus or other threat protection method, you basically have 2 options when you get problems with it but can't remove it.
Option 1: Exclusions. Convince whoever is managing it for your company that the performance hit is severe enough that they need to exclude LabVIEW files or processes from it.
Option 2: Workarounds. Try to narrow down exactly what causes the biggest lags, and see if you can either do less of that, do something else that doesn't require as much action by the scanning process, or see if you can at least "batch up" the problem. By batching up, that means if the problem is "per file", see if you can merge them all together into one file (.llb, .lvlibp, .zip, etc...). Or if it's something that "sends data" but doesn't need any data back in response, create a separate process that sends that data so your main process isn't held up by it, and the separate process perhaps sends the data every minute instead of every 5 seconds, or whatever.
