Interesting Windows 10 bug...

I have the switch from Daylight Saving Time to regular Daylight Time as an event in my calendar, from 2am to 3am this morning, and this is, of course, how it shows up in my calendar (both in Calendar and Outlook). However, when I click on the taskbar clock it brings up an agenda that has this event pegged from 2pm to 3pm. Apparently some doofus forgot to distinguish between am and pm somehow. Oh well, typical for the kind of fit and finish to expect from Microsoft in general, and Windows 10 in particular.

Mine has always switched automatically no matter what OS I have. Maybe I don't understand what or why you did anything.

I almost never use the event calendar on my computer, so whatever is in it is strictly built-in. Having not entered anything at all manually myself, my calendar shows end of Daylight Savings Time as an all day event today starting at 12:00 AM. I'm calling user error on whomever entered 2:00 pm to 3:00pm . The hours are not even correct. Daylight Savings Time ended at 02:00AM and which time the clock should be reset to 01:100 am. 3:00 am or pm has nothing to do with it.

Sorry guys, you completely misunderstood this: this has nothing whatsoever to do with the handling of the time change (which Windows does just fine; seriously, it can't be that completely unusable as to be unable to handle a crucial feature of that magnitude). The issue is that a calendar event, any calendar event, that has been entered for the time between 2 and 3am is shown in agenda as occurring in the afternoon between 2 and 3pm. And, no, it is completely irrelevant what that event is for, or if the user timed the event right, or anything of that sort. I could have an event labeled "gobbledeegook" in there, and the exact same thing would have happened. Hope this helps...

essenbe said:

@Pirx, a bug constitutes something that happens to all machines. Thus far yours is the only post I have seen of this happening. I also did not see any posts last week when the EU had their time change. Therefore it is obviously not a bug.

Whoah, there's some creative logic there... See above. This is about the handling of certain calendar events, not about the time change.

essenbe said:

[MENTION=102014]It is also not something wrong with Windows 10

It's most definitely a bug in Windows 10. Feel free to give it a try.

Pirx said:

Sorry guys, you completely misunderstood this: this has nothing whatsoever to do with the handling of the time change (which Windows does just fine; seriously, it can't be that completely unusable as to be unable to handle a crucial feature of that magnitude). The issue is that a calendar event, any calendar event, that has been entered for the time between 2 and 3am is shown in agenda as occurring in the afternoon between 2 and 3pm. And, no, it is completely irrelevant what that event is for, or if the user timed the event right, or anything of that sort. I could have an event labeled "gobbledeegook" in there, and the exact same thing would have happened. Hope this helps...

Yes, that does clarify. I can't verify, but it would seem to me like Windows should not adjust any event time on the calendar. If I put a meeting in for 3:00PM - to me that means 3:00PM and when the actual clock hits 3:00pm that's when the meeting occurs. If I scheduled that meeting for today at 3:00pm two weeks ago, it should be the naturally inferred intent that it occurs when the clock hits 3:00PM today regardless of the stupid adjustment back one hour that occurred at 2:00am.

I'll set an event now for 2:30am in the spring and see if the whole system crashes when the clock skips from 2:00am to 3:00 am . All that SHOULD happen is at 1:00 am the system says you have an invent in 1/2 hour. Then the next minute at 3:00 am it should say your event happened 1/2 hour ago.

That's an interesting point, too: Both Outlook and Mail continue to show the event occurring from 2-3am. The Calendar app on my iPhone, on the other hand, now shows this as occurring from 1-2am. Which one is "the right way" may be debatable.