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(310.4, 20%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHP%3C/text%3E%3C/svg%3E)
Hi,
I did a search but had trouble narrowing down to my specific so, hopefully, this is not a repost.
Running Exchange 2016 Std virtualized in WS2016 Std environment. Installed CU20 fine. Rebooted. Now Exchange services takes 30 minutes to load and, usually, not everything starts. After waiting, I tend to need to manually start Frontend Transport and a few other required services.
Also, two other issues have propped up. After a while (not set time period), a CMD process pops up and uses 80-90%+ CPU and 4-6GB or memory. This grinds Exchange down to a halt. I log in and run Task Manager. When it comes to, I terminate that CMD process and everything is fine again.
The other issue is that I can no longer install any Microsoft Updates after CU20. It downloads and installs then I get the "reverting back" after a few reboots.
None of the old WS2012 Std / Exchange 2013 Std setups are affected. All the WS2016 Std/Exchange 2016 Std setups experience the same issue.
Any suggestions?
Thanks in advance,
Hedwig Poon
![](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(28.799999999999997, 82%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEY%3C/text%3E%3C/svg%3E)
Hi,
In my lab(CU20), no issues like you describe have appeared.
1 How often does the CMD show? What does it say if you don't stop it?
2 Do you have other servers with Win2016 with no Exchange server installed or with other CUs of Exchange 2016 installled? Test if they can install Windows updates.
Check the Event log. there might be errors telling you the reason.
If an Answer 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 Eric,
Thanks for responding.
I checked the event viewer but I couldn't find any specific error listing that coincided with the CMD process. It had lots of error launching Exchange services but eventually they launch.
I've read somewhere some people were having W3WP error. Sometimes, I pop in via OWA to see if it's still working (quick response). If the just spins, I figured it's got that CMD process again. I wonder if OWA is causing it.
Hedwig
Spoke too soon. One site just spiked CPU.
Also, these events are shown:
I've attached a renamed EVTX file as a .log so I can upload it. 86061-21-04-08-eventsevtx.log
Lastly, after terminating the CMD process, I see these in the event viewer (looks OWA related).
Regards,
Hedwig
Hi,
Those Exchange errors can be solved, following these links:
https://support.microsoft.com/en-us/topic/msexchangeapplicationlogic-event-3018-in-exchange-server-2013-and-2016-65582c77-ff32-653a-8397-e1e72a64a074
https://social.technet.microsoft.com/Forums/en-US/2f935339-efa1-44ad-92e1-fbdb7b844e4c/event-msexchangeapplicationlogic-3025-amp-3018?forum=Exch2016Adm
And I think you should enable tls 1.2 as default: https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-tls-guidance-part-2-enabling-tls-1-2-and/ba-p/607761
For the issues about CMD and Windows updates, not sure if it's caused by Exchange, but looks more related to windows server. I would try solving those Exchange errors here.
Thx for those.
No proxy servers are used and I ran Qualys SSL test to confirm sites are using TLS 1.2. The second link page discussed enabling the TLS in registry after adding the SCHANNEL keys so I did. We'll see.
I disabled OWA to test but it still had the CMD pop up. In fact, I just checked and the rogue CMD process popped up again using 76%+ CPU so launch Task Manager takes a long time.
Terminating that process restores function.
Further, in checking the error/warning/critical list of the Event Viewer, the Application log shows OWA related issues as well as ASP.NET 4.0.30319.0 listing. I did Recycle the Application Pools items per the link.
Is there a way to revert back to CU19? I did not experience this issue with that update.
Thx again.
Hedwig
Hi，
Is your server directly installed with Exchange 2016 cu20, if so, the answer is no. You can only revert back from your full backup.
Does enabling tls 1.2 make a change?
Hi Eric,
Yes, it has CU20 installed. That's when we noticed the issue. CU19 was working normally but the "must-install" notification I received advising to install CU20 prompted me to go ahead. It already had TLS 1.2 enabled since the beginning.
In fact, it's stuck with the CMD at 80% again. No response so just waiting out for Task Manager so I can End Task this offending process.
Sadly, our system image ran so it will have CU20 on as well (we only keep one image from the week's backup). We have daily data backup but that's not going to help.
Is there a paid option? We need to resolve this as it's killing off multiple 2016 sites and my customers are ready to kill. :-(
Thx.
Hedwig
Open a ticket here: https://support.microsoft.com/oas/
Be free to post any progress and solutions back.