Easy fix 0xFFFD0000 in Task Scheduler when running Powershell script

In my Task Scheduler I had error 0xFFFD0000 as a last run result on one of my Powershell scripts:

It appeared to be a path error to my ps1 script. I apparently had moved the script to another folder to reorganize some things. 🙂

To run a Powershell script in Powershell, I basically fill in these fields with the following values:

Program/script: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add Arguments (optional): -File C:\Scripts\myScript\dailyreport.ps1
Start in (optional): <empty>

Any typo may result in a specific error. Here are some examples:

The system cannot find the file specified (800070002)

The field “Program/script” contains an invalid directory

The task is currently running. (041301) hangs

The field “Program/script” contains an invalid executable name extension. For example: powershell.sexe instead of powershell.exe would lead the task to be hanging. In the end, the task will time out after 72 hours.

(0x1)

The field “Add arguments (optional)” contains an invalid argument. For example: -Gile instead of -File could lead to this error.

(0xFFFD0000)

The field “Add arguments (optional)” contains an invalid file name. For example: you refer to myscript.ps2 instead of myscript.ps1

You may also benefit from an external Microsoft site listing all Success and Error codes:
https://docs.microsoft.com/en-us/windows/desktop/taskschd/task-scheduler-error-and-success-constants

In addition, I have also experienced other errors according Scheduled Task errors:

Leave a comment

As I’ve updated this article in 2023, the solution for Task Scheduler error 0xFFFD0000 still remains valid. However, if this article did not help you solve your problem, please leave a comment! This website is visited thousands of times a day. There is a good chance that I or someone else has an answer to your question.