Virtual Machine with Windows Server 2022 KB5022842 (OS Build 20348.1547) configured with secure boot enabled not booting up

 

we are facing a issue with windows server 2022 Virtual Machine was update to latest patch's with KB5022842.

 Server is not booting showing error with operating system not found.

we are using VMware ESXi, 6.7.0, 15160138

Server Configuration :-


  • Model:ProLiant DL380 Gen9
  • Processor Type:Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz


    • After the Windows Server 2022 update KB5022842 (OS Build 20348.1547) has been installed, virtual machines running on vSphere ESXi 6.7 U2/U3 or vSphere ESXi 7.0.x that have secure boot enabled may experience difficulty in booting up the guest operating system.

    In VMWare article says we need to update to the latest version of ESXI7 u3or Esxi8.

    https://kb.vmware.com/s/article/90947


    Now the VM was not boot we don't have backup of VM also, what we did is download the vmdisk files and vm.vmx file to a local server and install the VMware Workstation Pro 17 from vmware site.

    install it  in local server connected the vmx file to it.


    we power on the VM, It automatically cleanup the windows update patches in the Virtual Machine. we disable the services of windows update and rename the software distribution folder file in the windows folder

     

    Now our VM was up and Running the trick works for me try it if you have any issue with Windows server 2022 VM.  ,


    To disable Secure Boot on Virtual Machines (VMs), follow the steps below:

    1. Open the VM Settings window.

    2. Select the "Security" tab.

    3. Uncheck the box labeled "Enable Secure Boot".

    4. Click "OK" to save the changes.

    Comments

    Post a Comment

    Popular posts from this blog

    Zabbix Server is not working: the information dispaly may not be current

    Image
      Details  Cannot display item queue. Connection to Zabbix server "localhost:10051" refused. Possible reasons: 1. Incorrect "NodeAddress" or "ListenPort" in the "zabbix_server.conf" or server IP/DNS override in the "zabbix.conf.php"; 2. Security environment (for example, SELinux) is blocking the connection; 3. Zabbix server daemon not running; 4. Firewall is blocking TCP connection. Connection refused Observation:- In Centos 9 [root@nmtool ~]# systemctl status zabbix-server.service ● zabbix-server.service - Zabbix Server      Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: d>     Active: activating (auto-restart) (Result: exit-code) since Fri 2023-02-03 10:36:52 IST;>    Process: 57289 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCC>    Process: 57295 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)    Main PID: 57291 (code=exited, status=0/
    Read more

    How to install VNX Launcher that has embedded java and Firefox

    Image
      Alternative for Adobe Flash Player to access Unisphere. Symptoms VNXe Unisphere in older OE revisions is not accessible after December 31, 2020. The Adobe Flash Player plug-in is no longer supported in browsers. VNXe Unisphere used to require a browser with the Flash Player plug-in. Cause When VNXe is running an older OE revision, Adobe Flash Player is required by Unisphere. Refer: https://elabnavigator.emc.com/vault/pdf/EMC_VNXe_ESSM.pdf?key=1588743011568 Adobe has expired Flash Player as of December 31, 2020.   Details: https://www.adobe.com/products/flashplayer/end-of-life.html Resolution Newer VNXe OE revisions support HTML5. Once the VNXe is upgraded, Unisphere will work. Since December 31, 2020 browsers do not support Adobe Flash Player. Most browsers support HTML5. VNXe Unisphere must also support HTML5 in order to use VNXe Unisphere. HTML5 support is delivered in these VNXe revisions:       VNXe3200: VNXe Operating Env
    Read more

    DHCP FAILED APIPA IS USED

    Image
    Hi to all, In a Cisco packet tracer while i am trying to connect the dhcp server to pc it will getting the error like dhcp failed. APIPA is being used. For this issues this is also one reason.dhcp is not configured correctly. If we create a  vlan's in the switch's and we configured dhcp server in the layer 3 switch or layer 2 switch or in router. VLAN 10 NAME SALES VLAN 20 NAME DATA We created two vlan's now creating dhcp server for that  Switch(config)#ip dhcp pool name sales (should be the vlan name. not any other name.) Switch(Dhcp-config)#network 192.168.10.0 255.255.255.0  Switch(dhcp-config)#default-router 192.168.10.1 Switch(dhcp-config)#exit Swithc(config)#ip dhcp pool name data Switch(dhcp-config)#network 192.168.20.0 255.255.255.0 Switch(dhcp-config)#default-router 192.168.20.1 Switch(dhcp-config)#exit
    Read more