Today we are re-releasing the November 2024 SUs for Exchange Server. The original release of these SUs (released on 11/12/2024) introduced an issue with Exchange Server transport rules stopping after...
Updated Jan 28, 2025
Version 11.0
Blog Post
Same with 0x800700B7 error on WS2016 + Exch2016 CU23 base (w/o SU).
Fixed by:
- Restoring services via reg file from backup with (Tryed .\servicecontrol.ps1 Afterpatch - didn't work for me. Maybe tryed to execute it too late but script doesn't restored correct order, only started all services)
- Reboot
- Compare inetpub, inetsvr and V15 directories via WinMerge with pre-patch snapshot to verify no corruption on MSI Rollback sequence occured
- Remove KB5049993 (will rollback to December patch, even if you have installed KB5049993 on earlier version)
- Reboot
- Install again November v2 patch again
- Reboot
- Install KB5049993 again
- Reboot
Funny thing: I've tested installation in testlab 3 times :D All was fine. And only step I've changed: installed Jan OS update :D And "Ah shiiiiiiit here we go again" meme comes into chat :D
Service restore file. Extracted via Diff from backup. Still missing 2 services: "Performance Logs & Alerts" and "W3SVC". Set first to "Manual", second to "Automatic". Updated. Added them to reg file too.
Moreover I've added manualy DependsOnService +MSExchangeADTopology to MSExchangeHM. Not always starting after reboot for me. Maybe my server RAID1 HDDs are too slow.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FMS]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HostControllerService]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IISADMIN]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeADTopology]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeAntispamUpdate]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDagMgmt]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDelivery]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDiagnostics]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeEdgeSync]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeFastSearch]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeFrontEndTransport]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeHM]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeHMRecovery]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeImap4]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIMAP4BE]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMailboxAssistants]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMailboxReplication]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangePop3]
"Start"=dword:00000003
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangePOP3BE]
"Start"=dword:00000003
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRepl]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRPC]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeServiceHost]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSubmission]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeThrottling]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeTransport]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeTransportLogSearch]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeUM]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteRegistry]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SearchExchangeTracing]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winmgmt]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wsbexchange]
"Start"=dword:00000003
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC]
"Start"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pla]
"Start"=dword:00000003
same problem nothing helped, im giving up on this, workaround not working
Can validate that uninstalling KB5050008 on Windows Server 2019 with Exchange 2019, restart, install November 2024v2 Exchange CU update, restart, install KB5050008, restart and all is well.
- Nino_Bilic
Microsoft
I just updated the blog post with our current understanding of the failure (we did reproduce this). The issue seems to be related to January .NET update having been installed, but the server was not rebooted after installation was completed.
Nino, we have just run into this exact problem on our Exchange 2019 server. Now the services are all in Disabled mode and I'm not sure from the comments if the workaround you introduced actually works or if there is a possibility of corruption? Please confirm how to move forward in this case. Also does this mean that we cannot proceed with installing the SU successfully?
- Nino_Bilic
Please see this article - this should help you recover the server to a working state:
File version error when you try to install Exchange Server November 2024 SU - Microsoft Support
Just wanted to give some feedback. This morning I reverted my DR environment restored Exchange server to the just restored state to test again. I ran healthchecker before and after a reboot to see what the Server Pending Reboot flag said and in both cases it was False. And after rebooting I tried the SU install and it failed again. So rebooting doesn't help our Exchange 2016 system.
- Nino_Bilic
Thanks for testing this!
I have just tested it once in an Exchange 2016 and 2019 environment and can confirm it. After a clean restart, the update installation went through successfully. previously it was cancelled in both environments.
