I am admittedly new to this. I have tweaked a script for basic renaming and relocation of some files. When I paste the code into cmd, it runs everything properly. However, when I make a .bat file with that script in it, and run that from scheduler, it appears to start fine, but doesn't actually run/complete. Neither drive is physical to the computer. I am running this in a VM, with the storage direct attached to the host machine. Both the fetch, and depository locations are shared and mapped network drives with full permissions. Double clicking the .bat file appears to execute it correctly as well.
Edit 1. I recorded my screen while executing the task.
c:\windows\system32>filebot -script fn:amc --output "R:" --action move -non-strict "E:\Watchdirectory" --def excludeList=amc.txt
Run script [fn:amc ] at [Mionday] Jan 09 15:51:58 CST 2017]
Parameter: excludeList = amc.txt
Argument [0] File does not exist: E:\Watchdirectory
Edit 2. Further reading into task scheduler issues revealed that there might be an issue with task scheduler understanding shared drives within commands. I will have to investigate this further to see if that is the case.