Windows10 x64 'vagrant up' error

[motatoes]

Hi,

On Windows 10 x64 when I follow the instructions after issuing a vagrant up I get the following output with an error "VBoxManage.exe: error: Failed to create the host-only adapter".

I'm not sure if its related to this project or VirtualBox, I found a bug ticket issued on virtualbox and I downloaded an attached fix but it didn't work. Any hints?

Full vagrant up output

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'bento/ubuntu-14.04'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'bento/ubuntu-14.04' is up to date...
==> default: Setting the name of the VM: sweetshop_default_1455744240769_82460
==> default: Auto-generating node name for Chef...
==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Could not find Host Interface Networking driver! Please reinstall
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 71 of file VBoxManageHostonly.cpp

[r8]

Thanks for the report. I'll try to reproduce it.
Could you please also share your vagrant/virtualbox versions? Is it just latest?

[motatoes]

Yes
vagrant v1.8.1
Virtual box 5.0.14

[Sotiris-k]

@motatoes do you by any chance have Kaspersky installed? From your initial link to relevant bug it seems to be a problem with KIS.

For what it's worth I run win10 x64 with vagrant 1.8.1 and VB 5.0.16 with no problems.

[motatoes]

@Sotiris-k Nope I don't have kaspersky installed, how is it related to Kaspersky?

[Sotiris-k]

@motatoes It was an issue on the bug ticket you first linked. Also since Kaspersky is generally very intrusive with such things, it could very well be a possible cause.

I guess you've already tried upgrading Virtualbox by now, right?