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.

Ben Murden
Ben Murden

Ben has over two decades in the IT industry, delivering both online and offline campaigns across all platforms to meet business goals and objectives. Joining Phoenix in 1999 as a graphic designer, Ben has evolved over the years into a fully-rounded marketing professional, before being promoted to Phoenix Marketing Manager early in 2018, reporting directly to the MD. With his background in creative design, Ben takes projects from inception to execution and can identify the correct strategy based on the subject, audience, and goals – while increasing the brand profile and revenue. His passion for digital marketing is evident in everything he does, and both vendors and strategic partners often comment on his incredibly positive attitude to ‘make things happen’.

See all posts by Ben Murden