I'm curious, has anyone else tested this? @JimChev3 You said you didn't have the issue, but that your agents were up to date, so did you actually run the task and was the server itself targeted?
For anyone testing on your production environment, please take a snapshot or backup first, rolling back was my only way to get things running again.
I can consistently reproduce the issue on a fresh install of the new VA as detailed below.
Steps to reproduce the issue:
Deploy as per https://help.eset.com/protect_deploy_va/11.0/en-US/deployment_on_vsphere_esxi.html
Config with name, password, domain & DC as per https://help.eset.com/protect_deploy_va/11.0/en-US/config_va.html
Log-in to the web console.
Run ESET PROTECT Components Upgrade task targeting the All group.
Then try to log-in to the web console.
The problem appears to be that the ESET PROTECT Server service is not running. In Webmin, it is no longer available in the System > Bootup and Shutdown list after the ESET PROTECT Components Upgrade task is run.