On initial execution of sql.exe it creates a dll file in the Windows TEMP directory and then tries to execute it.
Such an action is blocked by our group policy. See evidence below.
This is something that could be changed/fixed in a future release?
I'm using the sql.exe that is packaged with SQL Dev 18.1 on Windows 10.
Let me know if you need any further information?
Thanks
