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(294.40000000000003, 56.00000000000001%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Hello We seem to be getting a issue where once we patched one of our Windows Server 2016 Exchange 2016 CU19 exchange servers yesterday with the latest Windows Updates, the Exchange Transport and Exchange Health Manager services are now stuck in a starting state and never go into the running state. We have restarted the server many times, restarted the domain controller in the same site, uninstalled a couple of the updates on the exchange server however this has not helped! See attached pictures of the updates installed, a couple of events we get when we force stop and start the transport service and a picture of the starting state of the transport service. Thanks Charlei[69634-pic1.png][1]![69651-pic2.png][2]![69558-pic3.png][3]![69559-pic4.png][4] [1]: /api/attachments/69634-pic1.png?platform=QnA [2]: /api/attachments/69651-pic2.png?platform=QnA [3]: /api/attachments/69558-pic3.png?platform=QnA [4]: /api/attachments/69559-pic4.png?platform=QnA
![](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(252.8, 22%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELL%3C/text%3E%3C/svg%3E)
Hi @CharlieRix ,
Did you try to manually stop the MS Exchange transport and Exchange health manager service and start it again?
I noted that you has been uninstall a couple of updates, it’s include the latest Windows Updates?
According to the error information, it’s could cause by service startup time is too long resulting in timeout, You can try to editing or creating the ServicesPipeTimeout DWORD value, the Service Control Manager timeout period can be overridden, thereby giving the service more time to start up and report ready to the Service. But it should be noted that if you modify the registry incorrectly, it will have a serious impact, so it is recommended that you back up in advance.
In addition, if running a third-party anti-virus and anti-spam software, if possible, try to temporarily turn it off.
----------
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 @CharlieRix ,
Do 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.
Thanks for your understanding.
----------
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 @CharlieRix ,
I am writing here to confirm with you how thing going now? If the above suggestion helps, please click “Accept as answer” to mark helpful reply as an answer.Your action would be helpful to other users who encounter the same issue and read this thread.
Thanks for your understanding.
----------
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.