Vagrant up not startedcode E_FAIL (0x80004005)

Question

I'm using W10 and I had a problem with Vagrant-suddenly I cannot do vagrant up. I received error:

There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "e11dfd77-f4e8-4125-8169-d81f7dc44e55", "--type", "headless"]

Stderr: VBoxManage.exe: error: Interface ('VirtualBox Host-Only Ethernet Adapter #3') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole"

used to work fine until yesterday. I had a Windows update as well yesterday, but after that update vagrant works well.

What i tried:

• checked Hyper-V platform - is disabled.
• reinstalled VM Box, Vagrant but nothing helped.

Any ideas?

Answer 1

For anyone getting this more recently where the stderr does not mention VT-x, but instead is something like this:

Stderr: VBoxManage.exe: error: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)

I finally found that it was a virtualbox update that broke it for me; trying to fix NEM in Windows 11 I guess, but breaking it in Windows 10? See discussion here on virtualbox's forum.

Basically if you have W10 and upgraded VirtualBox to 6.1.28, you'll want to downgrade to 6.1.26.

Answer 2

I know it's an old post but this link worked for me.

Open CMD as administrator and run:

bcdedit /copy "{current}" /d "Hyper-V" 
bcdedit /set "{current}" hypervisorlaunchtype off
bcdedit /set "{current}" description "non Hyper-V"