"Failed to create host network interface" on Windows 10

[BlueRaja]

I'm trying to get Xamarin Android Emulator working on Windows 10. It's failing because VirtualBox does not have a host network adapter set up. It worked fine on Windows 8.

When I attempt to create a host network adapter in Virtual Box, I get this error:

"Failed to create the host network interface Result Code: E_FAIL (0x80004005)"

I've tried doing a uninstalling/reinstalling, and doing a repair install. I don't know if this is related to #14040, but I'm using the latest beta, which supposedly fixed that issue..

Version: 5.0.3-102322-Win

[BlueRaja]

I should mention the installer acts like the host-only networking interface is installed correctly, but it's definitely not.

Are there any logs I can provide to help debug?

Update: I also tried version 5.0.3-102467-Win, with the same results.
Update2: Also tried 5.0.2-102096-Win for good measure, same results.

[Frank Mehnert]

Please check if VBox 5.0.4 fixes your problem.

[KevinS80]

Still an issue with 5.0.4

[Aleksey Ilyushin]

Do I understand it correctly that after VBox installation there is no host-only adapter on your system? Please provide the output of

ipconfig /all

and

driverquery /fo list /v

and

VBoxManage hostonlyif create

with VBox 5.0.4. It would be great if you provided VM log (preferably one bridged to physical Ethernet adapter) and VBoxSVC.log too.

[Aleksey Ilyushin]

KevinS80,

there is no need to provide all the info I asked for in comment 4. I wrote it before I saw your latest edit of comment 3. It already provides enough information to identify the error. Thanks a lot!

[Sae1962]

Hello!

I want to run the VMBox under Windows 10, but have problems having the four "Adapter 0"s in the Network setting after the message

Could not start the machine FW732_1a (OPC Serv. Simulator) because the following physical network interfaces were not found:

VirtualBox Host-Only Ethernet Adapter (adapter 2)

You can either change the machine's network settings or stop the machine.

Deactivating the adaptors does not solve the problem.

When I select an "Heedless" or a "Detachable" start, the progress bar goes to 100%, ending with the same error message (E_FAIL (0x80004005)) at the end.

Do you have a (beta) version for Windows 10? I attached the results of the commands ipconfig /all and driverquery /fo list /v into the VMBox.txt file.

There is good news for Windows 10 users, however, as VMBox 4.3.30 runs without problems!

[Sae1962]

Result of commands

[Aleksey Ilyushin]

Sae1962, could you provide the failing VM log and VBoxSVC.log, please?

[BlueRaja]

I ended up uninstalling Windows 10 because I cannot wait for this to be fixed. But please leave this issue open, since others are able to repro it.

[klapperkopp]

I have the same prob also on Win 10. I was updating from 4.x to 5.0.4 and had the adapter first. Laravel homestead wanted to create new ones and didn't work so I uninstalled. Now I can't install anymore because I get the same error on install. The weird thing is it worked before... the adapter was there... :(

[fangtr]

When I was updating from 5.0.4 to 5.0.6,it problems also arise. My OS is windows 10 pro 64bit 10240.

[travassos]

Hi,

this problem still occurs on version 5.0.10.

[keklabs]

I have the same issue on Windows 7, VirtualBox 5.0.10, when I try to create Docker virtual machine.

It is related to

​https://github.com/docker/machine/issues/1754

Failed to open a session for the virtual machine test-docker11.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

But the report from IPCONFIG is:

Ethernet adapter VirtualBox Host-Only Network #3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #3
   Physical Address. . . . . . . . . : 0A-00-27-00-00-00
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::1023:4a8d:66ed:896%35(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.36.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 587857959
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-21-BB-9B-F0-DE-F1-97-4D-2C
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Same issue occures, when I remove all HostOnly adapters and create nad configure new one for VM. I disable the AVG antivirus, and still the same issue.

[keklabs]

I resolved my issue

the ​https://forums.virtualbox.org/viewtopic.php?f=6&t=68590&start=450#p345381

"After re-installing VB I switched on "VirtualBox NDIS6 Bridged Networking Driver" in properties network connection."

Now it is working.

[Aleksey Ilyushin]

Please try build 104592. It is important to uninstall VirtualBox before installing the test build as it will ensure that all unbound host-only adapters are removed.

[Frank Mehnert]

Or test the latest 5.0.x Windows test build.

[Frank Mehnert]

Fix is part of VBox 5.0.12.

[Vito]

Sorry to say the issue is not fixed with VBox 5.0.12.
I did not have this issue with 5.0.10, until I upgraded to 5.0.12.
Then I had the issue.
I tried uninstalling and reinstalling, but no success until I fixed it following the ​https://forums.virtualbox.org/viewtopic.php?f=6&t=68590&start=450#p345381
(I added VirtualBox NDIS6 Bridged Networking Driver element to the VirtualBox Host-Only Ethernet Adapter). Windows 10 Professional 64 bit here.

[proxenus]

In case it can help to fix the issue, this is the workarround I apply when I encounter this issue.

On my side is always related to an upgrade from 4.x to 5.x. The machines started or created in the "upgraded" systems fail to start.

the issue is related to the stored "default" virtual box adapter in the host.

the workarround to solve the issue is.

1- File > Preferences > net

2- Select Host only network.

3- Create a new Host only network (it shall appear with a new name and a prefix at the end like #2)

4- Open the virtual machine configuration

5- VM > configuration > net

6- Select the interface and change the name to the new created one in step 3.

it fix the issue 100% of the times this issue happens.

hope this helps to find the root cause.

[Ajedi32]

FYI, I encountered this same error while trying to create a VirtualBox VM through Vagrant:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/ubuntu-14.04' is up to date...
==> 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: 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

I was able to work around this problem for me with the following steps:

1. Open the VirtualBox Manager GUI.
2. Go to File -> Preferences -> Network -> Host-only Networks
3. Delete all entries in that list
4. Run vagrant up again

[maltem]

See ​this StackOverflow answer for a potential solution.

[mjohenneken]

I had the same issue while trying to create a Kubernetes Minikube.

VirtualBox was not able to create a host-only network. I'm using a upgraded Windows 10. The upgrade messes Up the network setup functionality of Windows. Microsoft released a fix for their hyperv product, but this also fixes the issue VirtualBox has. See this support site ​https://support.microsoft.com/en-us/help/3101106/you-cannot-create-a-hyper-v-virtual-switch-on-64-bit-versions-of-windo