This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 84%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
I started to update client exchange servers to the latest CU (one client uses 2013 standard and another 2016 standard). Both updates deleted dll files from the directories. One server i was able to restore them from a backup to get the exchange services running. The other server however i am not so fortunate. no exchange services will start. They were left in a disabled state after the update failed. restoring a backup i took before the update ran into problems because the machine account lost its trust with the domain controller, removing and readding did not solve the problem - additionally, exchange doesn't show as being installed in add remove programs. I have been waiting over a week for Microsoft support to respond, all i get are notices that it is taking longer than normal to assign a tech. We have already been forced to route mail to an cloud provider just to get email but we still need our history. I am posting this as a warning to anyone who is looking to install the latest CU. Make sure you have a very good disaster recovery plan because this affected 2 out of 2 exchange server i tried it on (a 2013 and 2016). Shame on Microsoft for releasing such a horrible patch, there is no way something like this should ever happen with a failed update.
Hi @TheDude ,
Good day!
As you said you installed the latest CU update for Ex 2013 and 2016, what's the version or do you mean you installed the security update? And I guess it's 2016 that's facing a service disabled issue right?
Can you set the services to automatic start and then start the services? Will it work?
For this issue, you could try https://www.reddit.com/r/exchangeserver/comments/lxfd8u/2013_kb5000871_killed_my_server_and_this_just/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
Lou
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @TheDude ,
Do the suggestions above help? If the issue has been resolved, please click “Accept as answer” to mark helpful reply as an answer, this will make answer searching in the forum easier and be beneficial to other community members as well.
Regards,
Lou
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
unfortunately the link doesn't help. To answer your question about what version this problem occurred with, both a 2013 and 2016 exchange server. Same exact symptoms experienced on both servers (missing DLL files, services set to disabled). Trying to set the services to automatic and start them fails immediately. One server was repaired by restoring the files from a backup, the other server is still not functioning properly and it's state degraded severely after trying to fix the problem (exchange doesn't even show as being installed any longer in add/remove programs).
Hi @TheDude ,
Thanks for sharing those info, as you said one of them was fixed while the other one was still in trouble, is the problematic one Ex 2016?
And please try recovering Exchange with: Recover Exchange servers. Or if it's Exchange 2016 CU19, you could try upgrading it to CU20.
Regards,
Lou
the problematic one is exchange 2016. I restored a backup and tested the latest CU with the same result. i will try the recover option...looks like that will take some time and planning to get a test environment setup. for the time being it seems that there isn't a known solution to this problem. I am having a hard time finding anyone else reporting this issue but it happened on two separate client servers in completely different environments so i have to image many other exchange environments are having this problem.
Hi @TheDude ,
Yes, for now there are no certain solutions for this issue, the Microsoft Official Doc is still like a ..
Repair failed installations of Exchange Cumulative and Security updates It's real-time update.
BTW how did you install the update? Others using Admin PowerShell seem have no issue.
I've seen a similar case, after installed CU20, other services all starting but EX Transport service.
Regards,
Lou
i try started the services but the stop because of dependencies. The root dependency is the Microsoft Filtering Management Service. I found it was looking for DLL files that were deleted during the setup. I restored those from a backup and the service would attempt to start but eventually fails. Event view shows an "unknown error" with the service startup and nothing online seems to address the issue. At this point i restored a full VM backup and had other AD related issues but i can at least migrate user mail boxes to a new server. I am not going to put anymore time into this as it seems there is not really anything i can do and microsoft has still not responded to the ticket i opened with them. A full paid support ticket and they don't even respond. Microsoft let the world down with this and the way they handled the situation.
no, it depends on the MS filtering management service. If i could have repaired the MS filtering management service it probably would have been ok but at this point i have moved on.
Hi @TheDude ,
Any error messages when you trying to start these services?
As I know and like the doc says, the other services are depended on MS AD Topology service. Exchange services on Mailbox servers
Have you tried to recover Exchange server with recovery mode? Or moved to a new server?
Regards,
Lou
