Quantcast
Channel: Java mon amour
Viewing all articles
Browse latest Browse all 1124

VirtualBox and Hyper-V on Windows 10 PRO

$
0
0
I have recently installed Windows PRO. During installation of Hyper-V, it duly warns you that you will no longer be able to use VirtualBox. Which is true, because when I start a VM in VirtualBOx I get the message:


WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX).


Apparently all you need to do to re-enable VirtualBox is:


open CMD as Administrator
bcdedit /set hypervisorlaunchtype off

reboot your machine

To restore Hyper-V you simply run:
bcdedit /set hypervisorlaunchtype on


I haven't tested yet but it should work IMHO



bcdedit is this https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdedit-command-line-options

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale fr-FR
inherit {globalsettings}
badmemoryaccess Yes
default {current}
resumeobject {b32f6aed-59a4-11e8-b3f7-b9390bbf0244}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale fr-FR
inherit {bootloadersettings}
recoverysequence {b32f6aef-59a4-11e8-b3f7-b9390bbf0244}
displaymessageoverride Recovery
recoveryenabled Yes
badmemoryaccess Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {b32f6aed-59a4-11e8-b3f7-b9390bbf0244}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto



Viewing all articles
Browse latest Browse all 1124

Trending Articles