For those who 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 12 months with a bug that stops Change servers from sending emails, however luckily, a repair has since been issued, as detailed in a report by Bleeping Pc.
“The issue pertains to a date verify failure with the change of the brand new yr”
“The issue pertains to a date verify failure with the change of the brand new yr and isn’t a failure of the AV engine itself,” Microsoft explains in a submit on its Tech Neighborhood discussion board. “The model checking carried out in opposition to the signature file is inflicting the malware engine to crash, leading to messages being caught in transport queues.”
Microsoft outlines the answer to the issue in its submit, requiring directors to both implement the repair manually or apply an automatic script. The submit additionally incorporates an in depth FAQ, noting that the answer “will take a while” for directors to implement. And relying on what number of emails are caught within the queue, it could take some time for the messages to land of their supposed recipients’ inboxes.
Issues began cropping up at midnight on January 1st, with an Change administrator on Reddit calling consideration to the difficulty. As defined by Bleeping Pc, directors started noticing error messages within the Change Server’s Occasion Log, akin to “The FIP-FS Scan Course of failed initialization. Error: 0x8004005. Error Particulars: Unspecified Error” or “Error Code: 0x80004005. Error Description: Can’t convert “2201010001” to lengthy.”
Directors have been pressured to give you alternate options through the time it took for Microsoft to deal with the difficulty, however now that the corporate has launched an official repair, it appears just like the Y2K22 disaster is over.