Vagrant up not startedcode E_FAIL (0x80004005)

▲
1
▼

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?

vagrant
vbox
asked on Stack Overflow Dec 9, 2017 by MirelaB • edited Dec 9, 2017 by cramopy

2 Answers

▲
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"
answered on Stack Overflow Jun 21, 2018 by Alessandro.Vegna
▲
0
▼

Just go to network setting in VMware and uncheck Enable Network Adapter in the adapter 3 setting.

this

answered on Stack Overflow Jun 7, 2020 by Prathamesh • edited Jun 7, 2020 by JQSOFT

User contributions licensed under CC BY-SA 3.0