We just ran into this (I've already reported it to MS with no response... We have to have the time on the machines at least close for our software). 

Of 100 client computers audited 100 of the machines had not synchronized since the US daylight savings time patch was released.
Of those 100, all of them that installed the patch in the middle of the night as part of an auto-update, had their date/times off by exactly a day.


This is on different networks, different installs of Windows, Windows XP, Windows Vista, Windows 2003 Servers, different IT departments, different routers etc. so it isn't anything BUT Windows causing the issue.

The only way to get it to work again is to run this script:

net stop w32time
w32tm /unregister [ignore error message]
w32tm /unregister [enter a second time]
w32tm /register
reg add hklm\system\currentcontrolset\services\w32time\parameters\ /v NtpServer /t reg_sz /d time.nist.gov /f
net start w32time
w32tm /resync

And then restart.

time.windows.com doesn't work at all no matter what you do. The others don't work unless you run the script above to reset the Windows Time Service.

MS really really really needs to fix this.  Some of these computers are out enough that SSL won't work any more amoung other encryption issues....

And how it's gone this long without anyone at MS noticing or doing anything about it boggles the mind....