If you awoke on January 1st, 2022, and located that your work electronic mail’s inbox was unusually empty, you aren’t alone. Microsoft rang within the New Year with a bug that forestalls Exchange servers from sending emails, however fortuitously, a repair has since been issued, as detailed in a report by Bleeping Computer.

“The problem relates to a date check failure with the change of the new year and is not a failure of the AV engine itself,” Microsoft explains in a post on its Tech Community forum. “The version checking performed against the signature file is causing the malware engine to crash, resulting in messages being stuck in transport queues.”

Microsoft outlines the answer to the issue in its put up, requiring directors to both implement the repair manually or apply an automatic script. The put up additionally accommodates an in depth FAQ, noting that the answer “will take some time” for directors to implement. And relying on what number of emails are caught within the queue, it might take some time for the messages to land of their meant recipients’ inboxes.

Problems began cropping up at midnight on January 1st, with an Exchange administrator on Reddit calling consideration to the difficulty. As defined by Bleeping Computer, directors started noticing error messages within the Exchange Server’s Event Log, reminiscent of “The FIP-FS Scan Process failed initialization. Error: 0x8004005. Error Details: Unspecified Error” or “Error Code: 0x80004005. Error Description: Can’t convert “2201010001” to lengthy.”

Administrators had been compelled to provide you with alternate options throughout the time it took for Microsoft to deal with the difficulty, however now that the corporate has launched an official repair, it seems to be just like the Y2K22 disaster is over.