0
Solved: Microsoft Exchange Y2K22 Bug
Some users on our site reported problems with Microsoft Exchange at the turn of the year:
This bug in the Microsoft Exchange server has ensured that emails can no longer be delivered since January 1, 2022. The bug, now called "Y2K22", has now been fixed by Microsoft.
Admins can either run the Y2K22 fix manually or use the Reset-ScanEngineVersion.ps1 script.
To run the script, you need to open the Exchange Management Console and change the execution policy for Powershell scripts with Set-ExecutionPolicy -ExecutionPolicy RemoteSigned.
If you have disabled the anti-malware engine, as Microsoft recommended in an initial proposal, it must be re-enabled with the Enable-AntimalwareScanning.ps1 script.
Here is the official FAQ and solution from Microsoft:
Email Stuck in Exchange On-premises Transport Queues
- Exchange und der Jahr 2022 Bug beim Antimalwarescanning (German)
- Exchange Y2K22 Bug: Kein Versand von Mails über Outlook mehr (German)
This bug in the Microsoft Exchange server has ensured that emails can no longer be delivered since January 1, 2022. The bug, now called "Y2K22", has now been fixed by Microsoft.
Admins can either run the Y2K22 fix manually or use the Reset-ScanEngineVersion.ps1 script.
To run the script, you need to open the Exchange Management Console and change the execution policy for Powershell scripts with Set-ExecutionPolicy -ExecutionPolicy RemoteSigned.
If you have disabled the anti-malware engine, as Microsoft recommended in an initial proposal, it must be re-enabled with the Enable-AntimalwareScanning.ps1 script.
Here is the official FAQ and solution from Microsoft:
Email Stuck in Exchange On-premises Transport Queues
Share on Facebook
Share on Twitter
Share on Reddit
Share on LinkedinPlease also mark the comments that contributed to the solution of the article
Content-ID: 1684205815
Url: https://rootdb.com/en/solved-microsoft-exchange-y2k22-bug-1684205815.html
Printed on: February 23, 2025 at 06:02 o'clock
