It won't help you, @pp, but I can confirm I've had similar issues at work with SentinelOne and InProcessClient(32|64).dll a couple of years ago (Nim 1.2.x days). Nimble stopped working out of nowhere, as well as some Nim programs I'd written. The most obvious symptom was that "nimble -v" produced no output whatsoever, immediately returning to the command prompt. There would be errors in the Windows Event Viewer.
Luckily for me, I was able to convince the security guys to add exclusions for Nimble and a tool I'd written and they worked when SentinelOne was out of the picture. I've not seen this error in recent times so I'd hoped that SentinelOne has stepped up its game but it sounds like it's still troublesome to developers. I was never able to pin down precisely what made SentinelOne break (I suspect it's not an intentional flag of software as a virus but simply SentinelOne being buggy - VirusTotal showed 0/74 matches for Nimble at the time) but I had a feeling that it was related to SSL: I had web sites that used Jester and SSL and they got flagged while other purely command line tools for CSV processing never triggered it.
