VirtualBox Network Adapter fails to install

The Host-Only Adapter fails to install in Windows 8.1 x64 with VirtualBox-4.3.20-96997.

When VirtualBox is installed, Host-Only appears in the Device Manager as a failed device.

enter image description here

Therefore Host-Only is not visible in the Network Connections window.
Reinstalling the device through VirtualBox returns:

Failed to create the host network interface.

E_FAIL (0x80004005).

enter image description here

Reinstalling VirtualBox duplicates the device as failed in the device manager:

enter image description here

Deleting the driver or a clean installation won't change the mentioned results.

Gabriel

Posted 2014-12-23T18:35:22.330

Reputation: 2 271

Which version of VritualBox are you trying to install? – Ƭᴇcʜιᴇ007 – 2014-12-23T18:42:39.063

Did you look at any of the answers here? https://www.virtualbox.org/ticket/6930

– JakeGould – 2014-12-23T18:58:17.143

Have you tried this way?. 1. Remove manually the Virtual Host-Only adapter, rebooted and installed it again? Sometimes, reboot will clear all cache files before you try re-installing it again. – vembutech – 2014-12-23T19:02:00.120

Yes I have removed Virtualbox along with the adapter, including all traces in the registry, rebooted, reinstalled and the problem persists. – Gabriel – 2014-12-23T19:07:59.363

Try installing an older version of VirtualBox. Such as 4.3.12 and see if you still have the problem. – imtheman – 2014-12-23T19:35:33.280

The problem persists with 4.3.12. – Gabriel – 2014-12-23T20:20:49.557

Here is one workaround. Try also in Device Manager to update the driver using "Browse my computer" and pointing to the VirtualBox installation folder.

– harrymc – 2014-12-26T12:17:03.183

@harrymc. It returns: The best driver software for your device is already installed. – Gabriel – 2014-12-26T18:27:42.690

Have you tried to right click the installer and select "Run as Administrator" ? Also, have you tried disabling antivirus or other software that may be preventing the adapter from installing? – Jorge Luque – 2014-12-31T21:57:21.237

Yes, I have tried with both suggestions. – Gabriel – 2015-01-01T22:03:58.917

Answers

This seems like a known bug : Ticket #12182 : Failed to create the host network interface.

The only claimed workaround is given by David.Requena :

In fact going back to 4.2.24 and creating some h/o adapter allows its use after upgrading to any 4.3.x release. Said adapter can be removed in 4.3.x but not modified. Under no circumstance can it be re-created.

Try going back to version 4.2.24 to create the adapter, or wait for the bug to be fixed by the developers.

Be careful to fully uninstall the current VB version and ensure that all its devices are deleted before installing version 4.2.24.

harrymc

Posted 2014-12-23T18:35:22.330

Reputation: 306 093

Unfortunately the issue persists with version 4.2.24. Either by installing from scratch or manually adding the network in VirtualBox settings: Failed to create the host-only network interface. And Device Manager shows the device as failed: This device is not working properly because Windows cannot load the drivers required for this device. (Code 31) – Gabriel – 2014-12-28T17:56:56.400

If this is an inherent defect in all versions of VB on Windows 8.1, then you are obliged to wait for a VB version that works on Windows 8.1. Your options as I see them are: (1) Try to execute the VB setup in compatibility mode of Windows 7 or earlier, (2) Try an even earlier version of VB, (3) Raise the question in the VB forums and wait for a fix, (4) Use Hyper-V instead of VB until the bug is fixed then convert the VM to VB. – harrymc – 2014-12-28T18:45:09.503

Thank you, I just tried with every existing 4.0 version with no avail, also 3.0 versions get interrupted and rollback during the installation wizard in 8.1. – Gabriel – 2014-12-28T23:15:43.437

There is also (5) Use another adapter than Host-Only; and I think that this exhausts the list of all possible actions on your side. – harrymc – 2014-12-29T08:43:55.710

Can you elaborate on that (5)? – Gabriel – 2014-12-29T19:11:33.693

It's just a trivial afterthought - use the NAT or bridged network adapters to make the VM accessible through your local network. – harrymc – 2014-12-29T19:20:35.933

The issue is known to persist no matter what. Make sure you perform the following steps: - uninstall VirtualBox; - remove Host-Only network interfaces from Device Manager in Control Panel;

After that, you will have to run regedit.exe, and search and remove all entries with keys containing VBox, VirtualBox and Oracle (excluding the ones related to Oracle DB). After doing that I was able to install VB with all default options.

phil pirozhkov

Posted 2014-12-23T18:35:22.330

Reputation: 185

My solution was to download and install version 5.0.6 of VirtualBox and it's Extension Pack. Tried various versions and methods before that without any luck. Now I'm virtual again ;)

superodde

Posted 2014-12-23T18:35:22.330

Reputation: 1