VirtualBox

Ticket #14832 (reopened defect)

Opened 6 years ago

Last modified 11 months ago

Unable to use Host-Only adapters on Windows 10 Threshold 2

Reported by: kohenkatz Owned by:
Component: network/hostif Version: VirtualBox 5.0.10
Keywords: Cc:
Guest type: all Host type: Windows

Description

I installed the new Windows 10 update "threshold 2" via Windows Update, and VirtualBox is no longer able to use Host Only adapters. While it creates them, changes their IPs, and deletes them with no trouble, the following error message comes up when I try to run any VM with a Host Only interface attached:

Failed to open a session for the virtual machine Ubuntu Test.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (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}

This worked with no trouble before the Windows Update, and all other adapter types still work perfectly.

I originally had this issue with VirtualBox 5.0.1, so I uninstalled that one and installed 5.0.10, and I still have the issue.

Log file attached.

Attachments

VBox.log Download (39.7 KB) - added by kohenkatz 6 years ago.
HostOnlyAdapter.png Download (96.6 KB) - added by karthik.echo@… 13 months ago.
which i am unable to change the adapter, in anyother later version also. Kindly need your assistant i have done many troubleshooting steps there is no luck

Change History

Changed 6 years ago by kohenkatz

comment:1 Changed 6 years ago by kohenkatz

After a lot more searching, I found  this post on the forum which describes the issue. The fix listed there appears to work, except that now every time a Host Only interface is created, I need to go in and make the changes.

It appears that somehow on the previous version of Windows 10, VB was setting this automatically and it is no longer doing so.

comment:2 Changed 6 years ago by engineAL

I too had this issue after installing the Windows 10 update, and the fix above resolved the issue.

comment:3 Changed 6 years ago by dermoritz

Same issue here, can also confirm for version 5.0.11. kohenkatz' linked post worked... Probably the title should also contain "1511" - to be easier googled and prevent possible duplicates.

Last edited 6 years ago by dermoritz (previous) (diff)

comment:4 Changed 6 years ago by frank

Current workaround is to enable "NDIS6 Bridging" on the HostIF network device. Open the view with "network devices" (not in VBox!) and right click "Properties" of the HostIF.

comment:5 Changed 6 years ago by aleksey

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.

comment:6 Changed 6 years ago by frank

Or test the latest 5.0.x Windows test build.

comment:7 Changed 6 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Please reopen if still relevant with VBox 5.0.12.

comment:8 Changed 5 years ago by kenkyee

FYI, this is an issue w/ the latest Vbox 5.1.0 even after a uninstall/reinstall. If I didn't do the uninstall, it left two host only adapters (one from 5.0.x)

I had to uninstall/reinstall Virtualbox, then go to network settings, and modify the HostOnly Virtualbox adapter to use the NDIS6 component for it to work again.

comment:9 Changed 5 years ago by wanderr

  • Status changed from closed to reopened
  • Resolution fixed deleted

Just encountered this issue on 5.1.2 r108956 on windows 10 1607, the fix linked from comment 1 also fixed it for me

comment:10 Changed 5 years ago by orever

Still having this issue on 5.1.12. It happens every time I install an updated version. On Windows 7 host.

Last edited 5 years ago by orever (previous) (diff)

comment:11 Changed 4 years ago by aleksey

Is this still relevant for 5.2.8?

comment:12 Changed 4 years ago by Anny

unable to create a host only network interface VBOX 5.2.8

Hello,

I'd like to have your help by solving this issue :

I installed the VirtualBox Graphical User Interface Version 5.2.8 r121009 (Qt5.6.2), and have the same problem.

I'm unable to create a host only network interface. I checked and my PC has the VirtualBox NDIS6 Bridged networking driver active. I have this error when adding the host interface through the Global Tools option - Host Network Manager - Adding Network: It activates a screen to copy drivers, but nothing happened and i had this message at the end: Failed to create a host network interface

Querying NetCfgInstanceId failed (0x00000002).

Result Code: E_FAIL (0x80004005) Component: HostNetworkInterfaceWrap Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

Tjank you very much for your help and answer

Cordially,

Anny

Last edited 4 years ago by Anny (previous) (diff)

comment:13 Changed 3 years ago by socratis

Anny,

  1. Try to upgrade to 5.2.10.
  2. Disable/uninstall all 3rd party antivirus, and/or other system-wide affecting software.

comment:14 follow-ups: ↓ 15 ↓ 17 ↓ 18 ↓ 20 ↓ 22 Changed 2 years ago by narr mlo

This is yet again a hard fail, with lovely Windows 10 1903, and VirtualBox 6.0.8

I finally after the requisite hours chasing got it to go away with: 1) following the somewhat paranoid install instructions floating about with reluctant support people here -- disconnect internet/wifi, drop your Internet etc. protection (didn't uninstall, did turn off the two menu abilities of Norton), de-install VirtualBox, use Run as Admin on the installer, let installer start Virtualbox, then close it, remembering then to turn back on your Internet protection. I believe this dance does nothing, but parts of it might for some??

2) I found pretty hidden away a similarly cross-your-fingers-and-dance-backwards-three-times fix that's worked for competent-sounding others. This is to locate the actual one of the three Network Interfaces VirtualBox installs that is failing, from the detailed name in the error message and hovering over these until you find the one which shows such a label only that way - watch out as the #N numbering doesn't agree with the Windows label. Then: open its settings, _un_check the VirtualBox NDIS6 Bridged Networking Driver, close. Open again, check this Driver to be on. Close. Then Disable this same network adapter, and then enable it again.

Try a vagrant up, and likely you'll be back on the air.

I suspect it's only the Disable-Enable step that actually fixes the problem, but I leave that to those fixing for the _years_ this has been unreliable apparently with VirtualBox. I had seen the issue once or twice in the form of being asked to allow Admin on startup of vagrant boxes after recent version of VirtualBox, but the Win 10 1903 update now that it's released in May caused this to be an entirely hard fail -- without having done anything to VirtualBox until I went about repairing this fail.

Last edited 2 years ago by narr mlo (previous) (diff)

comment:15 in reply to: ↑ 14 Changed 2 years ago by viktor_jamrich

thanks man this defo worked for me ;)

Replying to narr mlo:

This is yet again a hard fail, with lovely Windows 10 1903, and VirtualBox 6.0.8

I finally after the requisite hours chasing got it to go away with: 1) following the somewhat paranoid install instructions floating about with reluctant support people here -- disconnect internet/wifi, drop your Internet etc. protection (didn't uninstall, did turn off the two menu abilities of Norton), de-install VirtualBox, use Run as Admin on the installer, let installer start Virtualbox, then close it, remembering then to turn back on your Internet protection. I believe this dance does nothing, but parts of it might for some??

2) I found pretty hidden away a similarly cross-your-fingers-and-dance-backwards-three-times fix that's worked for competent-sounding others. This is to locate the actual one of the three Network Interfaces VirtualBox installs that is failing, from the detailed name in the error message and hovering over these until you find the one which shows such a label only that way - watch out as the #N numbering doesn't agree with the Windows label. Then: open its settings, _un_check the VirtualBox NDIS6 Bridged Networking Driver, close. Open again, check this Driver to be on. Close. Then Disable this same network adapter, and then enable it again.

Try a vagrant up, and likely you'll be back on the air.

I suspect it's only the Disable-Enable step that actually fixes the problem, but I leave that to those fixing for the _years_ this has been unreliable apparently with VirtualBox. I had seen the issue once or twice in the form of being asked to allow Admin on startup of vagrant boxes after recent version of VirtualBox, but the Win 10 1903 update now that it's released in May caused this to be an entirely hard fail -- without having done anything to VirtualBox until I went about repairing this fail.

comment:16 Changed 2 years ago by ced-urls

I confirm it's the Disable-Enable step that actually fixes the problem (still existing in VirtualBox 6.0.10)

comment:17 in reply to: ↑ 14 Changed 2 years ago by AllJunior

I got the same issue and used the number 1 tip, worked fine for me: de-install VirtualBox, turn off the firewall and reinstall with admin privileges. Replying to narr mlo:

This is yet again a hard fail, with lovely Windows 10 1903, and VirtualBox 6.0.8

I finally after the requisite hours chasing got it to go away with: 1) following the somewhat paranoid install instructions floating about with reluctant support people here -- disconnect internet/wifi, drop your Internet etc. protection (didn't uninstall, did turn off the two menu abilities of Norton), de-install VirtualBox, use Run as Admin on the installer, let installer start Virtualbox, then close it, remembering then to turn back on your Internet protection. I believe this dance does nothing, but parts of it might for some??

2) I found pretty hidden away a similarly cross-your-fingers-and-dance-backwards-three-times fix that's worked for competent-sounding others. This is to locate the actual one of the three Network Interfaces VirtualBox installs that is failing, from the detailed name in the error message and hovering over these until you find the one which shows such a label only that way - watch out as the #N numbering doesn't agree with the Windows label. Then: open its settings, _un_check the VirtualBox NDIS6 Bridged Networking Driver, close. Open again, check this Driver to be on. Close. Then Disable this same network adapter, and then enable it again.

Try a vagrant up, and likely you'll be back on the air.

I suspect it's only the Disable-Enable step that actually fixes the problem, but I leave that to those fixing for the _years_ this has been unreliable apparently with VirtualBox. I had seen the issue once or twice in the form of being asked to allow Admin on startup of vagrant boxes after recent version of VirtualBox, but the Win 10 1903 update now that it's released in May caused this to be an entirely hard fail -- without having done anything to VirtualBox until I went about repairing this fail.

comment:18 in reply to: ↑ 14 Changed 2 years ago by Kom-o-kosy

Also an issue for me on Host only network. Windows 10 Pro - 1903, VirtualBox Version 6.0.12.

Tried variations of step 1 and none of them fixed the issue. Tried step 2, found the network device in Windows, went into Properties -> Configure -> Disable Device - OK (don't know if disabling it this way makes any difference, just how I had done it). Right clicked disabled network and selected Enable, and issue was resolved.

Replying to narr mlo:

This is yet again a hard fail, with lovely Windows 10 1903, and VirtualBox 6.0.8

I finally after the requisite hours chasing got it to go away with: 1) following the somewhat paranoid install instructions floating about with reluctant support people here -- disconnect internet/wifi, drop your Internet etc. protection (didn't uninstall, did turn off the two menu abilities of Norton), de-install VirtualBox, use Run as Admin on the installer, let installer start Virtualbox, then close it, remembering then to turn back on your Internet protection. I believe this dance does nothing, but parts of it might for some??

2) I found pretty hidden away a similarly cross-your-fingers-and-dance-backwards-three-times fix that's worked for competent-sounding others. This is to locate the actual one of the three Network Interfaces VirtualBox installs that is failing, from the detailed name in the error message and hovering over these until you find the one which shows such a label only that way - watch out as the #N numbering doesn't agree with the Windows label. Then: open its settings, _un_check the VirtualBox NDIS6 Bridged Networking Driver, close. Open again, check this Driver to be on. Close. Then Disable this same network adapter, and then enable it again.

Try a vagrant up, and likely you'll be back on the air.

I suspect it's only the Disable-Enable step that actually fixes the problem, but I leave that to those fixing for the _years_ this has been unreliable apparently with VirtualBox. I had seen the issue once or twice in the form of being asked to allow Admin on startup of vagrant boxes after recent version of VirtualBox, but the Win 10 1903 update now that it's released in May caused this to be an entirely hard fail -- without having done anything to VirtualBox until I went about repairing this fail.

comment:19 Changed 23 months ago by jmathias

I just had this issue after the Windows 10 update today, but in the process of writing this post I solved the issue:

My error:

""" Failed to open a session for the virtual machine docker-compose-vm.

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

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

My process:

  • Updated VirtualBox (I was notified of an update when opening the VM Manager, but I haven't in a while so I'm not sure if the update was for this particular issue).
  • Went to Host Network Manager and hit "enable" for the host there. - This didn't work.

* Created a new host (Adapter #3) and left it enabled (disabled the other). - This didn't work. However, tthe error message did not change; it kept saying "Adapter #2" instead of "Adapter #3" which was enabled.

  • Restarted my computer.
  • Did some disabling and reenabling of network adapters, and tried creating a network bridge from my wifi - didn't work. (aka random clicking around). At this point I realized that the error message should be saying Adapter #3.

* In the VirtualBox Manager, for the particular virtual machine that I use, I went to Details -> Settings -> Network, disabled the first adapter, and made sure the second that said the new "Adapter #3" was enabled. - This worked.

Edit: But now Internet doesn't work on the virtual machine. I went to Network Connections, clicked "Remove from Bridge" on Adapter #3, and remade a bridge from my wifi, but that didn't work, including after restarting the VirtualBox. In the VirtualBox settings, Adapter #3 doesn't appear when I select "Bridged Adapter". The other ones that I appear I don't see in Network Connections, though I'm trying a couple of them.

Second edit: I guess I just needed to disable the host-only adapter and enable NAT. Internet works now.

Last edited 23 months ago by jmathias (previous) (diff)

comment:20 in reply to: ↑ 14 Changed 20 months ago by fsilva

Thanks for info. Just to confirm, that the same situation occurred here (Virtualbox 6.0.16 on Windows 10 1903) and adapters on line. Made the second suggestion and that worked for me !!

Replying to narr mlo:

This is yet again a hard fail, with lovely Windows 10 1903, and VirtualBox 6.0.8

I finally after the requisite hours chasing got it to go away with: 1) following the somewhat paranoid install instructions floating about with reluctant support people here -- disconnect internet/wifi, drop your Internet etc. protection (didn't uninstall, did turn off the two menu abilities of Norton), de-install VirtualBox, use Run as Admin on the installer, let installer start Virtualbox, then close it, remembering then to turn back on your Internet protection. I believe this dance does nothing, but parts of it might for some??

2) I found pretty hidden away a similarly cross-your-fingers-and-dance-backwards-three-times fix that's worked for competent-sounding others. This is to locate the actual one of the three Network Interfaces VirtualBox installs that is failing, from the detailed name in the error message and hovering over these until you find the one which shows such a label only that way - watch out as the #N numbering doesn't agree with the Windows label. Then: open its settings, _un_check the VirtualBox NDIS6 Bridged Networking Driver, close. Open again, check this Driver to be on. Close. Then Disable this same network adapter, and then enable it again.

Try a vagrant up, and likely you'll be back on the air.

I suspect it's only the Disable-Enable step that actually fixes the problem, but I leave that to those fixing for the _years_ this has been unreliable apparently with VirtualBox. I had seen the issue once or twice in the form of being asked to allow Admin on startup of vagrant boxes after recent version of VirtualBox, but the Win 10 1903 update now that it's released in May caused this to be an entirely hard fail -- without having done anything to VirtualBox until I went about repairing this fail.

comment:21 Changed 14 months ago by chumkui

I have just had this issue on my Dell Inspiron 5491 2-in-1 using the wifi adapter (Intel AC-9560). I am running Windows 10 2004 (latest at time of writing) I installed VirtualBox Version 6.1.12 r139181 (Qt5.6.2) and had similar errors trying to start the networking from a Vagrant Up (I got the same trying to start the VM using the VirtualBox interface as well):

here was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "43783329-d0f5-4b8c-9130-973b5cb0c20b", "--type", "headless"]

Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_INTNET_FLT_IF_NOT_FOUND). VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole#

I solved the issue by uninstalling and reinstalling without the NDIS6 bridged driver and then disabling and renabling the Host Only network adapters a couple of times. I ran the Windows Troubleshooter on the adapter to check if it thought it was working - after that, it all magically worked. I am sure that unticking the NDIS adapter will probably work as well, but as I am not using it, I didn't install it.

Interestingly, I tried an older Lenovo desktop that is connected via a network cable i.e. not using Intel Wifi and it all worked flawlessly using the default install options (i.e. everything), so it must be a combination of the network adapter hardware somewhere along the line.

Last edited 14 months ago by chumkui (previous) (diff)

Changed 13 months ago by karthik.echo@…

which i am unable to change the adapter, in anyother later version also. Kindly need your assistant i have done many troubleshooting steps there is no luck

comment:22 in reply to: ↑ 14 Changed 11 months ago by ronil

Replying to narr mlo:

This is yet again a hard fail, with lovely Windows 10 1903, and VirtualBox 6.0.8

I finally after the requisite hours chasing got it to go away with: 1) following the somewhat paranoid install instructions floating about with reluctant support people here -- disconnect internet/wifi, drop your Internet etc. protection (didn't uninstall, did turn off the two menu abilities of Norton), de-install VirtualBox, use Run as Admin on the installer, let installer start Virtualbox, then close it, remembering then to turn back on your Internet protection. I believe this dance does nothing, but parts of it might for some??

2) I found pretty hidden away a similarly cross-your-fingers-and-dance-backwards-three-times fix that's worked for competent-sounding others. This is to locate the actual one of the three Network Interfaces VirtualBox installs that is failing, from the detailed name in the error message and hovering over these until you find the one which shows such a label only that way - watch out as the #N numbering doesn't agree with the Windows label. Then: open its settings, _un_check the VirtualBox NDIS6 Bridged Networking Driver, close. Open again, check this Driver to be on. Close. Then Disable this same network adapter, and then enable it again.

Try a vagrant up, and likely you'll be back on the air.

I suspect it's only the Disable-Enable step that actually fixes the problem, but I leave that to those fixing for the _years_ this has been unreliable apparently with VirtualBox. I had seen the issue once or twice in the form of being asked to allow Admin on startup of vagrant boxes after recent version of VirtualBox, but the Win 10 1903 update now that it's released in May caused this to be an entirely hard fail -- without having done anything to VirtualBox until I went about repairing this fail.

I was in doubt at the beginning, but I confirm that's works! VB 6.1.14r.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use