Microsoft has delivered an emergency fix for its email services that was hit by Y2K22 bug starting January 1. It blocked up Exchanges on-premise servers, whereby users were unable to access their inbox.
“We have addressed the issue causing messages to be stuck in transport queues of on-premises Exchange Server 2016 and Exchange Server 2019. The problem relates to a date check failure with the change of the new year and it not a failure of the AV engine itself,” said Microsoft in a blog post.
The issue is of date check failure with the change of the new year and not a security issue.
“This is not an issue with malware scanning or the malware engine, and it is not a security-related issue. The version checking performed against the signature file is causing the malware engine to crash, resulting in messages being stuck in transport queues,” the blog post added.
The fix provided by Microsoft can be operated automatically or done manually.
Microsoft said that it has “now 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.”