Failed to create the host-only adapter - windows 10, docker, virtualbox

Question

I\'ve recently run into this problem after having used docker toolbox without a problem for a while.

Started happening after windows update?

Windows 10 Home - 64

Answer 1

I uninstalled wireshark, docker tooltip and VirtualBox.I also deactivate the antivirus temporary. Then, i installed docker tooltip without selecting install NDIS5 and it worked for me.

Answer 2

I got to the same error.

But I don't have "VirtualBox NDIS6 Bridged Networking Driver" in properties of physical connection. A have same driver "NPCAP ..." from wireshark installation. If look at description you can see this is NDIS6 driver.

Then I remove all wireshark packages: NPCAP, WinPCAP, Wireshark and remove VirtualBox.

Restart.

Reinstall Virtual Box. Install Docker ToolBox(Uncheck install NDIS5). And Create default VM for docker.

docker-machine create -d "virtualbox" default

Host-only interface created normally

docker-machine status
Running

That works for me.

Answer 3

I first installed Docker Toolbox yesterday since I have Windows 10 Home which does not support Docker Desktop.

Rebooting or installing Java did not solved it for me. What did was to delete Oracle's VM that was installed with the Toolbox (5.2.12 or something), and reinstall the new 6.1.8. Checking their website, this makes sense:

Answer 4

tl;dr If you are using Trend Micro or Symantec antivirus solutions, try uninstalling Virtualbox, then re-install it with the antivirus disabled. It may work with others as well.

I am adding this answer for the record.

My coworkers and I started having a similar issue just after updating from Windows 10 Pro version 1703 to version 1709.

I tried rolling back to version 1703, and it worked, but of course this is not an acceptable solution.

For some reason, this had to do with the antivirus, which in our case is Trend Micro Office Scan. After doing a clean re-install with the antivirus disabled, the host-only adapter was available again.

The issue has been reported in the Virtualbox forum and issue tracker:
https://forums.virtualbox.org/viewtopic.php?f=6&t=86179#p413876
https://www.virtualbox.org/ticket/17354#comment:22

Unfortunately, this error is quite frequent, and it has been reported dozens of times with different causes. In our case, the settings shown in bszom's answer were already correct.

Answer 5

Unfortunately I also had the Issue (Win10, 1709,virtualbox 5.1). While Using vagrant to pull linux images from the web.

This fixed it

Get your network drivers to the latest stand

Uninstall Virtualbox

Reinstall Virtualbox

Check if you have the "host only" virtual adapter in your network adapters config. If yes than you're good to go. If not. Try to install it from vboxmanage.

C:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create

And uninstall HyperV Virtual ethernet Adapter from the device manager if you see it (this blocks usually creation of virtualbox virtual network (Host-Only Ethernet adapter))

I had this issue on one type of computer of my company but not on others types. So this must be related to the type of network adapter itself. so sometimes you are lucky sometimes not. But I was more lucky having hardware to the latest stand.

Answer 6

I got the same error:

(default) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface

but in my case I was trying to install Docker Toolbox on Windows 8.1 64-bit.

Windows-8.1-6.3.9600-SP0 : AMD64

Previously, I had virtualbox version 6.0 installed on my system, so I unchecked the docker toolbox installer option, install virtualbox.

For my scenario it worked to uninstall virtualbox 6.0 reboot the system and install VirtualBox-6.1.12-139181

Note: As uninstaller use this tool.

And ready docker in windows 8.1 running.