Microsoft Exchange 2016/2019 Y2K22 bug
Microsoft customers are experiencing an issue that is causing messages to be stuck in transport queues on Exchange Server 2016 and Exchange Server 2019.
The problem – which started at 00:00 on 01.02.2022 – has been triggered by a date check failure created by the change of a new year from 2021 to 2022 and is not a failure of the AV engine itself.
Microsoft has confirmed that it is not an issue with malware scanning or the malware engine, and it is not security related. The version checking performed against the signature file is resulting in the malware engine crashing, resulting in messages getting stuck in transport queues.
Microsoft has released a workaround, which can be found within its Tech Community pages.
For support or assistance with this on-going issue, contact us.