Exchange 2016 no ECP after yesterday's patch

Hi,

We've installed Microsoft Tuesday's update for Exchange 2016 (KB5003435) & now there's no access to ECP or OWA & no outlook connection to the server as well.

All exchange services seem to be disabled, I've enabled them & when trying to start them there were 2 errors:

Get-Service | Where-Object { $_.DisplayName –like “Microsoft Exchange *” } | Start-
Service
WARNING: Waiting for service 'Microsoft Exchange Compliance Service (MSExchangeCompliance)' to start...
WARNING: Waiting for service 'Microsoft Exchange Diagnostics (MSExchangeDiagnostics)' to start...
WARNING: Waiting for service 'Microsoft Exchange Diagnostics (MSExchangeDiagnostics)' to start...
Start-Service : Service 'Microsoft Exchange Health Manager (MSExchangeHM)' cannot be started due to the following
error: Cannot start service MSExchangeHM on computer '.'.
At line:1 char:78
+ ... bject { $_.DisplayName –like “Microsoft Exchange *” } | Start-Service
+                                                             ~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
   ServiceCommandException
    + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand

Start-Service : Service 'Microsoft Exchange Health Manager Recovery (MSExchangeHMRecovery)' cannot be started due to
the following error: Cannot start service MSExchangeHMRecovery on computer '.'.
At line:1 char:78
+ ... bject { $_.DisplayName –like “Microsoft Exchange *” } | Start-Service
+                                                             ~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
   ServiceCommandException
    + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand

WARNING: Waiting for service 'Microsoft Exchange IMAP4 (MSExchangeImap4)' to start...
WARNING: Waiting for service 'Microsoft Exchange IMAP4 (MSExchangeImap4)' to start...
WARNING: Waiting for service 'Microsoft Exchange IMAP4 (MSExchangeImap4)' to start...
WARNING: Waiting for service 'Microsoft Exchange IMAP4 Backend (MSExchangeIMAP4BE)' to start...
WARNING: Waiting for service 'Microsoft Exchange IMAP4 Backend (MSExchangeIMAP4BE)' to start...
WARNING: Waiting for service 'Microsoft Exchange IMAP4 Backend (MSExchangeIMAP4BE)' to start...
WARNING: Waiting for service 'Microsoft Exchange Information Store (MSExchangeIS)' to start...
WARNING: Waiting for service 'Microsoft Exchange Information Store (MSExchangeIS)' to start...
WARNING: Waiting for service 'Microsoft Exchange Mailbox Assistants (MSExchangeMailboxAssistants)' to start...
WARNING: Waiting for service 'Microsoft Exchange Mailbox Assistants (MSExchangeMailboxAssistants)' to start...
WARNING: Waiting for service 'Microsoft Exchange Mailbox Assistants (MSExchangeMailboxAssistants)' to start...
WARNING: Waiting for service 'Microsoft Exchange Mailbox Assistants (MSExchangeMailboxAssistants)' to start...
WARNING: Waiting for service 'Microsoft Exchange Mailbox Assistants (MSExchangeMailboxAssistants)' to start...
WARNING: Waiting for service 'Microsoft Exchange Mailbox Replication (MSExchangeMailboxReplication)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePop3)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePop3)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePop3)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 Backend (MSExchangePOP3BE)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 Backend (MSExchangePOP3BE)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 Backend (MSExchangePOP3BE)' to start...
WARNING: Waiting for service 'Microsoft Exchange RPC Client Access (MSExchangeRPC)' to start...
WARNING: Waiting for service 'Microsoft Exchange Service Host (MSExchangeServiceHost)' to start...
Start-Service : Service 'Microsoft Exchange Transport (MSExchangeTransport)' cannot be started due to the following
error: Cannot start service MSExchangeTransport on computer '.'.
At line:1 char:78
+ ... bject { $_.DisplayName –like “Microsoft Exchange *” } | Start-Service
+                                                             ~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
   ServiceCommandException
    + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand

WARNING: Waiting for service 'Microsoft Exchange Unified Messaging (MSExchangeUM)' to start...
WARNING: Waiting for service 'Microsoft Exchange Unified Messaging (MSExchangeUM)' to start...
WARNING: Waiting for service 'Microsoft Exchange Unified Messaging (MSExchangeUM)' to start...
WARNING: Waiting for service 'Microsoft Exchange Unified Messaging (MSExchangeUM)' to start...
WARNING: Waiting for service 'Microsoft Exchange Unified Messaging Call Router (MSExchangeUMCR)' to start...

When I tried to start Microsoft Exchange Transport service I got "Error 1068: The dependency service or group failed to start"

Update: I've managed to start the Microsoft Exchange Transport service after enabling and starting the Microsoft Filtering Management Service.
Still the Microsoft Exchange Health Manager service can't start due to same "Error 1068: The dependency service or group failed to start"..

Update 2: Updating here helps me track my actions and may also help others having the same issue..
So the event viewer was stating that Microsoft Exchange Health Manager service couldn't start because Windows Management Instrumentation service was disabled, I've enabled and started it & Microsoft Exchange Health Manager service would then start as well

By now I also realize that installing Exchange updates through the windows update automatically is perhaps not a wise thing and that it'd been best to manually install it through an elevated command prompt (perhaps the auto-update doesn't have the elevation to reenable the services after the update finishes installing (honestly, why allow the update in the fist place without elevation if this is what we get?!%$).

Another remaining issue:
I've enabled and started the IIS Admin service but now getting Http error 404 (and email clients still not connecting).
If anyone can make this swifter for me I'd appreciate what are the steps to deal with this.

Last update: All seems to be resolved -Opening the IIS the sites were stopped. When trying to start them it was indicating the World Wide Web publishing service was disabled. took care of that and all seems to be alright currently

My question now is:
Is it alright to leave the Exchange auto-updates on (through the Windows update..) or should I check every Tuesday to see if there's a new Exchange patch and apply it manually through an elevated command prompt?
Was this really what caused the issue to begin with?