News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Task Scheduler not working (for some) in Win10 Anniversary Update

    Posted on October 24th, 2016 at 11:50 woody Comment on the AskWoody Lounge

    I’m just starting to clear out the backlog. Could you tell?

    Here’s another known bug in Win10 1607 – the Anniversary Update – that hasn’t yet been officially acknowledged, much less corrected.

    http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/task-scheduler-jobs-not-working-after-anniversary/ba7f453d-87b3-4b04-ae31-cbfb290d48a4?auth=1

    Since the Windows 10 Anniversary Update was automatically installed on my machine, jobs in Task Scheduler no longer run as they did previously. The scheduled jobs are failing with error “2147943767” and “2147943726”.

    Lost of discussion – SpiritX is trying hard to help – but no answers.

    If that helped, take a second to support AskWoody on Patreon

    Home Forums Task Scheduler not working (for some) in Win10 Anniversary Update

    This topic contains 19 replies, has 5 voices, and was last updated by  Some Dude 2 years, 1 month ago.

    • Author
      Posts
    • #29916 Reply

      woody
      Da Boss

      I’m just starting to clear out the backlog. Could you tell? Here’s another known bug in Win10 1607 – the Anniversary Update – that hasn’t yet been off
      [See the full post at: Task Scheduler not working (for some) in Win10 Anniversary Update]

    • #29917 Reply

      Some Dude

      For an OS that’s collecting all the data and details of everyones’ machines, every piece of software, every photo, video, and document, my passwords, EVERYTHING! YOU THINK THEY’D BE ABLE TO FIGURE OUT THE PROBLEMS AND FIX THEM! GOD!

    • #29918 Reply

      SureThing

      2147943767 = 0x80070557
      2147943726 = 0x8007052E

      0x80070557 = ERROR_INVALID_LOGON_TYPE
      # A logon request contained an invalid logon type value.

      0x8007052E = ERROR_LOGON_FAILURE
      # Logon failure: unknown user name or bad password.

    • #29919 Reply

      fp
      AskWoody Lounger
    • #29920 Reply

      PKCano
      Da Boss

      I wonder it the telemetry tasks still work?

    • #29921 Reply

      woody
      Da Boss

      🙂

    • #29922 Reply

      woody
      Da Boss

      I don’t entirely agree with this assessment, because it underplays the role of pure, blind luck.

    • #29923 Reply

      ch100
      AskWoody_MVP

      Which tasks specifically don’t work which were working before?
      There was a similar glitch in Windows 7 or 2008 R2 after applying Service Pack 1, which was not visible on all machines.
      The solution in those situations was to export tasks from a known good machine and import them in the machine with the failed tasks.

    • #29924 Reply

      fp
      AskWoody Lounger

      To analyze all the data and draw conclusions they do not have the necessary resources.
      So they focus on narrow segments that they deem critical or profitable and the likelihood that the interest of users is prominent is pretty low.

      In fact, the more they are overwhelmed by d ata on problems, the less they will try to solve them and focus instead of glossing over them and intensify marketing.

    • #29925 Reply

      Anonymous

      Task Scheduler not working? Good! The only thing I can see it doing is uploading telemetry, perhaps they can break it permanently!

      If our government spent half as much $$$ on Data Security as they do Surveillance we would all be in better shape!

      This place is getting more messed up by the minute…

    • #29926 Reply

      fp
      AskWoody Lounger

      His point is that if you are a CEO you can’t RELY on long term luck and if you don’t get it you must ensure both vision and execution.

      If you read carefully the history, most huge success stories are based on exploiting the ideas of others and or luck that were in no way envisioned. This is forgotten and they are made “visionaries”, which is sheer nonsense.

      Gates and Jobs exploiting ideas of others and benefitted from sheer luck. Zuckerberg got extremely lucky 2ice when he was actually failing.

      None of these people are what they are made up to be. They are deemed geniuses when they are nothing of the kind.

    • #29927 Reply

      Michael

      I guess that’s one way to stop a lot of the telemetry phone-home stuff. 🙂

    • #29928 Reply

      woody
      Da Boss

      Fitzgerald: You know, the rich are different from you and me.

      Hemingway: Yes. They’ve got more money.

    • #29929 Reply

      fp
      AskWoody Lounger

      Its what they do w it that makes them different.

    • #29930 Reply

      b

      Haven’t all of these very few users affected been able to find a very simple workaround?

      Certainly the original poster whose description you quote solved her issue more than two months ago by changing her task to run as System user.

      Your headline dramatically overstates the situation (as usual) by making it sound like a problem for everyone and all scheduled tasks rather than a few isolated, unusual cases.

      The title was reasonable when used by the OP to summarize her specific question, but it’s not reasonable (just lazy) to re-use it to introduce a general article about “another known bug”.

    • #29931 Reply

      woody
      Da Boss

      Looks like it’s a continuing problem. Susan Bradley reported on Oct. 19 that she’s “Checking on the eta for a fix, hang loose.” I haven’t seen any acknowledgment of the problem, a solution, or an ETA.

      The folks I’m most concerned about are the ones who don’t have the Scheduled Task(s) run – and don’t have a clue what a “Scheduled Task” is.

      When I say “X not working” I’m not saying “X not working for anyone, in any circumstance.”

    • #29932 Reply

      Noel Carboni

      There was a whole Task Scheduler flap when build 10586 came out too, where the stored information for many scheduled tasks was not properly interpreted by the new version.

      That this could happen – over and over – implies that Microsoft has lost proper focus on compatibility and continuity.

      -Noel

    • #29933 Reply

      b

      This minor issue is not affecting anyone who doesn’t have a clue what a scheduled task is.

      If it’s only affecting a few, your headline could make that clear; right now it makes it sound like it’s totally broken for everyone.

    • #29934 Reply

      Noel Carboni

      With all due respect, you can’t say whether it will affect someone, as many applications schedule their own components. Maybe it means some common application that a whole lot of folks rely upon just doesn’t work right.

      The Task Scheduler is an important part of the OS. Please don’t overgeneralize or marginalize those who need it.

      -Noel

    • #29935 Reply

      b

      I used the current tense, because so far there’s only evidence of it affecting a few users who have created their own scheduled tasks (less than 10 users, most of whom have confirmed one of three simple workarounds). To pretend otherwise is to overgeneralize.

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Task Scheduler not working (for some) in Win10 Anniversary Update

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.

    Your information: