Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, November 11, 2017 10:23 AM | 1 vote
Ever since I upgraded my Win10 to ver. 1703 [original Creators' Update], I started having a problem that was never a problem before. I have certain tasks set to run every 2 weeks (i.e., every 14 days). So, the same calendar day ... every other week. What started happening with ver. 1703 is that the "every 2 weeks" parameter gets ignored and the system executes the task every week. Here, a couple examples: two tasks, having run on 10/08, were not supposed to run again until 10/22 ... but they got run on the next Sunday (10/15) anyway....
________________________________________________________________________________
Well, since then, I upgraded again, to the Fall Creators' Update (ver. 1709). But we have the same problem. Again, a task that wasn't supposed to run until next Sunday was run last Sunday morning. (The reason it failed was because the full system backup task was already running.)
I definitely suspect this is a bug (and reported it as such through the Feedback app; no response from there yet). Thoughts, anyone?
All replies (16)
Monday, November 13, 2017 2:35 AM | 1 vote
Hi,
Thank you for your detail description.
What's the previous Windows version that this task schedule works well before?
I will feedback the issue to product team today, and also I will test this issue on my side. As the test period needs one week for result, please be patient for it.
Bests,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Sunday, November 26, 2017 6:35 AM
Sorry not to have replied sooner; I didn't get a notification somehow.... This wasn't a problem for me with either the Anniversary Update (v. 1607) or v. 1511 before that.
Monday, November 27, 2017 1:47 AM
Hi,
Thank you for your feedback. The issue has been feedback to Microsoft Product department. They will analyses the issue on multiple environment, and various device. Please patience to they deep research.
Bests,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, November 30, 2017 7:58 AM
I should also add, perhaps - it might matter? - that I came to Windows 10 via an in-place upgrade from Win 8.1 to Win 10 v. 1511.
Thursday, November 30, 2017 10:48 AM
Hi,
"I should also add, perhaps - it might matter? "
Sorry for not understanding the sentence clearly. Would you explain more specific?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Sunday, December 3, 2017 1:32 PM
In other words: I have Windows 10 due to an in-place upgrade from Windows 8.1 ... if, by chance, that matters - I've read in several places that in-place upgrades don't always go cleanly. I'm thinking I might need to do a clean re-install of Windows 10, but I'm not sure if that will truly make a difference or not - since, by design, each version of Windows 10 is, in effect, an in-place upgrade.
Monday, December 4, 2017 1:45 AM
Hi,
I would apologize for my action in last week. At first I configured this task on my Virtual Machine, but I reinstall it after several days later after configured. So last week I reconfigured this task on my Virtual Machine too. I could get the test result in this Wednesday. I would recommend to keep your machines in the existing status, after the result I got, I will reply to you immediately.
Bests,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, December 6, 2017 10:16 AM
Hi,
I configured the task scheduler and set the time to every Wednesday every 2 weeks last week on Windows 10 1709 virtual machine. So the next run time it writes should be 13/12 2017. But the task not run today(not advance as yours). I will continues to monitor it until next Wednesday to check again.
Bests,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, January 2, 2018 11:10 AM
Any further insight as to why my issue could be happening? It still is going on. I'm having to manually edit my batch file back and forth, so that on the Sundays I don't want it executing, I "REM" out the "delete" command, and remove the REM on the Sundays it's supposed to run.
Saturday, February 24, 2018 3:21 AM
I've been having the same issue on my computer as well. Windows 10 Pro, currently on 1709 but it started doing this after upgrading to 1703. I have a scheduled task configured to run every two weeks (runs a batch file that automatically backs up some files to a NAS), but instead it runs every single week.
I do not know WHY this is happening, but there is a small workaround I added to my own batch file. This will guarantee the batch file only runs every other week, with no need to keep editing it to disable and re-enable the commands within it.
Add the following commands to the beginning of your batch file:
if exist %temp%\week.1 goto skiprun
if exist %temp%\week.2 goto dorun
if not exist %temp%\week.1 echo.>%temp%\week.1
:skiprun
rename %temp%\week.1 week.2
exit
:dorun
rename %temp%\week.2 week.1
...[Rest of your batch file goes here]...
Basically, it creates a small file in the TEMP folder, which it then uses to make sure the batch file only runs to completion every other time it is called. Admittedly this is not a perfect solution, because even though the batch file won't run in full, it will still briefly flash up on the screen before closing, potentially interrupting whatever it is you are doing if you're using the computer at the time. Also, if you regularly delete the contents of you TEMP folder, this will reset the counter and prevent the batch file from ever running...although in this case you can simply modify my code above to save the counter file somewhere else.
It's not a fix to the underlying Task Scheduler problem, but it does at least allow you to work around it. Unfortunately, at this point, it seems to be the only way to avoid this glitch.
Thursday, March 22, 2018 7:20 AM
same here tasks not working
Saturday, March 31, 2018 12:05 PM
That's a thought, but what I ended up doing is manually disabling the bi-weekly tasks on the off-weekends; that's the only way I can be sure they don't run. It's still a problem even now.
Wednesday, April 18, 2018 8:10 PM
Has the Microsoft guy gotten back to you on this. It is a bug that I am need of a solution to as well. Mine was a clean install of Win 10 on a new machine. So the issue was never an upgrade from a previous version. I am seeing this issue occurring in other posts on the internet as well. It doesn't look like any response has occurred on the topic from MS since December on this thread.
Tuesday, April 24, 2018 1:58 PM
I have the same issue with Windows 10 Enterprise. My bi-weekly task runs every week.
Friday, September 13, 2019 7:54 AM
I have the same issue after update to Windows 10 Education 1903 from Windows 7. And this is two years later!?
Tuesday, May 19, 2020 6:52 PM
Yes ... and up through version 1909, this still remains a problem, exactly as described originally. I've seen it happen on different PC's and with different programs since I posted this issue in late 2017. So it's definitely not a machine- or software-specific issue; it's definitely a Task Scheduler bug. Seeing that there's never been a fix for this, I've had to adjust my backup scheduling cycles to go around the issue.