On 8/7/2026 11:09 AM, Tim Parenti via tz wrote:
On Fri, 7 Aug 2026 at 10:33, James Bellaire via tz <[email protected]> wrote:
Microsoft's blog has announced changes to support the time zone
changes in British Columbia and Alberta.
I had been starting to wonder when they would get to that.
Remaining versions of Windows will receive the update as part of
October 2026 monthly quality update."
Worth noting that October's "Patch Tuesday" is 13 October 2026, less
than three weeks before these changes take effect. Additionally, only
a handful of LTS releases of Windows 10 continue to enjoy support:
https://endoflife.date/windows
As workarounds on unsupported versions, users in British Columbia can
select Arizona for year-round UTC−7, while those in Alberta can select
Saskatchewan for year-round UTC−6.
BC could also chose Yukon time.
On Fri, 7 Aug 2026 at 10:48, Robert Bastian via tz <[email protected]> wrote:
Clocks will not be advanced by an hour at 12:00 a.m. on
November 01, 2026, for the British Columbia time zone.
Yes, they won't be advanced, but they also won't be turned back,
which is really the more important part.
That is indeed quite an unfortunate error for as long as the guidance
took to prepare.
I read that as their way of saying "DST will end" November 1st at the
same time as the base time is set to UTC-07 instead of UTC-08.
Probably could say at 2am but it may be easier to code a change at
midnight if they are going to support historical dates and times.
There is still a "(UTC-05) Indiana (East)" time zone in Microsoft and
that has not been distinct from "(UTC-05) Eastern Time (US & Canada)"
for 20 years. Support for files created when there was a distinction?
Good to see movement. Especially on zones where the government has
completed their work of legislating the change.
