Microsoft releases a fix for the Y2K22 bug that affected Microsoft Exchange servers

Microsoft Exchange had a rocky start to the New Year, as the popular email service was hit by a Y2K22 bug, which prevented users from accessing their inbox. After investigating, they found that mail was getting stuck in the queue, and the Windows event log showed one of the following errors: These errors are caused by Microsoft Exchange checking the version of the FIP-FS antivirus scanning engine and attempting to store the date in a signed int32 variable. In a post in its support forums, Microsoft says: "We've created a solution to address the problem of messages stuck in transport queues on Exchange Server 2016 and Exchange Server 2019 because of a latent date issue in a signature file used by the malware scanning engine within Exchange Server. Fortunately, the computer apocalypse never came to pass, with only minimal disruptions recorded, but the issue has come back to plague some Microsoft Exchange servers 22 years later.