Hi Rajat,
I am having issues getting UiPath to run Win10 native bash commands.Screenshots show bash works from the command line, works invoked from an AutoHotkey script, but fails from a UiPath workflow. Any help you can give me getting going with it would be great.
- PowerShell, as you, Richard and Clayton point out, l is an option that works for some things, and I use it when needed, and it works fine.
- Git bash also works with UiPath workflows with no issues encountered yet.
- Here’s the rub: Any workflow that calls “C:\Windows\System32\bash.exe” will not run. Calling PowerShell to run native bash will not run from a workflow, although it works fine with the command line.
I’m afraid I should have logged more of my results, but on several occasions PowerShell (invoked from a workflow) asked for a Windows Credential. Stepping through workflows, the Output window has on some occasion shown that bash is not recognized as a command. This leads me to believe I may have to give UiPath permission to access bash, but I have not found anything in the forum or StackOverflow yet to suggest how to do it.
I believe that any workflow that would simply execute “bash -c ls” would get me most of the way there, be it from “Start Process”, “Run Power Shell Script”, or anything.
The Microsoft docs on security policies and local Win10 accounts are sufficiently opaque to me that I’ve not been able to determine whether I need to set a security policy for UiPath to use bash or not.
Here’s some screenshots:
Okay, bash works …
Calling a bash script from an AutoHotkey script works …
But UiPath can’t, apparently, access it as I have it configured.
Once again, thanks for your help. Also, Richard, Clayton, any thoughts?
Regards,
burque505