Oops - I wonder why that is

Take all of this with a grain of salt as I’m not a security expert/researcher and I don’t know what your internal IT policies are.

I Just ran it through our enterprise AV and no issues. I imagine it will be doing some level of heuristics and has determined that something in the executable has a similar signature to a known malicious threat.

Another thing that I know catches out some Enterprise AV is the actual location of the executable. For example, even though SentinelOne doesn’t class this as malicious, it won’t let me run it from download, i have to shift it else where