Did you know that 2008 was a dual leap year? Probably not since I made up the whole "dual leap year" tag, but what I do mean is that we had a February 29th this year and we’ll also have an extra leap second added to our clocks tomorrow night.

The problem is that Microsoft won’t really catch up with that second until later.

It turns out the deal is that Microsoft doesn’t recognize (or ignores) the alert in the atomic time codes that says a leap second is being added to the time adjustment. When the leap second is added at 12:59:59 tomorrow night, Microsoft won’t catch it and will just adjust the clock on your computer the next time it syncs after tomorrow night.

As you can see in the image above though, I can’t connect to the time.windows.com website URL to update my time anyway. Makes me wonder if their working on a fix right now maybe even though their Knowledge Base Article 909614 states otherwise.

Does anyone really care though? Are you going to stress out over it? If you’re Microsoft maybe you can smirk and know that at least for a little while you can really claim you’re a step ahead of Apple on something.

Hat Tip: Douglas Karr at Marketing Tech Blog

Image: Snagit of Windows Time and Date Properties Dialog box

Post from: EveryJoe

Hey Microsoft! Got a Sec?