If you DON'T administer windows defender exclusion lists, then please DON'T answer, thank you!
I found defender to mistakenly detect a command line as virus. The command
C:\Windows\System32\vssadmin.exe delete shadows /all /quiet
gets detected as Trojan:Win32/ShadowCopyDelQuiet.A
So I'd like to create an exception. If I exclude
C:\Windows\System32\vssadmin.exe as path, it still gets detected.
If I exclude it as process, it still gets detected.
So whatever MS is thinking by detecting this, they don't let me deploy a rule to stop their scanner (up2date) detecting it! Logs get flooded and users get anxious.
So right now I am removing that command from my script.
I never had problems adding a path or process before, so I am clueless what to do about it.
Here's the log entry:
CmdLine: C:\Windows\System32\vssadmin.exe delete shadows /all /quiet