4

Hyper-V installs without apparent problem, but then any attempt at launching a virtual machine throws this error :

'<virtual machine name>' failed to start.

Virtual machine '<virtual machine name>' could not be started because the hypervisor is not running.

System info:

  • Windows 10 Enterprise 1803 17134.523
  • ASUS PRIME B350-PLUS
  • AMD Ryzen 5 1600X

Here is the output of the various software I've checked :

  • ASUS UEFI BIOS Utility > Advanced Mode > Advanced > CPU Configuration

    NX Mode                     Enabled
SVM Mode                    Enabled
SMT Mode                    Auto
Core Leveling Mode          Automatic mode

  • Task Manager > Performance

    Virtualization: Enabled

  • msinfo32.exe > System Summary

    Hyper-V - VM Monitor Mode Extensions                   Yes
Hyper-V - Second Level Address Translation Extensions  Yes
Hyper-V - Virtualization Enabled in Firmware           Yes
Hyper-V - Data Execution Protection                    Yes

  • coreinfo.exe -v

    AMD Ryzen 5 1600X Six-Core Processor
AMD64 Family 23 Model 1 Stepping 1, AuthenticAMD
Microcode signature: 00000000
HYPERVISOR      -       Hypervisor is present
SVM             *       Supports AMD hardware-assisted virtualization
NP              *       Supports AMD nested page tables (SLAT)

  • bcdedit.exe > Windows Boot Loader

    nx                      OptIn
hypervisorlaunchtype    Auto

  • PowerShell > Get-Service -DisplayName Hyper-V*

    Status   Name               DisplayName
------   ----               -----------
Running  vmcompute          Hyper-V Host Compute Service
Stopped  vmicguestinterface Hyper-V Guest Service Interface
Stopped  vmicheartbeat      Hyper-V Heartbeat Service
Stopped  vmickvpexchange    Hyper-V Data Exchange Service
Stopped  vmicrdv            Hyper-V Remote Desktop Virtualizati...
Stopped  vmicshutdown       Hyper-V Guest Shutdown Service
Stopped  vmictimesync       Hyper-V Time Synchronization Service
Stopped  vmicvmsession      Hyper-V PowerShell Direct Service
Stopped  vmicvss            Hyper-V Volume Shadow Copy Requestor
Running  vmms               Hyper-V Virtual Machine Management

I have found multiple similar threads on this website and others, and have already tried (all of them to no avail) :

  • Uninstalling and reinstalling Hyper-V (multiple times)
  • Rebooting the machine (cold boot, multiple times)
  • Upgrading my BIOS
  • Upgrading the motherboard chipset driver

Any idea about the next course of action?

Mathieu Renda
  • 51

2 Answers2

0

Your hardware can run Hyper-V according to the specs, so the problem is probably with some settings.

Check in the BIOS under Advanced Frequency Settings > Advanced CPU Core Settings, if the option named "SVM mode" is set to Enabled. If it is not, enable it, save the BIOS, turn-off the computer and do a cold boot.

If this does not help, open an elevated Command Prompt and run this command:

bcdedit /set hypervisorlaunchtype auto

then reboot the computer, again with a cold boot.

If this does not work either, check if your setup is really capable of running Hyper-V with the AMD-V with RVI Hyper V Compatibility Utility, running it in elevated mode.

harrymc
  • 480,290
  • These two options are already activated, and I've performed multiple cold boots since. The tool says "This system is compatible with Hyper-V". Despite all this, no VM is starting. – Mathieu Renda Jun 02 '19 at 14:20
  • Is this the same for both 32-bit and 64-bit VMs? – harrymc Jun 02 '19 at 15:53
  • 1
    I don't think you can create a 32-bit VM per se in Hyper-V. You can install a 32-bit operating system on a VM. Here, I cannot do that because the VM doesn't even start. – Mathieu Renda Jun 04 '19 at 03:59
  • Try this: Run gpedit.msc and go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security, and set to Disabled. Reboot. – harrymc Jun 04 '19 at 06:17
  • You can't even add Hyper-V feature without enabling SVM mode first, so this is irrelevant. – Alex G Dec 28 '19 at 23:23
  • @AlexG: I don't understand your remark and downvote. – harrymc Dec 29 '19 at 08:10
-1

OSes can only run one hyper-Visor at one time. Is it possible you have another one running such as VMware, virtual box. Or maybe a program that utilizes that such as NOX? Since you mention your on enterprise is there any GPOs blocking use of Hyper-V.

To test I would install a Spare SSD and install windows 10 Pro and see if the issue persists.

Davef
  • 60