Interface (‘VirtualBox Host-Only Ethernet Adapter’) is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).

My laptop was upgraded from Windows 8 to Windows 10 . After that when I tried to start up VirtualBox 5.0 software, there was no response at all. The software is neither up nor with any error messages.

Then I uninstalled VirtualBox 5.0 and installed latest VirtualBox 5.1.6. It was better this time. But when I tried to start up one Linux virtual server, got this message:


Interface ('VirtualBox Host-Only Ethernet Adapter') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).

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


Checked a couple of items, all look fine:

a) Run “VBoxManage list hostonlyifs”

c:\Program Files\Oracle\VirtualBox>VBoxManage list hostonlyifs
Name: VirtualBox Host-Only Ethernet Adapter #2
GUID: be24ca57-3d51-4b39-bb51-5675a36f571b
DHCP: Disabled
IPV6Address: fe80:0000:0000:0000:2561:106d:eb4c:7410
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:18
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2

b) Go to File->Preference->Network->Host-only Network Details, looks good.


c) “VirtualBox NDIS6 Briged Networking Driver” is checked:


d)  Click the refresh button to get a new “MAC ADDRESS”.


e) After the new “MAC ADDRESS”, then everything is working fine. Linux virtual server starts up successfully.

So it is working by giving a new “MAC address”. Amazing !

This entry was posted in VirtualBox and tagged , , , , , , . Bookmark the permalink.

25 Responses to Interface (‘VirtualBox Host-Only Ethernet Adapter’) is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).

  1. elance says:

    Thank you, you solved my problem too!


  2. Brian says:

    Nice! Saved me hours – I doubt that I ever would have thought to try refreshing the MAC address!


  3. Awesome – thanks for the fix. Saved me quite some headache.


  4. Kagemand Andersen says:

    Might be a bit late to the party here, but it’s not the MAC address causing it. It’s the name of the Host Only. I’m guessing the machine you’re importing originally used ‘VirtualBox Host-Only Ethernet Adapter’ instead of ‘VirtualBox Host-Only Ethernet Adapter #2’. When opening the network settings for the VM, it automatically switches to #2 because it’s the only one there, thus fixing the problem when pressing ‘Okay’.

    I have the same problem. I tried renaming it, but it says that ‘VirtualBox Host-Only Ethernet Adapter’ already exists, despite it now showing up anywhere.


  5. Lera says:

    Thank you! I have spent almost two hours debugging this. Everyone else with this error seems to just check a box in the network adapter settings for the NDIS6 driver. What to do if that’s not your problem? I uninstalled and reinstalled and rebooted and used test builds and tried EVERTHING in all the trouble tickets I could find.

    Finally, your explanation with the MAC address refresh cured it *instantly*. Thank you thank you thank you!


  6. Adler says:

    Thank you!


  7. Piotr Kasprzyk says:

    What happened to the original “VirtualBox Host-Only Ethernet Adapter”? In my case it was converted to “bridge”, you can see it with “VBoxManage list bridgedifs” but I was unable to remove this network adapter from Windows 10 configuration.


  8. Kevin A. says:

    Error happened after updating windows 10
    Cannot vagrant up anymore:

    Command: [“startvm”, “0501201a-8118-47ca-a754-7b627807db48”, “–type”, “headless”]

    Stderr: VBoxManage.exe: error: Interface (‘VirtualBox Host-Only Ethernet Adapter #3’) is not a Host- Only Adapter interface (VERR_INTERNAL_ERROR)
    VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

    The refresh on the mac address did the trick. Thanks!


  9. Eliza says:

    Genial funciono era algo tan simple Chevere!!!!!


  10. Raul says:

    It worked for me. The virtual interface suddenly dissapeared from windows 10, after Vbox software removal and restart (with update in this case), network interface appeared again, but anyway I had to generate a new mac-address (BTW I had one manually configured)


  11. Andreas Stahl says:

    Oh thank you very much for this! Refreshing the Mac-Address also helped me after windows 10 Updates


  12. ana says:

    Thank you!!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s