We have addressed the issue causing messages to be stuck in transport queues of on-premises Exchange Server 2016 and Exchange Server 2019. The problem relates to a date check failure with the change ...
Updated Jan 11, 2022
Version 36.0
Blog Post
Hi Nino_Bilic,
we have implemented the workaround with Bypassfiltering $true
Now we try to make the final solution: (manual or automated) on our to be cared 2016-2019 Server, all this are fully patched (MS Update, Exchange update,....)
ON Some we get the same error like
***Error starting the anti-malware engine update***
We started EX-Powershell as administrator also server is restarted before ,user has enough rigths on Server and Exchange, Domain,......
Also try to run manually Update-MalwareFilteringServer.ps1 <Our-Servername>.
Also try it with this.
Add-PSSnapin Microsoft.Forefront.Filtering.Management.Powershell
[PS] C:\>Start-EngineUpdate -Verbose
VERBOSE: [08:24:47.367 GMT] Start-EngineUpdate : Beginning processing
VERBOSE: [08:24:47.961 GMT] Start-EngineUpdate : Initiating engine Update für the following engines: Microsoft
VERBOSE: [08:24:48.149 GMT] Start-EngineUpdate : Ending processing
But we always get on some Exchange the error ***Error starting the anti-malware engine update***.
I have someone the detailed steps how you have fix this error?
TIA and Happy new Year to you
br
Johannes