@UKTechHub
.
.

Reply To: Remember the Y2K bug? Microsoft confirms new Exchange Y2K22 issue As digital calendars around the world changed to 01.01.2022, Microsoft customers found their Exchange servers stopped processing emails. Microsoft says it is aware of a programming flaw which saw some…

UKTH forums 💻 Computers Servers Et al Remember the Y2K bug? Microsoft confirms new Exchange Y2K22 issue As digital calendars around the world changed to 01.01.2022, Microsoft customers found their Exchange servers stopped processing emails. Microsoft says it is aware of a programming flaw which saw some... Reply To: Remember the Y2K bug? Microsoft confirms new Exchange Y2K22 issue As digital calendars around the world changed to 01.01.2022, Microsoft customers found their Exchange servers stopped processing emails. Microsoft says it is aware of a programming flaw which saw some…

#16909
UK SentinelUK Sentinel
Keymaster
  • Replies 8,581
  • The Skipper

What actually went wrong?

The technical issue seems to lie with the way that Microsoft was naming updates for its malware-scanning engine, putting the year, month, and day (220101) at the front of another four-digit number (0001).

Microsoft seems to use this system because when an update is named “2,201,010,001” it is simple to mathematically check which update is the most recent as it will have the higher value.

In a completely sane world, madness is the only freedom (J.G.Ballard).

Latest Posts