Windows 10 - Failed to create the host-only adapter

[josin]

When I'm trying to run my VM using vagrant I'm getting following error:

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_INVALIDARG
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.0\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0036).
VBoxManage.exe: error: Please contact the product vendor!
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

System information:

• VirtualBox 5.0.21r107152
• Vagrant 1.8.1
• Windows 10 Enterprise Insider Preview, Build 14342.rs1_release.160506-1708

[Curt]

Still true in VirtualBox-5.0.21-107170-Win as well.

[APIs Can't be Copyrighted]

Hello,

This is due to something that changed in the most recent Windows 10 Insider Fast Ring build. I think I got on the Windows 10 insider train with the April 6th build because of my interest in Project Centennial. You guys fixed something related to that issue in April and that worked for a while.

In fact, a new build or two came out and things still worked. I had to re-install VirtualBox to get the networking driver adapters to install, but after that, it still worked.

Now, this most recent insider build (14342) either re-breaks that or there's another underlying issue they're creating for you. If I were to guess, I think either removing host-only networks doesn't work or getting the status of existing host-only networks doesn't work. Every time I try to run 'vagrant up' on a box that has a host-only adapter, a new VirtualBox Host-Only Ethernet Adapter gets created. I get a dialog box saying "Can't rename this connection" or something like that and the output from Vagrant is like the initial poster just posted.

...also something totally strange just happened. In trying to get the dialog box to come up to give the exact "can't rename" error message, running 'vagrant up'...worked! I have 7 host-only adapters, but it worked.

I'm following the ticket. If you have any questions, let me know and I'll answer them.

[Curt]

I managed to get it to work in 14342 as well using build 107302. Yesterday, Win 10 upgraded to build 14352 and once again, a working vagrant/virtualbox VM dies in starting the network adapter. I have gone through an install cycle and been unsuccessful. I very carefully removed all Virtual Box entries from the registry (there are some left after uninstall) including several network adapter entries but once again encountered the host adapter rename error during install

Error now reports:
Progress state: E_INVALIDARG
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.0\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0036).
VBoxManage.exe: error: Please contact the product vendor!
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

[bnebosen]

Still reproducible on 5.0.51-107546-Win

[bnebosen]

Still reproducible on version 5.0.21 r107750. Is this bug expected to be fixed sometime soon?

[cwadrupldijjit]

I also have encountered this issue. It seems like either it's timing out or it's going to create a host-only adapter and then it tries again, saying that it can't rename the connection. I've noticed that when I keep trying to run "vagrant up" and when it runs the command to create the host-only adapter, it fails many times, then it finally succeeds.

Here is a pictrue of my network connections pane:

I, myself, am using Windows 10 Insider build 14366, and my VirtualBox version is 5.0.20. Any version of the software, as well as any build of Windows seems to result in the same thing.

As you can probably tell from looking at the number next to the "Ethernet" on the adapters how many times I've had to do this.

Whenever I get a system update or a delete the extra adapters, it seems to take one extra attempt in order to get it to make a host-only adapter that works. Since I'm on the fast ring for Windows insiders builds, this happens often. It may well be the only issue I'm experiencing with getting Vagrant to run on my computer for work.

I was reading another ticket where the issue was their antivirus. In my case, I'm using Windows Defender, and it's not blocking the creation of the adapter, otherwise it wouldn't work at all.

[bnebosen]

Still happening with 5.0.24r108355

[StijnDeWitt]

Still happening on v5.1.2:

C:\VirtualBox\v5.1.2>systeminfo | Findstr /i "OS"
Host Name:                 ----REDACTED----
OS Name:                   Microsoft Windows 10 Home
OS Version:                10.0.10586 N/A Build 10586
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Microsoft
Registered Organization:   Microsoft
BIOS Version:              American Megatrends Inc. 1207   , 7-12-2009
                           [02]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network

C:\VirtualBox\v5.1.2>VBoxManage --version
5.1.2r108956

C:\VirtualBox\v5.1.2>VBoxManage hostonlyif create
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
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

Observations:

• Once it prints 0%, Windows asks for admin priviliges, which I give.
• Some GUI window flashes by, can't see what's in it
• Gui window flashes by another time, and then a third
• Process terminates with logs shown above.

[StijnDeWitt]

Just to test, I set processes:

• VirtualBox.exe
• VBoxHeadless.exe
• VBoxManage.exe

to always run as administrator using compatibility mode settings (for all users), then opened a command prompt as administrator, but nearly the same thing happens. I don't get the Windows dialog asking for admin permissions, but I still get the three gui windows flashing by and the resulting output is exactly the same.