Microsoft has made a decision about addressing the new time-related change for Manitoba
Updated Oct 27, 2026
Version 5.0I see the new time zone in Windows and Outlook classic but importing an iCalendar file with TZID:America/Winnipeg and a valid VTIMEZONE definition still imports using the US rules. Is that a known issue? Is a different TZID being used. New BC and Alberta imports work as expected. Sample ics below.
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:Manitoba
X-WR-TIMEZONE:America/Winnipeg
BEGIN:VTIMEZONE
TZID:America/Winnipeg
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;UNTIL=20251102T070000Z;BYMONTH=11;BYDAY=1SU
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;UNTIL=20261101T070000Z;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0500
TZNAME:Central Time
DTSTART:20261101T020000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Monthly Manitoba
DTSTART;TZID=America/Winnipeg:20261014T090000
DTEND;TZID=America/Winnipeg:20261014T100000
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
RRULE:FREQ=MONTHLY;UNTIL=20271015T000000Z;INTERVAL=1
LAST-MODIFIED:20261014T133217Z
CREATED:20261014T133300Z
DTSTAMP:20261014T133217Z
UID:asdgfapdsgawsrdf
END:VEVENT
END:VCALENDAR