December 2021 Exchange Server Cumulative Updates postponed

MS Exchange Team posted an update/fix, but forgot to mention it here.

PepperdotNetthey used your suggestion: "verify the UpdateVersion information is 2112330001" 

See: https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-transport-queues/ba-p/3049447

hi 

I can create a new Datastore but cannot move any mailboxes and the move option fails as my search is not uptodate.........

So I am stuck 

In reply to the comment ..... Users can not search in Outlook 

Create a new Exchange Datastore and migrate a User to the new Datastore. Test the search function it should work in Outlook.

Migrate all users and delete the old Datastore.

The fix, when it comes, will probably be in the form of a patch to fix the affected components to use something bigger than an unsigned long integer datatype to store the version number.

A quick workaround, which should fix the problem instantly, would be for them to stop releasing the updates as "220101xxxx" and go back to something like "211301xxxx" as in the 13th month of 2021, that should get them plenty of time to develop a proper fix.

Thanks to all those that helped.  This had us stumped and glad I came across this.  We bypassed for now to get our smtp working, but MS releasing something with a bug figures.  Let us know when you get an update and kudos!

Thank you very much for sharing that link David Richard.

I had the same problem yesterday at 23PM!

Event ID: 7036 - The Microsoft Filtering Management Service service terminated unexpectedly. It has done this 14 time(s).

Event ID: 1106 - The FIP-FS Scan Process failed initialization. Error: 0x80004005. Error Details: Unspecified error

Event ID: 5300 - The FIP-FS "Microsoft" Scan Engine failed to load. PID: 61872, Error Code: 0x80004005. Error Description: Can't convert "2201010001" to long.

I tryed this, but no success:

Add-PsSnapin Microsoft.Forefront.Filtering.Management.Powershell

Get-EngineUpdateInformation

cd "C:\Program Files\Microsoft\Exchange Server\V15\Scripts'

$Computer = $ENV:ComputerName

.\Update-MalwareFilteringServer.ps1 -Identity $Computer

I used this workaround yesterday temporarily:

Get-TransportAgent "Malware Agent" | Disable-TransportAgent -Confirm:$false

Stop-Service msexchangetransport

sleep 5

Start-Service msexchangetransport

Get-TransportAgent "Malware Agent"

Any fix?

audi911 use https://www.alitajran.com/exchange-mail-flow-breaks/

the updates are shown below.

Where are people looking to get an official response from MS?

Is there a site where we can track what is going on and when a fix will be issued?

Can't believe it - 17 hours later and still no comment from the Microsoft regarding the "2022" Bug 😞