During the transition to the new year, many emails got stuck in the Exchange Server queue in versions 2016 and 2019. This issue has since been fixed, according to Microsoft. In any case, many users characterized it as a New Year’s bug.
We all remember the Y2K bug preventing computer dates from changing to the year 2000, due to IT development issues. Microsoft would have done it again for the new year 2022?
A hiccup due to a date problem
The transition to the year 2022 was not without a hitch for everyone. Indeed, the IT giant Microsoft suffered a bug in its Microsoft Exchange messaging service, blocking the sending of emails to recipients.
According to the preliminary investigation reported by Bleeping Computer, the Microsoft Exchange bug was caused by a date problem, because the IT multinational uses an int32 on its mail server. This can support a maximum value of 2 147 483 647. However, the date of 1er January 2022 has a value of 2,201,010,001. This incident caused the crash of the antivirus scanning system, which in turn affected the mail service, thus preventing e-mails from being sent.
Microsoft is still working on an update to automatically fix this bug. In the meantime, there is a manual solution to temporarily work around the problem, by running the “Reset-ScanEngineVersion.ps1” PowerShell script. Before that, however, it is essential to modify the PowerShell script execution policy by running “Set-ExecutionPolicy – ExecutionPolicy RemoteSigned”. This will stop Microsoft Filtering Management and Microsoft Exchange Transport from working, download the malware update, and restart the program.
Source: TechRadar
0