![]() ![]() I have seen the other threads, however none of the threads specifically lists a specific recurring type as the issue.Ĭan you reproduce the issue with your system?Ģ) set first run on January 1st 2022 (so it defaults to standard time)ģ) select run every week, check the "current" day of week and set a time runtime 2 minutes in ahead of your current system time (given that you are now in daylight saving time) The issue is also present on newly created jobs and also persists after restarting the machine. Maybe the issue fixes itself next week, however this is a very strange, annoying an inconsistent behavior. With the daily setting the task is started at the correct time! Amazing! So there seems to be some sort of bug when using the the "once per week on a specific day option". Out of curiosity I just changed the task to repeat daily instead of every Monday. When 19:00 passes, the task is not repeated, and the displayed time when the task is run next is moved ahead 1 week. However the task is executed one hour early at 28th March 18:00. ![]() So the task keeps being aligned with UTC. Now with DST in effect, the scheduled task overview window displays the next runtime correctly as 28th March 19:00. The scheduled tasks windows displayed the next runtime correctly. I configured the task in a way that it's first runtime is on 18:00 every Monday (thus standard time is used). Therefore I checked the "Synchronize accross time zones" option within the scheduled task options. I have several tasks in my windows 10 task scheduler that need to be aligned with UTC, thus independent of DST changes. This weekend, EU switched from standard time to DST. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |