Friday, 1 Jul, 2022

Someday, one of my servers failed to boot up one of my virtual machines.

For whatever reason, I did figure out that the Hyper-v Role got disabled on boot.

 

ISSUE.

RDCMan-amatesi@smptvx_(smptvx.lan.pwrusr.com)_-_Remote_De-2017-05-13_21-08-04

Hyper-V Manager

An error occurred while attempting to start the selected virtual machine(s).
'vm-name' failed to start.
Virtual machine 'vm-name' could not be started because the hypervisor is not running.
'vm-name' failed to start. (Virtual machine ID 6280CC5E-4E1 E-44CO-8D5F-g8E58732C1 C8)
Virtual machine 'vm-name' could not be started because the hypervisor is not running (Virtual machine ID 6280CC5E-4E1 E-44CO-8D5F-g8E58732C1 G).
The following actions may help you resolve the problem: 1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.
2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on. Resetting the physical computer is not sufficient.)

3) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.



FiX.


(On Command Prompt or Windows PowerShell As Admin):


BCDEDIT /set hypervisorlaunchtype auto


Restart your Hyper-V Host then try again.
















            


    


            

            



        

            

            



        

            

            



        

            

            



        

            

            



        

    

    


            

            



        

            

            



        

            

            



        

            

            



        

            

            



        

    



                



            Rate this post