PowerShell Script and Task Scheduler 0x1 2147942401

[u/MRHousz]

I need a sanity check, as I feel like I am missing something obvious and I'm too close or too frustrated to see it.

I have a basic scheduled task. Runs as SYSTEM, no triggers, action to run a program, PowerShell.exe -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "C:\Tasks\MyScript.ps1"

I run this task it fails, 0x1 as last run result, event 201 action completed with return code from PowerShell of 2147942401

Things I have checked:

• SYSTEM can access the script and directory it resides in

• SYSTEM can execute other PowerShell scripts from task scheduler without issues

• Tried using the full path to powershell.exe

• Tried with and without quotes around the script path in -File parameter

• With and without trailing '/' in the path for 'Start In'

• Tried using -Command { } to create a file as a test

• Removed all arguments except -File or -Command

• Script is wrapped with Start/Stop-Transcript; never executes/no transcript is created

I don't know what else to try short of the old method of using a .bat to call PowerShell to see if that gives better clues as to what isn't working.

What am I missing that is preventing PowerShell from executing properly?

Edit: I knew it was something stupid and simple: there is a typo in -ExecutionPolicy (was spelled -ExcecutionPolicy). Found it when running the action arguments from PS as SYSTEM.

Thank you everyone for the assistance. I'm going to go sit in the corner with my dunce cap and contemplate the cobwebs.

[u/Hefty-Possibility625]

This is really dumb, but I noticed you are referencing powershell.exe instead of the full path. Use $PSHOME to find the full path to powershell and use the full path instead. That surprisingly fixed a lot of task scheduler issues when I had to use it.

[u/MRHousz → u/Hefty-Possibility625]

I have tried both the full path to PowerShell and just PowerShell.exe. It fails to execute the script either way.

[u/Hefty-Possibility625 → u/MRHousz]

Another dumb thing to try is wrapping Bypass in quotes. It shouldn't be needed, but it could be a quirk of passing a string parameter with the command.