NCrunch takes assemblies apart, shoving instrumentation into them. It creates isolated processes to execute code, which depending on what you are testing, can be literally anything. It has network code to share data with grid nodes, sets up temporary working directories under the user profile to store executables which can target any number of platforms. It contains IPC/RPC mechanisms. It allocates shared memory. It integrates with the system in low levels to coordinate processing loads.

This is, of course, the point of the product, but you can understand how security software might consider these activities suspicious. If you install software on your computer to do the above things, and you have security software on your computer that is designed and configured to block the above things, then the software is going to get blocked.

I understand that you find this frustrating. Just imagine that you've spent 15 years building useful software that does the above, only for a scanner to accuse you of being a malware developer. I've just replaced my code signing keys twice in the last year (going through all the verification each time, with different vendors) to try and solve these problems at considerable expense. There are limits to what can be done about this. We are moving into a world where security is considered to be of upmost importance, and the most secure machine in the world is one that cannot be used and does not work at all.

The screenshot of the error you've provided (thanks for this btw) gives the reason for the blockage. The latest version of NCrunch was built this morning and is only a few hours old. It has almost no download history right now. Because it's from a small vendor and not signed by a tech giant, it isn't on an automatic inclusion list. Most likely you're seeing this because the security settings on your machine are set quite high (I assume via local policy and isn't something you can control). There isn't anything I can do from the product side to help with this problem - you'll need to speak to whoever is responsible for the security settings to get an exclusion added.