Windows 10: Task Scheduler and Bat File Problem

Hi,

Not sure which forum to post this in, but hopefully someone has some insight and can help me with this.

I have a simple .bat file that stops my media server, creates an archive of a folder (for backup purposes), and then starts the media server again. It works perfectly if I double click the .bat file, or if I run the bat file from the command prompt.

When I run it from Windows Task Scheduler, however, it does not work properly. The media server does not shut down. If I look in the task manager, though, I see that the archiving program has started. It is difficult to see what is happening because, unlinke when running this in CMD, when it is run from the task scheduler it produces no output to see if there is an error message.

Why would it run differently from the task scheduler than when I simply double click the .bat file? I have chosen to run it from the same user account, and also selected "run with highest privileges."

Here is the bat file. The first line stops the media server. The second line runs the archiving process (using 7zip). The third line starts the media server again. Again, it works perfectly if I simply double click the bat file.

Code: @echo off taskkill /im "plex media server.exe" 7za u C:\plexbackup.7z C:\plexdata -mx0 -up1q0r2x1y2z1w2 "C:\Program Files (x86)\Plex\Plex Media Server\plex media server.exe"[/quote] Anyone have insight?

Thanks.

:)

 

Task Scheduler

In Windows 10 version 1703 the Task Schedule with a .bat file will start, but does not recognize a mapped drive. If I start the .bat file manually it works fine. Prior version had no problem.

***Post moved by the moderator to the appropriate forum category.***

 

MS16-100: Security update for Secure Boot: KB3172729 Seems to be causing Inaccessible Boot Device error

If not I'll create a scheduled task on shutdown linked to a BAT file to do this in the meantime.

 

In Task Scheduler Enable All Tasks History
Run the scheduled task
Refresh, and look at the History tab for that task.
Look at each entry in history and see if you can find an error message/code for any step in the task run.

 

If you run it with standard privileges it should display a console window and you should be able to see any error messages.

 

I solved the problem by disabling the feature "run whether the user is logged on or not." With that disabled the batch script runs as it should and the output is visible in the command shell.