You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to create some schedule tasks where the executable is located in Program Files. Without quotes in the command path it creates the schedule task without issue. But the schedule task does not run because it only sees "c:\Program". If quotes are added then the task scheduler has no problems executing but then it is no longer idempotent.
Expected Behavior
To be able to put quotes in both the command and working directory. And to have the schedule task run properly.
Steps to Reproduce
Steps to reproduce the behavior:
Add a schedule task with any trigger.
Use the full path of pwsh.exe in the command
3 mock any arguments like -Command { "Hello World" }
Execute.
Environment
windows
The text was updated successfully, but these errors were encountered:
Describe the Bug
We are trying to create some schedule tasks where the executable is located in Program Files. Without quotes in the command path it creates the schedule task without issue. But the schedule task does not run because it only sees "c:\Program". If quotes are added then the task scheduler has no problems executing but then it is no longer idempotent.
Expected Behavior
To be able to put quotes in both the command and working directory. And to have the schedule task run properly.
Steps to Reproduce
Steps to reproduce the behavior:
3 mock any arguments like -Command { "Hello World" }
Environment
The text was updated successfully, but these errors were encountered: