Fix it now
The Hyper-V role can be fully installed, the console can look entirely normal, and every virtual machine still fails at power-on because no hypervisor launched at boot. Two things stop it: hardware virtualisation switched off in firmware, or the boot configuration told it not to launch.
systeminfo
bcdedit /enum | findstr -i hypervisorlaunchtype
- Read the Hyper-V Requirements section at the bottom of the
systeminfooutput. Four lines matter: VM Monitor Mode Extensions, Virtualization Enabled In Firmware, Second Level Address Translation and Data Execution Prevention Available. Any No is your answer. - If instead it reads “A hypervisor has been detected. Features required for Hyper-V will not be displayed.”, the hypervisor is already running and your fault is elsewhere.
- If the second command shows
hypervisorlaunchtype Off, set it back withbcdedit /set hypervisorlaunchtype Autoand reboot. - If the firmware is the problem, enter the system firmware setup and enable the virtualisation extensions and data execution prevention, then power the machine fully off and on rather than restarting it. Some platforms only apply the change across a full power cycle.
Note the current hypervisorlaunchtype value before you change it. Turning the hypervisor off also disables virtualisation-based security features that may be in use on that server.
If a virtual machine reaches its guest firmware, stop here. If the requirements are all satisfied and the launch type is Auto and machines still will not start, the next section covers what else claims the extensions.
Why it happens
Hyper-V is a type 1 hypervisor. When it is working, Windows itself has been demoted to a privileged partition running on top of the hypervisor, and every virtual machine is a partition beside it. That transition happens once, at boot, and only if the processor exposes what Hyper-V needs and the boot configuration asks for the hypervisor to launch.
Microsoft names four requirements and systeminfo reports on all of them: VM Monitor Mode Extensions, Virtualization Enabled In Firmware, Second Level Address Translation and Data Execution Prevention Available. If every one reads Yes, the machine can run the role. Any No is a hardware or firmware condition rather than a Windows one, and no amount of reinstalling the role will change it.
If the transition does not happen, Windows boots normally and the Hyper-V management tools work normally, because they are management surfaces and nothing more. Nothing complains until you try to start a virtual machine, at which point the virtualisation stack finds no hypervisor to create a partition on. Microsoft does not publish a meaning for the code that comes back, but it does publish the sibling code in the same family, 0x80370102, as the virtual machine not starting because a required feature is not installed, and it points at exactly the two checks above.
One number here is worth being careful with. Event ID 41 is published by Microsoft, and its published meaning has nothing to do with Hyper-V: it is Microsoft-Windows-Kernel-Power in the System log, recording that the system rebooted without cleanly shutting down first. It is a useful thing to notice on a host that keeps failing, because an unexpected shutdown explains a lot of odd states, but it is not evidence about the hypervisor. Read the log name and source before you act on any 41 you find.
Hardware virtualisation is disabled in firmware
You have this one if systeminfo reports Virtualization Enabled In Firmware as No.
- Reboot into the system firmware setup and enable the virtualisation extensions. Vendors label them Intel VT-x, Intel Virtualization Technology, AMD-V or SVM Mode.
- Enable data execution prevention as well, listed as XD bit, NX bit or Execute Disable depending on the vendor.
- Save, then power the machine down completely rather than restarting it.
- Run
systeminfoagain and confirm the requirement now reports Yes.
On a leased or hosted server you may not have firmware access. Ask the provider to enable the extensions rather than trying to work around it.
The hypervisor launch type is off
You have this one if Every requirement is satisfied and bcdedit shows hypervisorlaunchtype Off.
- Run
bcdedit /set hypervisorlaunchtype Autofrom an elevated prompt. - Reboot the host.
- Confirm with
bcdedit /enum | findstr -i hypervisorlaunchtypethat the value is now Auto, and that machines start.
Troubleshooting guides for unrelated problems, and some third-party debugging tools, set this to Off and never set it back. It is a common finding on a host that used to work.
The host is itself a virtual machine without nested virtualisation
You have this one if The host is a guest on another hypervisor and reports no virtualisation extensions at all.
- On a Hyper-V parent, shut the virtual machine down and run
Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true. The machine has to be off for this. - Check the published prerequisites: an Intel processor with VT-x and EPT needs a Windows Server 2016 or later parent and configuration version 8.0 or higher; AMD EPYC or Ryzen needs a Windows Server 2022 or later parent and configuration version 9.3 or higher.
- Start the machine and install Hyper-V inside it as you would on a physical server.
Something else already holds the virtualisation extensions
You have this one if Another hypervisor or a security product is installed on the same machine.
- Uninstall or disable competing hypervisors. Older desktop virtualisation products claim the extensions exclusively and will not share.
- Check whether a security feature that depends on the hypervisor has been enabled or disabled recently, because those changes move the launch type as a side effect.
- Restart and re-test, reading
systeminforather than the console.
The role is present but did not load on this boot
You have this one if Requirements and boot settings look right, and nothing about this boot shows a successful launch.
- Confirm the role is genuinely installed with
Get-WindowsFeature Hyper-V. - Confirm the machine did not boot into safe mode, where the hypervisor does not run at all.
- Reinstall the role with
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restartif the feature state is inconsistent. - Read the Hyper-V-Hypervisor log entries from the last boot and work from their text rather than their numbers.
Full reference
The four requirements, and what each one is
| systeminfo line | What it is | Where it is set |
|---|---|---|
| VM Monitor Mode Extensions | The processor’s virtualisation instructions | Fixed in the processor |
| Virtualization Enabled In Firmware | Those instructions switched on | System firmware setup: VT-x, Virtualization Technology, AMD-V or SVM |
| Second Level Address Translation | Hardware page-table translation, required rather than optional | Fixed in the processor |
| Data Execution Prevention Available | Hardware-enforced DEP available and enabled | System firmware setup: XD bit, NX bit or Execute Disable |
Two of these you can change and two you cannot. If the processor lacks the extensions or second level address translation, the machine cannot run Hyper-V and no configuration change alters that. If they are present and switched off, it is a firmware visit and a full power cycle.
Reading the boot configuration
bcdedit /enum | findstr -i hypervisorlaunchtype
bcdedit /set hypervisorlaunchtype Auto
bcdedit changes the boot configuration of the host. Note the current value before you change it, change one setting at a time, and be ready to boot from installation media if the machine will not start. Turning the hypervisor off is also how virtualisation-based security features get disabled, so on a server that uses them, treat the launch type as a security setting rather than a virtualisation one.
Nested virtualisation, properly
| Parent processor | Parent operating system | Minimum VM configuration version |
|---|---|---|
| Intel with VT-x and EPT | Windows Server 2016 or later, or Windows 10 or later | 8.0 |
| AMD EPYC or Ryzen or later | Windows Server 2022 or later, or Windows 11 or later | 9.3 |
Set-VMProcessor -VMName LabHost -ExposeVirtualizationExtensions $true
The virtual machine has to be off. Running the command against a running machine does not take effect, and the guest continues to see no extensions, which produces exactly the failure this article is about and looks like the command did nothing.
When the hypervisor is running and machines still will not start
- Read
systeminfofirst. If it says a hypervisor has been detected, you are in the wrong article and should be looking at storage, configuration or integration failures instead. - Check whether the specific machine has a saved state or a checkpoint chain it cannot resolve, which fails at power-on and looks similar from the console.
- Check whether the virtual disks are reachable and whether the per-machine identity still has rights on them.
- Check free memory on the host. A machine configured with static memory the host cannot supply refuses to start rather than starting slowly.
- Read the text of the entries in the Hyper-V logs rather than the numbers. Microsoft does not publish meanings for most of them, and the text names the machine and the operation.
The licensing question, since it always comes up
None of this needs a purchase. The Hyper-V role is included in both Standard and Datacenter editions, and edition affects how many virtual machines you are entitled to run rather than whether the hypervisor starts. Windows Server 2025 Standard permits two virtual operating system environments per licensed host and Datacenter permits an unlimited number, but a host with the extensions disabled in firmware runs none of them regardless of which licence it carries.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC0370102 |
Not published by Microsoft. It accompanies a virtual machine start refused because no hypervisor is running on the host. Microsoft does publish the sibling code 0x80370102 as the machine not starting because a required feature is not installed, with firmware virtualisation and hypervisorlaunchtype as the documented checks | not published by the vendor |
Event ID 41 |
Microsoft publishes this as Microsoft-Windows-Kernel-Power in the System log: the system rebooted without cleanly shutting down first. It is not a record of a hypervisor launch, so read the log name and source before acting on it | Microsoft Learn |
Event ID 12140 |
Not published by Microsoft. It appears against a machine that could not be started; the entry names the machine | not published by the vendor |
Event ID 15350 |
Not published by Microsoft. It appears from the worker side of the same failure | not published by the vendor |
Confirm the fix worked
systeminforeports that a hypervisor has been detected.bcdedit /enum | findstr -i hypervisorlaunchtypeshows Auto.- A virtual machine powers on and reaches its guest firmware.
- If the host is nested, the guest itself reports the four Hyper-V requirements as satisfied.
- After a full power cycle rather than a warm restart, the same is still true.
Questions people ask about this
Do I need a different Windows Server licence to run Hyper-V?
No, and this costs nothing to fix. The Hyper-V role is included in both Standard and Datacenter. Edition affects how many virtual machines you may run, not whether the hypervisor starts.
Why did this start after a Windows update?
Updates do not normally change firmware settings, but a firmware update installed alongside them can reset the virtualisation options to defaults. Check the firmware first on any host that failed after maintenance.
Can I run Hyper-V inside another virtual machine?
Only with nested virtualisation enabled on the parent, with the virtual machine shut down when you enable it, and only where the processor, parent operating system and configuration version meet the published prerequisites.
I found Event ID 41. Is that my hypervisor failing?
Not on its own. Microsoft publishes Event ID 41 as Kernel-Power in the System log, recording that the machine rebooted without shutting down cleanly. It is worth investigating on its own terms and it is not evidence about the hypervisor.
Does turning the hypervisor off help performance?
On a virtualisation host it stops the machine doing its job. It also disables the security features that depend on the hypervisor, which is usually the more expensive half of that trade.
