locked
Windows 10 Task Scheduler Skips Schedule execution of task for days, then starts running it again RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I' have a simple script file that runs every 2 hours, daily.  It has executed flawlessly for over a year, since my upgrade to 10.  Recently, (late Jan), it now doesn't always run the task.  It will skip the task for a day or two, then start executing it again.  There are no error messages, nothing in the log file.  It just doesn't run on its scheduled time.  It will run manually from within scheduler, but not according to the schedule.  This computer is unattended, so nothing additional has been installed.

    I even reformatted hard drive and reinstalled windows 10, a very basic system, very limited other programs installed, (office 2010 is). 

    I'm wondering if a recent windows update may be the culprit.  Weird how it runs according to schedule, then doesn't.

    Thursday, March 2, 2017 8:18 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi IlikeToSki,

    What is recorded in the task history?

    If it is possible, please share us the exact configurations of the task schedule especially the trigger for the task. It would be very useful to troubleshoot this issue.

    "I'm wondering if a recent windows update may be the culprit."
    Check the update history for the newly installed updates. Uninstall them then check the symptom again.

    Best regards

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, March 3, 2017 2:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As far as checking recent updates, since I totally reinstalled windows to try and solve, there were massive updates on that day, so I really wouldn't be able to narrow it down.

    Some additional data that I have found, after I reboot the computer, it typically doesn't work that day, but start working the next, but sometime later in the same day, really tough trying to figure out the pattern.

    Here is an export of the task:

    <?xml version="1.0" encoding="UTF-16"?>
    <Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
      <RegistrationInfo>
        <Date>2017-02-18T09:50:14.3237995</Date>
        <Author>DESKTOP-8GDC22U\Houseboat</Author>
        <URI>\Check Internet Connection</URI>
      </RegistrationInfo>
      <Triggers>
        <CalendarTrigger>
          <Repetition>
            <Interval>PT2H</Interval>
            <Duration>PT13H</Duration>
            <StopAtDurationEnd>false</StopAtDurationEnd>
          </Repetition>
          <StartBoundary>2017-02-17T07:05:00</StartBoundary>
          <ExecutionTimeLimit>PT30M</ExecutionTimeLimit>
          <Enabled>true</Enabled>
          <ScheduleByDay>
            <DaysInterval>1</DaysInterval>
          </ScheduleByDay>
        </CalendarTrigger>
      </Triggers>
      <Principals>
        <Principal id="Author">
          <UserId>S-1-5-21-4261142202-1126358112-2050804276-1001</UserId>
          <LogonType>InteractiveToken</LogonType>
          <RunLevel>LeastPrivilege</RunLevel>
        </Principal>
      </Principals>
      <Settings>
        <MultipleInstancesPolicy>StopExisting</MultipleInstancesPolicy>
        <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
        <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
        <AllowHardTerminate>true</AllowHardTerminate>
        <StartWhenAvailable>false</StartWhenAvailable>
        <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
        <IdleSettings>
          <StopOnIdleEnd>true</StopOnIdleEnd>
          <RestartOnIdle>false</RestartOnIdle>
        </IdleSettings>
        <AllowStartOnDemand>true</AllowStartOnDemand>
        <Enabled>true</Enabled>
        <Hidden>false</Hidden>
        <RunOnlyIfIdle>false</RunOnlyIfIdle>
        <WakeToRun>false</WakeToRun>
        <ExecutionTimeLimit>PT1H</ExecutionTimeLimit>
        <Priority>7</Priority>
      </Settings>
      <Actions Context="Author">
        <Exec>
          <Command>C:\Users\Houseboat\Documents\BCRLogin.ahk</Command>
        </Exec>
      </Actions>
    </Task>

    Saturday, March 11, 2017 2:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi IlikeToSki,

    What is recorded in the running history of the specific task?
    Please try to update to the latest Windows 10.14393.953 (KB4013429) version then check the symptom again.

    Best regards

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, March 15, 2017 7:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As for the history, when the time is skipped, there is no history at all for that time period, it is just like the time didn't exist.  The scheduled run time just passes and nothing happens. 

    I am already at the current version number 10.14393.953.

    One thing I seem to now observe, is that after I reboot the computer, the task scheduler doesn't work at all immediately, but starts working either later that day, or the next day, after the computer has been put to sleep and reawakened.

    Thursday, March 16, 2017 3:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi IlikeToSki,

    "the task scheduler doesn't work at all immediately"
    Do you mean the task schedule service didn`t run automatically after we restarted the machine, right? Have you reinstalled the machine? Are there any error or warnings recorded in the Event Viewer(Windows Logs\Applications, System)?

    Please check the task schedule service's startup type and ensure it is configured to start automatically.

    Best regards

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, March 17, 2017 7:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The task scheduler service runs just fine, its just that the scheduled even doesn't fire at the next scheduled time, even though the next scheduled time is listed and correct, since it is a repeating task, all of a sudden, the task will start running at point in the future.  I see no errors in the windows logs associated with Task Scheduler.
    Friday, March 17, 2017 11:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi IlikeToSki,

    "(<DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
         <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>)."
    Please try to untick the task schedule settings for power configuration "start the task only if the computer is on AC power".

    "    <StartWhenAvailable>false</StartWhenAvailable>"
    Choose "Run task as soon as possible after a scheduled start is missed".
    "   <ExecutionTimeLimit>PT1H</ExecutionTimeLimit>"
    Untick the option "stop the task if it runs longer than " and "If the running task does not end when requested, force it to stop".

    Best regards

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Tuesday, March 21, 2017 7:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I tried changing all of the changes recommended and it did not have an impact, still skips.
    Tuesday, March 21, 2017 6:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi IlikeToSki,

    How about the issue now?

    Best regards

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 27, 2017 7:15 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Problem still exists, I have found that if I put the computer to sleep, then turn it back on (automated each night), all tasks run as scheduled.  They just do not run after a full reboot.  This is a remote computer, and I have it go to sleep every night.  I would need to deactivate the sleep cycle to be able to determine if the task scheduler ever restarts without first going into sleep mode.  The problem doing this, is my routine checks for internet connection and re-logs in if not found, (and also includes a reboot option if it can't immediately connect).  If the task scheduler never runs, I have the risk of it never reconnecting and I can't access it until I revisit the location 4-6 weeks apart.
    Monday, March 27, 2017 3:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    My troubleshooting determined that:

    • After a reboot, the scheduled tasks will not start executing for 14 to 16 hours, (even though their next scheduled time was within the next hour after a reboot)
    • If the computer is put to sleep, the tasks will run as scheduled at the very next scheduled time, no scheduled time is missed.
    Thursday, April 6, 2017 8:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote


    Hi IlikeToSki,

    I would make an apology for the delayed response.
    Considering there is no running history of the task, the forum community resources are limited to resolve this issue. It is recommended to open a ticket for this case from Microsoft.
    https://support.microsoft.com/en-us/getsupport?oaspworkflow=start_1.0.0.0&wf=0&wfName=productselection&gprid=18165&ccsid=636281641575355369

    Best regards

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 19, 2017 2:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I realize this is an old post, but I have this same problem. I have many scheduled tasks that have multiple triggers each day. They run once per hour on separate triggers. The are set to stop if they run longer than 30 minutes, so don't interfere with next one. 

    However, of the 20 or so tasks, one of them will just choose to skip a run time. For example, it runs at 9:10am. It says the next run time is at 10:10, but when that time goes by all that happens is it says the next run time is 11:10. This continues until I run it manually.

    Anybody else have this problem?

    Thursday, October 11, 2018 5:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    I had exactly the same problem following some recent update.

    I had to set the trigger for the scheduled task to "One time", then set the "Repeat task every" to get the frequency I required.

    Thursday, January 10, 2019 1:19 PM