• Tip: task scheduler task enabled

    From T@T@invalid.invalid to alt.comp.os.windows-11 on Sat May 2 14:23:09 2026
    From Newsgroup: alt.comp.os.windows-11

    Hi All,

    Speaking of the Task Scheduler, I just fixed an
    issue for a customer that is interesting.

    He had me change when his backup was scheduled
    so as not to interfere with a synchronizing program
    with his web site.

    Problem, his backup stop triggering. It worked fine
    when run manually. After considerable hair pulling,
    I decided to examine the XML code directly. Found
    the problem right away. Somehow, the XML had been
    changed from:

    <CalendarTrigger>
    <StartBoundary>2025-05-28T06:10:00</StartBoundary>
    <ExecutionTimeLimit>P1D</ExecutionTimeLimit>
    <Enabled>true</Enabled> <----- the correct value
    <ScheduleByDay>
    <DaysInterval>1</DaysInterval>
    </ScheduleByDay>
    </CalendarTrigger>

    to

    <CalendarTrigger>
    <StartBoundary>2025-05-28T06:10:00</StartBoundary>
    <ExecutionTimeLimit>P1D</ExecutionTimeLimit>
    <Enabled>false</Enabled> <----- the changed bad value
    <ScheduleByDay>
    <DaysInterval>1</DaysInterval>
    </ScheduleByDay>
    </CalendarTrigger>


    Changed it back to "true" and now they are backing up again.
    I could never find the problem in the Task Scheduler's edit,
    but I could have just missed it.

    So the tip is if you want to look at the XML code, right click
    on the task and export it. Then open the saved XML into
    notepad and make your changes. Of coarse save them.

    To import them, you have to right click on the task again
    and delete it. Then on the Scheduler's right pane, import
    the XML you just altered.

    Just not be on the safe side, make a backup copy of the
    original XML you saved before altering things.

    My hair should grow back soon.

    HTH someone else,
    -T
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.comp.os.windows-11 on Sun May 3 05:07:58 2026
    From Newsgroup: alt.comp.os.windows-11

    On Sat, 5/2/2026 5:23 PM, T wrote:
    Hi All,

    Speaking of the Task Scheduler, I just fixed an
    issue for a customer that is interesting.

    He had me change when his backup was scheduled
    so as not to interfere with a synchronizing program
    with his web site.

    Problem, his backup stop triggering.  It worked fine
    when run manually.  After considerable hair pulling,
    I decided to examine the XML code directly.  Found
    the problem right away.  Somehow, the XML had been
    changed from:

        <CalendarTrigger>
          <StartBoundary>2025-05-28T06:10:00</StartBoundary>
          <ExecutionTimeLimit>P1D</ExecutionTimeLimit>
          <Enabled>true</Enabled>             <----- the correct value
          <ScheduleByDay>
            <DaysInterval>1</DaysInterval>
          </ScheduleByDay>
        </CalendarTrigger>

    to

        <CalendarTrigger>
          <StartBoundary>2025-05-28T06:10:00</StartBoundary>
          <ExecutionTimeLimit>P1D</ExecutionTimeLimit>
          <Enabled>false</Enabled>             <----- the changed bad value
          <ScheduleByDay>
            <DaysInterval>1</DaysInterval>
          </ScheduleByDay>
        </CalendarTrigger>


    Changed it back to "true" and now they are backing up again.
    I could never find the problem in the Task Scheduler's edit,
    but I could have just missed it.

    So the tip is if you want to look at the XML code, right click
    on the task and export it.  Then open the saved XML into
    notepad and make your changes.   Of coarse save them.

    To import them, you have to right click on the task again
    and delete it.  Then on the Scheduler's right pane, import
    the  XML you just altered.

    Just not be on the safe side, make a backup copy of the
    original XML you saved before altering things.

    My hair should grow back soon.

    HTH someone else,
    -T

    According to the discussion here, AVG was doing this.

    https://stackoverflow.com/questions/65753183/win-10-task-scheduler-keeps-disabling-tasks

    Apparently it is an overzealous interpretation of "Do not disturb" in AVG :-/

    Is there nothing that antivirus programs cannot do ?

    Paul

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From T@T@invalid.invalid to alt.comp.os.windows-11 on Sun May 3 11:58:48 2026
    From Newsgroup: alt.comp.os.windows-11

    On 5/3/26 02:07, Paul wrote:
    On Sat, 5/2/2026 5:23 PM, T wrote:
    Hi All,

    Speaking of the Task Scheduler, I just fixed an
    issue for a customer that is interesting.

    He had me change when his backup was scheduled
    so as not to interfere with a synchronizing program
    with his web site.

    Problem, his backup stop triggering.  It worked fine
    when run manually.  After considerable hair pulling,
    I decided to examine the XML code directly.  Found
    the problem right away.  Somehow, the XML had been
    changed from:

        <CalendarTrigger>
          <StartBoundary>2025-05-28T06:10:00</StartBoundary>
          <ExecutionTimeLimit>P1D</ExecutionTimeLimit>
          <Enabled>true</Enabled>             <----- the correct value
          <ScheduleByDay>
            <DaysInterval>1</DaysInterval>
          </ScheduleByDay>
        </CalendarTrigger>

    to

        <CalendarTrigger>
          <StartBoundary>2025-05-28T06:10:00</StartBoundary>
          <ExecutionTimeLimit>P1D</ExecutionTimeLimit>
          <Enabled>false</Enabled>             <----- the changed bad value
          <ScheduleByDay>
            <DaysInterval>1</DaysInterval>
          </ScheduleByDay>
        </CalendarTrigger>


    Changed it back to "true" and now they are backing up again.
    I could never find the problem in the Task Scheduler's edit,
    but I could have just missed it.

    So the tip is if you want to look at the XML code, right click
    on the task and export it.  Then open the saved XML into
    notepad and make your changes.   Of coarse save them.

    To import them, you have to right click on the task again
    and delete it.  Then on the Scheduler's right pane, import
    the  XML you just altered.

    Just not be on the safe side, make a backup copy of the
    original XML you saved before altering things.

    My hair should grow back soon.

    HTH someone else,
    -T

    According to the discussion here, AVG was doing this.

    https://stackoverflow.com/questions/65753183/win-10-task-scheduler-keeps-disabling-tasks

    Apparently it is an overzealous interpretation of "Do not disturb" in AVG :-/

    Is there nothing that antivirus programs cannot do ?

    Paul


    And I had presumed I was the screw up!

    They are using ESET.
    --- Synchronet 3.21d-Linux NewsLink 1.2