Error in Windows Server: Virtual machine could not start because the hypervisor is not running
This article helps fix an issue that you're unable to start virtual machines because of incorrect DEP setting in BIOS.
Applies to: Windows Server 2012 R2
Original KB number: 2490458
Symptoms
Consider the following scenario:
You install the Hyper-V role on a computer that is running Windows Server.
You create a virtual machine and attempt to start the virtual machine.
You may see the following event ID:
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Event ID: 3112
Level: Error
Description:
The virtual machine could not be started because the hypervisor is not running.
In this scenario, you're unable to start the virtual machine and receive the error message below:
Virtual machine could not start because the hypervisor is not running.
Cause
The Data Execution Prevention (DEP) setting isn't enabled in BIOS. For HP server, it's called "No Execute Memory Protection."
Resolution
To fix the issue, enable the DEP setting in BIOS.
More information
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for