Why is Vagrant creating a new Host-only adapter in VirtualBox?

Question

virtual box

I'm trying to start a virtual machine through Vagrant (the config is generated in PuPHPet), as a result I get the following error:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'puphpet/ubuntu1404-x64'...
==> default: Matching MAC address for NAT networking...
==> default : Checking if box 'puphpet/ubuntu1404-x64' is up to date...
==> default: Setting the name of the VM: apsfze_default_1437658608403_25152
==> 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: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)

After that, a new adapter appears in the VirtualBox settings, and so after each attempt to run vagrant up.
Prior to this, a default adapter has already been created with the required IP range.
UPD: Update to the latest version https://www.virtualbox.org/wiki/Downloads
There is no official support for Windows 10 yet, but most of the problems have already been fixed.

Answer 1

UPD: Update to the latest version https://www.virtualbox.org/wiki/Downloads
There is no official support for Windows 10 yet, but most of the problems have already been fixed.