Error after rebooting VM

[p360_rchavez]

I am trying to figure out what is going on with this VM, I rebooted the VM and it is coming up directly to the boot manager. In the Event log, it says, no operating system found, so I attached the Windows Server 2022 ISO and booted it, but now I am getting this error. I attached the screenshot. Can someone help?

[RDPetruska]

What VMware product and version are you using?

[p360_rchavez]

vCenter 6.7

[Alfista_PS]

Hi,

how you have set the VM in settings?

And its only one VM or are depend more VM's?

 

[p360_rchavez]

Please see attached settings. 

[p360_rchavez]

It is only 1 vm so far, but strange this is, I tried to create a new VM and ran into the same issue. Does this like the picture attached. 

 

 

[RajeevVCP4]

Do one thing to check disk corrupted  or not 

create a dump vm without disk.

remove disk from problematic vm (check data store path before remove disk, vm edit setting  --copy that path of disk in notepad )

create a dump vm and at the time of add disk , use existing disk and provide path which you copied. once done power on vm if its work then you can add rest of disk in this vm from old vm.

 

[PrashantG]

Try Enabling / Disabling Secure boot option in boot setting of virtual machine.

1. Browse to the virtual machine in the vSphere Client inventory.
2. Right-click the virtual machine and select Edit Settings.
3. Click the VM Options tab, and expand Boot Options.
4. Under Boot Options, ensure that firmware is set to EFI.
5. Select your task.
   • Select the Secure Boot check box to enable secure boot.
   • Deselect the Secure Boot check box to disable secure boot.
6. Click OK.

Remove the ISO attached and check.

[p360_rchavez]

I tried this and same result. 

[Alfista_PS]

This last issue happens when you don't have there installed OS.

Now you have build EFI so you need to top a new install of the OS you will.

You can do it from CDROM, but sometimes happens even you set it in the settings that it start at connecting and use a image that it doesnt do.

You need then open VRMC nd there set the image again set both connecting and restart the VM. Then it should read it. Sometimes happens that you need to do it more times that it start working. I don't know why it happens but I have many times this problem by building a new system, and their I then do from it an template for later use again.