Here in the forum and on the Exchange Team Blog there are indications that the installation of the November update for Exchange Server 2016 / 2019 may cause problems. It seems that once again there are problems with servers with German or non-English operating systems when the January update for the Windows Server is installed. The error and its possible solution also seem quite familiar to me. If I'm not mistaken, the problem has existed before.
When trying to install the November Update for Exchange Server on a Windows Server with the January Update installed, the following error message appears:
An error occurred during the installation of assembly 'Microsoft.Exchange.Data.Common,version="15.1. 2503.00", fileVersion="15.1.2507.44", culture="neutral",publicKeyToken="31BF3856AD36435", processor Architecture ="MSIL". For more information, refer to Microsoft Help and Support. HRESULT: 0x80070087.
At the time of the installation attempt, all Exchange services were still running. After restarting the server, the Exchange services were no longer started despite the "Automatic" start type. The Exchange server was therefore no longer functional after the restart.
Daniel has the solution to this error in the Forum posted. Thank you very much for the detailed article. Let me summarize briefly:
In the Exchange installation directory there are errors in the file "V15\bin\servicecontrol.ps1", apparently the commands "Stop-SetupService" and "Start-SetupService" are used here, but they do not exist.
Daniel has worked around this problem by adapting the script and adding appropriate aliases. He has written his solution in great detail in the forum so that the corresponding changes can be reproduced.
I don't remember the commands "Stop-SetupService" and "Start-SetupService", I think that was a problem before. Probably an old error has crept in again.
Incidentally, I was also unable to reproduce the problem on Exchange servers with an English operating system and January update. Unfortunately, there are always problems on operating systems in other languages.
If the Exchange November Update still needs to be installed, it is probably better to install the Exchange Update first and then the January Windows Update. I don't think Microsoft will release a new security update for Exchange now or fix this problem.
The CU15 for Exchange 2019 should not be long in coming, as CU15 contains the November update, the update should be tested thoroughly.