Released: May 2025 Exchange Server Hotfix Updates

It was a long time since we had any problems with an exchange update but this time it happened.

We did the same procedure as always fresh rebooted server after any windows update. Run the update in an elevated command prompt.

This time we had run Windows update to apply June security updates to both of our Windows 2019 Servers in an Exchange 2019 CU15 DAG.

First server issues after Exchange update:

Installer told us processes was in use. Retry did not work for us. The same dialog appeared again. We decided to cancel it and skip the update for now. That did not work. After that all exchange service was in a disabled state. We tried to re-run the update and then it completed sucessfully. But still all services was in a disabled state. We put them in automatic start and rebooted the server. Got some error that Exchange service host terminated all the time. We found out that world wide web publishing service also had been disabled and IIS admin service. After enabling automatic start it worked.

Second Server issues after Exchange update:

Exchange update run successfully with out issues. Rebooted server. Thought everything was fine. Later users complained about HTTP error 500 (directory not found, or something like that). The update must have messed up the virtual directories for OWA. After googling we found that the updatecas.ps1 script found in exchange installation could repair. We tried that and it worked.

So this time the patching was a nightmare.