Lost connection to Hyper-V VMs

I had multiple VMs defined and working. Did something but I have no idea what and now when I open Hyper-V Manager I get this:



Where is the link to my VMs defined? I thought I knew this stuff but apparently I don't.

Here are my VMs:



Edit; When I tried to make sure Hyper-V was active (On) I get this error:

Code:

D:\tools>bcdedit /set {current} hypervisorlaunchtype auto
The boot configuration data store could not be opened.
Access is denied.

Self inflicted wound. I turned off Hyper-V while trying different things and apparently forgot to turn it back on again.

Turned it back on and all is well: bcdedit /set {current} hypervisorlaunchtype auto from a elevated command prompt.

Ztruker said:

Self inflicted wound. I turned off Hyper-V while trying different things and apparently forgot to turn it back on again.

Doh!

FYI, if you need to test things you can also safely uninstall Hyper-V in 'Turn Windows features on or off'. When you reinstall it all your VMs and settings will still be there and working. The only thing you'll have to set up again are any virtual switches you may have set up, the Default switch is the only one that gets recreated. I find this is a good way to reset Hyper-V if I've played around a bit too much and messed it up.

Good tip, thanks Bree.

Kari explains how to create a boot menu to give the choice of booting with or without Hyper-V in Method Two of this tutorial.

Run Hyper-V, VirtualBox and VMware on same Computer

Bree said:

Kari explains how to create a boot menu to give the choice of booting with or without Hyper-V in Method Two of this tutorial.

Run Hyper-V, VirtualBox and VMware on same Computer

Actually vmware and virtualbox can coexist with Hyper-V now but it is painfully slow compared with a dual bcd entry as per tutorial.

jimbo, Bree, great idea. I'll give it a whirl and see how it goes. Sounds simple enough.

Thank you both.

Edit: Worked great.

Code:

C:\Users\ztruk>bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
resumeobject            {8d90a8c3-d39b-11ea-982c-97b4c3117002}
displayorder            {default}
                        {8d90a8c9-d39b-11ea-982c-97b4c3117002}
                        {current}
toolsdisplayorder       {memdiag}
timeout                 3

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8d90a8c6-d39b-11ea-982c-97b4c3117002}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8d90a8c3-d39b-11ea-982c-97b4c3117002}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

Windows Boot Loader
-------------------
identifier              {8d90a8c9-d39b-11ea-982c-97b4c3117002}
device                  ramdisk=[X:]\sources\boot.wim,{8d90a8c8-d39b-11ea-982c-97b4c3117002}
path                    \Windows\system32\boot\winload.efi
description             KYHI Rescue
osdevice                ramdisk=[X:]\sources\boot.wim,{8d90a8c8-d39b-11ea-982c-97b4c3117002}
systemroot              \windows
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10 No Hypervisor
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {8d90a8c6-d39b-11ea-982c-97b4c3117002}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {8d90a8c3-d39b-11ea-982c-97b4c3117002}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Off

C:\Users\ztruk>