[JENKINS-75884] powershell step should hint towards using pwsh step instead

[jenkins-infra-bot]

powershell executable being replaced by pwsh, one could be confused by the current behaviour because there are two different steps for these different executables.

If trying to run a powershell step in an environment where it is not available, you get CreateProcess error=2, The system cannot find the file specified.

If powershell step fails because it could not find the executable, maybe the error message could check whether pwsh is available and hint the user towards using it?

---

Originally reported by vlatombe, imported from: powershell step should hint towards using pwsh step instead

• status: Open
• priority: Minor
• component(s): durable-task-plugin, workflow-durable-task-step-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 2025-12-09

Raw content of original issue

powershell executable being replaced by pwsh, one could be confused by the current behaviour because there are two different steps for these different executables.

If trying to run a powershell step in an environment where it is not available, you get CreateProcess error=2, The system cannot find the file specified.

If powershell step fails because it could not find the executable, maybe the error message could check whether pwsh is available and hint the user towards using it?