Exchange Services Not Starting After an SU? The Proven Fix

By Ahmet Tolga KAYA 9 min read
Exchange Services Not Starting After an SU? The Proven Fix

Exchange services not starting after a security update is one of those problems that looks far worse than it is. The installer finishes or rolls back, the server reboots, and then nothing: no mail flow, no Outlook on the web, and a Services console full of Microsoft Exchange entries that are stopped and set to Disabled. I have seen admins start planning a recovery install at this point. Hold on. In almost every case the databases are fine and the update was simply interrupted halfway. With the Exchange November 2026 security update rolling out this week, here is the order I work through, built on Microsoft’s own troubleshooting guidance.

Exchange Services Not Starting: Why It Happens After a Security Update

When you install a security update (SU) or cumulative update (CU), Exchange Setup stops the Exchange services and sets their startup type to Disabled, so that nothing restarts and locks a file in the middle of patching. At the end of a clean run, Setup puts everything back. If something interrupts the installation, that second half never happens and the services stay disabled.

The Exchange team says this in plain words in its November 2026 Exchange Server security updates post: restart after Setup, check that all Exchange services started, and if some are in a disabled state, something interrupted the installation of the update. So when I see Exchange services disabled after security update work, I read it as a symptom of an unfinished install, not as a broken server.

The usual interruptions, based on Microsoft’s Fix failed Exchange Server updates article:

  • Antivirus scanning or locking Exchange files while Setup runs. Microsoft tells you to set the documented antivirus exclusions or disable the product during setup.
  • An update started without elevation. Microsoft’s fix for several post-SU errors is to rerun the update from an elevated command prompt.
  • Services that did not stop cleanly, or a pending restart from an earlier installation. Microsoft recommends restarting the server before you install a CU or SU.
  • A permissions problem that ends in error code 1603 (The installer has insufficient privileges to access this directory).

Any of these can leave you with Exchange services not starting after the reboot.

One note on scope. The November 2026 SU was released for Exchange Server Subscription Edition only, and Microsoft states that Exchange 2016 and 2019 received no update this month. The recovery steps below are the same for all three versions, because Microsoft’s troubleshooting article covers CU and SU installs for Exchange Server in general, and the script lives in the same V15 folder.

Step 1: Confirm Exchange Services Not Starting Means Disabled

A case of Exchange services not starting deserves one clean restart before you touch anything. Then open Windows PowerShell as administrator and run the check from Microsoft’s article:

Get-Service -DisplayName "Microsoft Exchange*" | FT DisplayName, StartType, StatusCode language: JavaScript (javascript)
Exchange services not starting: Get-Service shows StartType Disabled after a security update (illustration)

The StartType column is what matters. A service that is Stopped but Automatic is a different problem from one that is Disabled. If you see a long list of Disabled entries, you have the interrupted-update pattern, and that is the whole reason you see Exchange services not starting.

Do not panic about four names in that list. By default the POP3 and IMAP4 services (MSExchangePOP3, MSExchangePOP3BE, MSExchangeIMAP4 and MSExchangeIMAP4BE) are stopped and not set to start automatically. Microsoft’s advice is to leave them alone unless your users need those protocols.

Next, read what Setup actually did. Every service that was disabled during the installation is written to ServiceControl.log:

Get-Content C:\ExchangeSetupLogs\ServiceControl.log -Tail 60Code language: CSS (css)

This log has saved me from guessing more than once. Microsoft is explicit that you should restore only the Exchange services that were active before the installation attempt, and ServiceControl.log is the record of which ones those were.

Step 2: Run ServiceControl.ps1 AfterPatch

This is the actual fix when Exchange services not starting is caused by a disabled startup type. Exchange ships a script that Setup itself uses to disable and re-enable services, and you can run its second half by hand. In the same elevated PowerShell window:

cd "C:\Program Files\Microsoft\Exchange Server\V15\Bin"
Add-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.Setup -ErrorAction SilentlyContinue
.\ServiceControl.ps1 AfterPatchCode language: CSS (css)

If Exchange is installed in a different folder, change the path in the first line. ServiceControl.ps1 AfterPatch sets the startup type of the Exchange services back to Automatic. Confirm it before you go on:

Get-Service -DisplayName "Microsoft Exchange*" | FT DisplayName, StartType, StatusCode language: JavaScript (javascript)

For Exchange services not starting, I prefer this over clicking through services.msc for two reasons. It is faster, and it is the documented method, so you do not accidentally enable a service that was never meant to run on that server.

Exchange services not starting fix flowchart: reboot, read ServiceControl.log, run AfterPatch, start services and rerun the update

Step 3: Start the Exchange Services

Now start them. Microsoft gives two variants. The first starts everything, the second skips POP3 and IMAP4, which is the one I use on servers that never ran those protocols:

Get-Service -DisplayName "Microsoft Exchange*" | Start-Service

Get-Service -DisplayName "Microsoft Exchange*" |
    Where-Object { $_.DisplayName -notlike "*POP3*" -and $_.DisplayName -notlike "*IMAP4*" } |
    Start-ServiceCode language: PHP (php)

If one service refuses to start, look at what it depends on before you blame Exchange. Active Directory Topology is the one most other Exchange services wait for, so I check it first, together with the IIS services that Outlook on the web needs:

(Get-Service MSExchangeADTopology).ServicesDependedOn | FT Name, StartType, Status

Get-Service W3SVC, WAS | FT Name, StartType, Status

If W3SVC or WAS shows up as Disabled in ServiceControl.log as well, set it back to its previous startup type and start it. This is usually where the Exchange services not starting problem ends for the users: they can connect again, and you have bought yourself time to finish the update properly.

Step 4: Finish the Interrupted Update

Getting past Exchange services not starting is only half the job. The update was interrupted, so the server may be on a mix of old and new files. Microsoft’s guidance for a failed install is short:

  • Rename the C:\ExchangeSetupLogs folder, for example to ExchangeSetupLogs-OLD, so the next run starts with clean logs. Keep the old folder for troubleshooting.
  • Make sure the Exchange services are started and set to start automatically, which Steps 2 and 3 already did.
  • Rerun the update with elevation. For an SU, open Command Prompt with Run as administrator, type the full path of the update file and press Enter. Restart the server when it finishes.

If you were installing a CU and Setup stopped with Cannot start the service Microsoft Exchange Service Host, the cause is the same disabled state. After Steps 2 and 3, resume Setup from the CU media. This example assumes the ISO is mounted as drive D:

D:\setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms_DiagnosticDataON

A small trap I want to flag: Microsoft warns that typing a bare setup.exe in PowerShell can run the copy in the Exchange Bin folder instead of the one on the media. Always use the drive letter or .\setup.exe.

For error code 1603, Microsoft’s first step is exactly the one above: start the stopped services, set them to automatic, and retry. If it fails again, check the folder named in the error for Read permission for Authenticated Users, Full Control for SYSTEM and the local Administrators group, and enabled inheritance. The general MSI error 1603 article covers the rest. When Setup still fails and you cannot tell why, run the SetupAssist script from the Exchange support team.

Step 5: Verify the Server Is Healthy

After the final reboot, open the Exchange Management Shell and check the roles, the build and the queues:

Test-ServiceHealth

Get-ExchangeServer | FT Name, AdminDisplayVersion

Get-Queue | FT Identity, Status, MessageCount
Exchange services not starting fixed: Test-ServiceHealth reports RequiredServicesRunning True (illustration)

Test-ServiceHealth should report RequiredServicesRunning : True for every role with nothing listed under ServicesNotRunning. When that is true, the Exchange services not starting incident is over as far as the roles are concerned. I also run the Exchange Health Checker script, because it tells you whether the server is behind on CUs, SUs or manual actions, which is the real proof that the update went in.

If you are past Exchange services not starting but mail still does not flow, Microsoft lists two more things to check: free disk space for the message queue database, and maintenance mode. A server that was put into DAG maintenance mode before patching stays there until you take it out:

Get-ServerComponentState -Identity EXCH01 | FT Component, State

Set-ServerComponentState EXCH01 -Component ServerWideOffline -State Active -Requester MaintenanceCode language: JavaScript (javascript)

Replace EXCH01 with your server name. The second command only makes sense if the first one shows components as Inactive and you were the one who set maintenance mode.

How I Avoid Exchange Services Not Starting on the Next Patch Day

  • Reboot first. Microsoft recommends restarting the server before a CU or SU so that no pending restart or stuck service blocks Setup.
  • Deal with antivirus before Setup runs. Verify the Exchange exclusions or pause real-time scanning for the maintenance window.
  • Always elevate. Start the update from an elevated command prompt, not by double-clicking it in a remote session.
  • Save the service state. I export the output of the Get-Service command from Step 1 to a text file before patching. If Exchange services not starting ever shows up again, I know exactly what normal looked like.
  • Do not uninstall the SU as a first reaction. Microsoft does not recommend uninstalling security updates, and a half-removed update is harder to repair than a half-installed one.

One last November detail. If you added the EpmapSavedContextCap registry value in October, the Exchange team says you can leave it in place, but it is no longer required once the November 2026 Windows Server updates are installed, and the order of the Windows and Exchange updates does not matter. I covered that issue in my Exchange OWA not working after October 2026 updates guide.

Read more: Exchange OWA Not Working After October 2026 Updates? Fix It Without Uninstalling

Read more: Exchange Published Calendar HTTP 500? The Proven Fix for Broken .ics Feeds

Read more: CVE-2026-96940: How to Patch the Exchange Server Flaw Safely

FAQ

Why are Exchange services not starting after a security update?

Exchange Setup disables the Exchange services while it patches and re-enables them at the end. If the installation is interrupted, the services stay Disabled and cannot start. Microsoft says disabled services after an update indicate that something interrupted the installation.

What does ServiceControl.ps1 AfterPatch do?

ServiceControl.ps1 AfterPatch is a script in the Exchange V15\Bin folder that sets the startup type of the Exchange services back to Automatic after an update. Microsoft documents it as the way to restore services that are left Disabled.

Where can I see which Exchange services were disabled by Setup?

Check C:\ExchangeSetupLogs\ServiceControl.log. It lists the services that were disabled during the CU or SU installation, so you can restore only the ones that were active before.

Should the POP3 and IMAP4 services be running?

Not by default. MSExchangePOP3, MSExchangePOP3BE, MSExchangeIMAP4 and MSExchangeIMAP4BE are stopped and not set to start automatically unless you configured them for your users.

Do I need to reinstall the update after fixing Exchange services not starting?

Yes. Starting the services restores access, but the update was interrupted. Rename C:\ExchangeSetupLogs, rerun the update from an elevated command prompt, restart, and confirm the result with the Exchange Health Checker script.

References

Microsoft Learn: Fix failed Exchange Server updates

Microsoft Exchange Team: Released: November 2026 Exchange Server Security Updates

Microsoft Learn: Running Windows antivirus software on Exchange servers

Microsoft Learn: Performing maintenance on DAG members

Microsoft Learn: MSI installation error 1603

Microsoft CSS-Exchange: Exchange Health Checker and SetupAssist

Ahmet Tolga KAYA

Systems Engineer and Technical Writer focused on Windows, Microsoft technologies, infrastructure, cybersecurity, automation, and platform reliability.