Hi, thanks for posting.
Instead of trying to exclude processes by EXE name, it may work better if you restrict the scanning to exclude the directories where NCrunch does work. Try excluding the following:
The NCrunch installation dir (i.e. C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2017)
The NCrunch
workspace base pathThe NCrunch AppData directory (i.e. C:\Users\Remco\AppData\Local\NCrunch)
It's worth considering that the scanner may be attempting to scan ALL files that are touched by any code executed by NCrunch. This means that scan targets should also be restricted by areas of the file system that are touched by your tests, build system and production code. So database and resource directories should probably be excluded.
It's much harder for me to advise on which areas of your disk are used by the build system, as this is a very dynamic beast that behaves differently depending on the packages you're using, the precise version of VS you have installed and the platforms you're working with. Excluding the Visual Studio directory itself is probably not a bad idea, and it may be worth excluding your Nuget packages directory too. I've also witnessed build tasks doing quite a bit of processing in the Windows Temp directories, though excluding these might undermine some of the benefits of using the scanner.
