Summit 7 Team Blogs

Exchange Services Not Starting? Windows Security Update Disables Exchange Services (pertaining to Exchange 2013/2016, Update KB4045655)

Microsoft has released an Exchange security update recently – KB4045655 - and there's been plenty of noise around it and others.  This patch has an issue that can render Exchange 2013/2016 inoperable, and (in short) the update fails - BUT  not before disabling all Exchange services.  As a result, these services are not able to be started manually, and installation of the security update via the control panel repeatedly fails. 

After a bit of investigation (via the Exchange log files), we’ve found that the reason behind this is a PowerShell call to an alias CMDLET that doesn’t exist natively.  See screenshot below.



The resolution is moderate and can be performed within half an hour.  It involves:

  • Creating a PowerShell Profile for the administrator performing the resolution (if not already exists)
  • Creating an alias inside the PowerShell Profile
  • Downloading the failed Exchange security update and installing manually
  • Starting all Exchange services and dependency services


Follow the procedures below to resolve this issue

Download patch (CU6): https://www.microsoft.com/en-us/download/details.aspx?id=56330

Download patch (CU7): https://www.microsoft.com/en-us/download/details.aspx?id=56331

Set the following Services to Automatic and Start them:

  • IIS Admin Service
  • Microsoft Filtering Management Service
  • World Wide Web Publishing Service

Create a PowerShell Profile:

New-item –type file –force $profile

Notepad $profile

. $profile


Create an Alias inside your PowerShell Profile and save (i.e. %userprofile%\Documents\WindowsPowerShell):

New-Alias Stop-SetupService Stop-Service

Install appropriately-versioned patch:


Restart all necessary Exchange 2016 services via PowerShell:

$svc = Get-Service | ?{$_.displayName -match "microsoft exchange" -and $_.displayname -notmatch "imap4" -and $_.displayname -notmatch "pop3"}


$svc | Set-Service -StartupType automatic

$svc | Start-Service

Ensure all services listed in the first step remain auto and started.

That's it! If you continue to run into trouble, please contact us - and we can provide additional support for your Exchange environment and others.


Subscribe Here!

Recent Posts