Powershell' is not recognized as an internal or external command,

i am getting this error what could be the possible error previously the workflow was working

@mukesh1434 there is a blue ‘?’ in the bottom right of the screen when you log into Harness. Can you click that and submit a ticket there? That will give more information on the error, the place that the error is happening, and some more backend information.

@mukesh1434 did you make any changes do your Delegates?

@ravi.lachhman no i haven’t made any changes to the delegate
when the workflow is runned for the first time its running sucessfull but when deplloyed second time by making small changes to script it failing

@sneakyaneurysm the actuall error is ‘Powershell’ is not recognized as an internal or external command,operable program or batch file.

Do you happen to have more than one Delegate? What type of Delegate(s) do you have deployed?

For now focusing on the Delegate(s) because that is where the invocations come from.

Can you post a screen shot of the step leading up to and including the Powershell Call? Also let us know what the script is trying to accomplish.


it runs in the local system
profile is primary
the scripts copys into zip file

Interesting so this is a Remote WinRM call and was mentioned the PowerShell script changes every time the pipeline is run. Is there a particular reason for that?

Since on a remote machine (that 192.xxx), not sure can take a look at these.



@ravi.lachhman thanks a lot i got it resolved just proweshell upgade to 4 it has resoved it

1 Like