Server 2016 Task Scheduler lost tasks

Ormond Stock 1 Reputation point

Running Windows Server 2016. I have a number of scheduled tasks which have run successfully for years. Then a few weeks ago they all vanished. Nothing in the event log I could see, the sa.dat file was empty. I put it down to a mystery and created the tasks again.
Now this morning they are all gone again, with no trace.
Does anyone have any ideas?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,410 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Dave Patrick 426.3K Reputation points MVP

    Any files in windows\System32\Tasks ?

    0 comments No comments

  2. MotoX80 32,441 Reputation points

    Check the Microsoft-Windows-TaskScheduler/Operational event log for event ID 141.

    My pc is Win10, but I would expect 2016 to have the same log.


    0 comments No comments

  3. Limitless Technology 39,461 Reputation points


    You can try to look for the tasks as they seem like they have been "forgotten" somehow. Run Command Prompt on the server and type:

    schtasks /query /TN "custom task name goes here"

    or if you can't remember a custom task name to test, just use:

    schtasks /query

    Scroll through the results to see if your task(s) are listed.

    It's also worth checking to see if the task(s) have corresponding files in:


    Some thoughts: if you create a new task while still in the 'Task Scheduler (local)' node it might disappear, but if you select a relevant node first this should not happen.

    I hope this will help you!

    0 comments No comments

  4. Kenneth Hippolite 0 Reputation points

    This just happened to me. Turns out Windows Defender had quarantined the tasks. Clicking restore didn't help because the restored task appears but does not run, however you might try exporting the recovered tasks and importing them back. Also add %system32%\tasks as an exception to Defender

    0 comments No comments