<div dir="ltr">There is an interesting comment on that (#7) that suggests that <a href="http://time.windows.com">time.windows.com</a> may have been down and that switching to the NIST servers fixed things.<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">--Matthew Donadio (<a href="mailto:matt@mxd120.com" target="_blank">matt@mxd120.com</a>)<br></div></div>
<br><div class="gmail_quote">On Mon, Apr 3, 2017 at 2:35 PM, Paul Eggert <span dir="ltr"><<a href="mailto:eggert@cs.ucla.edu" target="_blank">eggert@cs.ucla.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Chris Keall of the National Business Review (New Zealand) reports that laptops and phones running Microsoft Windows 10 missed the end of daylight saving time in New Zealand yesterday. Microsoft Windows 7 laptops operated correctly. This leads me to think that the problem has something to do with the tz database, as MS-Windows 7 does not use tzdata whereas MS-Windows 8.1 and later use tzdata, at least in some cases. Does anyone have technical information about why the glitch happened? Is there some way we can help avoid it in the future?<br>
<br>
Keall C. Living in the past: Windows 10 fails to update for end of daylight saving. NBR 2017-04-03. <a href="https://www.nbr.co.nz/article/living-past-windows-10-fails-update-end-daylight-saving-ck-201449" rel="noreferrer" target="_blank">https://www.nbr.co.nz/article/<wbr>living-past-windows-10-fails-u<wbr>pdate-end-daylight-saving-ck-2<wbr>01449</a><br>
</blockquote></div><br></div>