I was sure the procedure would help, as it had helped several times before, but this time, it was different. This time it did not help: Trying a Re-installation of VirtualBox… The problem with some Microsoft updates is, that they tend to set the „hypervisorlaunchtype“ to „auto“ in the default profile. Now, the vagrant up command should not show the “VT-x is not available” error message anymore. Step 2: Reboot the machine and choose the “non-Hyper-V” option. Step 1: prepare your Windows machine for dual boot with and without Hyper-VĪs Administrator, open a CMD and issue the commands bcdedit /copy "" description "non Hyper-V" However, the code E_FAIL remains the same. It does not tell anymore, that VT-x is not avialable (an anti-improvement).
#Iconsole plus windows 10#
Note: after the latest Windows 10 Pro update, the error message has slightly changed. VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX) The command and stderr is shown below.Ĭommand: There was an error while executing `VBoxManage`, a CLI used by Vagrantįor controlling VirtualBox. => default: Running 'pre-boot' VM customizations. => default: Preparing network interfaces based on configuration.ĭefault: 8443 (guest) => 8443 (host) (adapter 1)ĭefault: 22 (guest) => 2222 (host) (adapter 1) => default: Clearing any previously set network interfaces. => default: Checking if box 'thesteve0/openshift-origin' is up to date. If you get an error message during vagrant up or when starting a VirtualBox machine, telling you that VT-x is not available, a reason may be that you have enabled Hyper-V on your Windows 10 machine: VirtualBox and Hyper-V cannot share the VT-x CPU: $ vagrant upīringing machine 'default' up with 'virtualbox' provider.
#Iconsole plus update#
This way, I hope to find it more quickly next time a Microsoft update is messing up with my configuration. Since the number of blog posts containing the word „Hyper-V“ is increasing on my blog, I now publish the information in a separate blog post.
Again! This is the second or third time I had to search for my blog post that is describing the resolution in an appendix. Shoot! The Microsoft update this morning has caused trouble with my VirtualBox installation.