Apple Watch Users Report 1-Hour DST Glitch on watchOS 27 in Europe

Q: Why does Apple's advanced watchOS 27 system clock keep perfect time while its display stubbornly refuses to fall back?

It appears to be a display-refresh bug, not a failure of watchOS 27’s core timekeeping. Reports from UK and central Europe indicate the Apple Watch is calculating local time correctly: when users actively wake the watch, it shows the right post-daylight-saving time hour. The problem is that the Always-On display and standby mode can remain stuck on the old summer-time offset, leaving the watch face looking one hour fast after clocks changed. That fits how Apple’s Always-On mode works. In wrist-down mode, the dimmed watch face does not behave like the fully active interface; Apple says it refreshes glanceable information on a limited schedule, often once a minute, to save battery. If the daylight-saving transition was not properly pushed through to that low-power display layer, the system clock could be correct while the cached face shown in Always-On mode remained stale. The fact that some users fixed the issue by restarting the watch or changing the watch face strengthens that explanation. Both actions force the display system to reload its state and re-render complications and the time display, which can clear a stuck offset without changing the underlying clock. Apple has not yet said which models or specific watchOS 27 builds are affected. A broader test will come when the United States falls back on November 1, which may show whether the bug is tied specifically to Europe’s DST transition rules or to Always-On display handling more generally.

Q: With the US time change looming, will your Apple Watch's Always-On display trick you into waking up an hour early?

Possibly, but there is no sign yet that this is a widespread U.S. problem. The reports so far are from Apple Watch users in the UK and central Europe after clocks moved back on Sunday, and the bug appears limited to the Always-On display and standby mode. In those cases, the watch showed the correct time when fully awake, while the dimmed screen stayed on summer time and looked one hour fast. That matters because it suggests this is a display-refresh glitch, not a full clock failure. If your watch wakes and shows the right time, alarms, system time, and normal timekeeping may still be correct even if the wrist-down screen looks wrong. The U.S. time change on November 1 will be the next real test of whether the same behavior appears more broadly. Apple has not said which watch models or watchOS 27 builds are affected. Some users said a simple restart fixed it. Others said changing the watch face cleared the problem, which fits the idea that the Always-On display is failing to refresh properly after the daylight saving switch. If you rely on your watch overnight or first thing in the morning, the safest step before the U.S. change is to install the latest watchOS update, then restart the watch after the clocks change. If the Always-On screen still looks an hour off, wake the watch fully to verify the actual time, and try switching watch faces or temporarily turning Always-On off and back on.

2 articles · Updated · MacRumors · Oct 26

Five users in a MacRumors forum thread said watchOS 27 left the Apple Watch Always-On display one hour fast after clocks went back in the UK and Europe on Sunday.
The watches reportedly show the correct time when activated, but the Always-On display—and in some cases standby mode—continues showing summer time.
Three users said restarting the watch fixed the issue, while a sixth poster said switching watch faces also resolved it.
Apple Watch models and watchOS 27 versions affected remain unclear, with the issue drawing extra attention before most U.S. clocks go back on November 1.