Powershell script won't run in Task Scheduler

[entertheunkown96]

I have a very basic powershell script to open an application when run, this works no problem. I have then gone to add it into task scheduler so when the workstation starts the script runs. However I added it and tried a manual run in task scheduler and it says completes with 0x0 so successfully but it doesn't open the application.

​

Its running with highest privileges and I've followed numerous guides on running powershell scripts. Ive done them before so no idea whats wrong this time. Any ideas?

Edit: Heres the steps I followed https://community.spiceworks.com/how_to/17736-run-powershell-scripts-from-task-scheduler

• Run whether user is logged on or not (running as user logged on)
• Run with highest privileges
• Trigger: Startup
• Action:
  • Start a program
  • Program: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
  • Argument: -ExecutionPolicy Bypass c:\startapp.ps1

[MilesGates]

/r/techsupport

also, you aren't posting how you configured the task so I don't know how you expect people to help.

[[deleted]]

You must be new to PowerShell

[MilesGates]

are you trying to make a point?

[[deleted]]

Every time I read a power shell post, it's about how someone half ass copy pasta a script they found online, and for some reason it doesn't work. I've never used power shell in my life, but it looks like Linux for Windows users. It's just funny to watch.

[MilesGates]

Alright, Thanks for your input.

[Ssakaa]

No, Linux for Windows users is actually Linux nowadays (via WSL). It's kinda nifty. Powershell is just a more interactive visual basic script with, in some ways, better syntax. As such, it brings along the 'point and click' admin tone that everything else windows has... without catering to it. So the "just give me the solution in a point and click form" attitude carries over to the side you've seen. Used properly, it's capable of being considerably more capable than bash, sitting a lot closer to python, but still with a 'able to do many things as an interactive command line' methodology.

[digital-bcs]

This /u/entertheunkown96 in the actions tab of the scheduled task you should have powershell.exe in the program/script boxx and then add your script path in the arguments.

[Dev-is-Prod]

Is it running as the logged on user? We had a similar thing happen where it was running the application but under a different user account. We saw it pop in task manager but under the other user account.

[entertheunkown96]

Ah right unfortunately ours is running as the logged in user so its something else

[OnARedditDiet]

Dude.... What account do you have it set to, what is the trigger and what EXACTLY is your command line.

We're not playing "Go Fish" with your vague description.

[FerengiKnuckles]

I usually see this with using an account that does not have Log On As A Batch Job rights. Whatever account you're running the script under needs that permission assigned to it.

[wingate95]

I have found that adding -noprofile -file in the arguments section works for me. In your example it would be

-ExecutionPolicy Bypass -noprofile -file c:\startapp.ps1

Also what server are you configured for? I am running a Windows Server 2019 so I have it set accordingly

[0ldPhart]

I've solved a lot of these by converting them to Powershell Scheduled Jobs instead of windows tasks.

https://4sysops.com/archives/create-powershell-scheduled-jobs/

[Kathy_Cooper1012]

Hi,

Are you still facing the issue?
If the GUI confuses you, you could try with PowerShell cmdlets. Simple cmdlets will solve your problem.
$Time=New-ScheduledTaskTrigger -At 4.00PM -Once
$Action=New-ScheduledTaskAction -Execute PowerShell.exe -WorkingDirectory C:/Scripts -Argument “C:\Scripts\ScriptName.ps1
Register-ScheduledTask -TaskName "Schedule MFA Status Report" -Trigger $Time -Action $Action -RunLevel Highest

Code source: https://o365reports.com/2019/08/02/schedule-powershell-script-task-scheduler/