All Services • vGRID Cloud Services

Is vGRID Cloud Services having problems? vGRID Cloud Services is up and running

vGRID Cloud Services problems reports in the last 24 hours

This chart shows the number of reports in the last 24 hours. It's normal to see a few reports, but if you see a lot of reports, it means that the service might be going through some issues.

Latest vGRID Cloud Services outage from official status page

Windows 2022 Server will cease to boot with security violation error

Microsoft’s latest cumulative update released for 'Windows 2022 Server' will cause virtual machines (VM's) which have the 'Secure Boot' option enabled, to stop booting. Windows Patch: • 2023-02 Cumulative update for Microsoft server operating system version 21H2 for x64-based Systems (KB5022842) Impact: • This issue will affect any VMs that are running ‘Windows 2022 Server’ and have 'Secure Boot' enabled as part of the base configuration. The 'vGRID Windows 2022 Server' template has this option enabled, therefore any VM's that were deployed from this template will also have 'Secure Boot' enabled. • The installation of the update and the initial reboot of the VM to apply the update will occur without issue. • Once the cumulative update (KB5022842) has been installed/applied & the 'Secure Boot' option is still enabled on the VM, the VM will experience the error on the next OS boot. Note: Uninstalling the update (KB5022842) will not resolve the issue. Resolution: 1. Do not install the KB5022842 patch on any Windows 2022 Server virtual machine until the issue is resolved. 2. Disable the Secure Boot option on the virtual machine. • The virtual machine needs to be powered off before this change can be applied, so please contact the vGRID Service Desk and schedule a time. Once the VM is fully powered off, we are able to untick the option and power the server back on again. • If the VM has already been updated and is not able to boot, please contact the vGRID Service Desk using the toll-free number (0800 425 383) so that this can be actioned quickly. For more information regarding this issue, please refer to the VMware Support article: https://kb.vmware.com/s/article/90947

Created about 1 year ago