Change the execution policy for PowerShell scripts by running Set-ExecutionPolicy -ExecutionPolicy RemoteSigned.
Download the Reset-ScanEngineVersion.ps1 script from.To use the automated script to apply the fix, you can follow these steps on each on-premise Microsoft Exchange server in your organization:
This fix comes in the form of a PowerShell script named 'Reset-ScanEngineVersion.ps1.' When executed, the script will stop the Microsoft Filtering Management and Microsoft Exchange Transport services, delete older AV engine files, download the new AV engine, and start the services again.
Microsoft has released a temporary fix requiring customer action while working on an update that automatically fixes the issue. "The version checking performed against the signature file is causing the malware engine to crash, resulting in messages being stuck in transport queues," Microsoft explained in a blog post. However, this variable can store only a maximum value of 2,147,483,647, which is less than the new date value of 2,201,010,001 for January 1st, 2022, at midnight.ĭue to this, when Microsoft Exchange attempts to check the AV scanning version, it would generate a bug and cause the malware engine to crash. These errors are caused by Microsoft Exchange checking the version of the FIP-FS antivirus scanning engine and attempting to store the date in a signed int32 variable. Log Name: Applicationĭescription: The FIP-FS Scan Process failed initialization. Error Description: Can't convert "2201010001" to long. Log Name: Applicationĭescription: The FIP-FS "Microsoft" Scan Engine failed to load. After investigating, they found that mail was getting stuck in the queue, and the Windows event log showed one of the following errors. Microsoft has released an emergency fix for a year 2022 bug that is breaking email delivery on on-premise Microsoft Exchange servers.Īs the year 2022 rolled in and the clock struck midnight, Exchange admins worldwide discovered that their servers were no longer delivering email.