ChristianK

Okay, I'll setup a test machine with ESET and Teams only to isolate the problem and run the steps you listed ASAP.

Actually, it does make a difference. When I disable realtime-protection the CPU-impact vanishes, too. Yes, there is v7.3.2039.0 on all clients.

We have performance issues with Microsoft Teams and the Endpoint Antivirus since the last update of the Teams client. The realtime-scanner seems to permanently scan the vairous "Teams.exe" processes which leads to extreme CPU load and loss of connection in Teams on some clients. Since most employees here are still in home-office, we need Teams to run stable for our communications. The only way to solve this issue for the moment is to exclude the "Teams.exe" processes from the scanner engine. "Teams.exe" resides in "C:\Users\<USERNAME>\AppData\Local\Microsoft\Teams\current", that's why I asked for a possibility to use placeholders.

Hi Marcos, thanks for your explanation. This makes sense. But what about wildcards? Something like "c:\Users\*\AppData\Local" would work theoretically. Why is that also not usable in that context?

Hi there, I try my best to exclude a specific process on all my windows-clients from the realtime scanner, but I can't find a way to do so since the web-UI refuses to let my use placeholders for system vars like %LOCALAPPDATA%. That way it renders this global setting useless for me since the path resides in "c:\<USERNAME>\AppData\Local\..." and the "<USERNAME>" part is different on each machine. If there is a way to add a specific file/process using system variables, please give me a hint how to do so. If not, it would be great if you (the supportes/devs) would consider to put this on the feature-request list as I'm sure that this is an issue for many enterprise customers. Thanks in advance!