Microsoft fixes harebrained Y2K22 Exchange bug that disrupted email worldwide

Microsoft fixes harebrained Y2K22 Exchange bug that disrupted email worldwide

Enlarge (credit: Getty Images)

signed integers, which max out at 2147483647, or 231 – 1. Microsoft uses the first two numbers of an update version to denote the year it was released. As long as the year was 2021 or earlier, everything worked fine.

“What in the absolute hell Microsoft?”

When Microsoft released version 2201010001 on New Year’s Eve, however, on-premises servers crashed because they were unable to interpret the date. Consequently, messages got stuck in transport queues. Admins around the world were left frantically trying to troubleshoot instead of ringing in the New Year with friends and family. All they had to go on were two cryptic log messages that looked like this:

Read 4 remaining paragraphs | Comments