Elaine, glad to hear that proactively installing the latest runtime helped mitigate the issue. We have seen cases where our signed EXE wrappers that launch and handle return codes from some third-party EXE installers, like those for Visual Studio and .NET, are sometimes getting flagged, so we are starting to look into potential options for those. I do not know if IT could or should be more proactive by keeping up with at least Microsoft's runtime updates, so that installers like NI's have nothing to install when we try to install a later runtime.
I agree with Rolf's reply.
NI does not have any details into how these security software decide whether some installer action is problematic. NI signs almost all binaries that can be executed which is an obvious red flag. We know unsigned MSIs are starting to come into play, so NI is moving toward signing MSIs in newly built packages.
Some companies are wanting to better understand what if any known vulnerabilities exist in what NI deploys with its software, NI is working to improve the uptake of fixes for third party stuff and including in new releases.
Scott Richardson
https://testeract.com
