Host-Only network adapter failure after updating Win. 10

Discussions related to using VirtualBox on Windows hosts.
Post Reply
engineAL
Posts: 2
Joined: 13. Nov 2015, 23:02

Host-Only network adapter failure after updating Win. 10

Post by engineAL »

I updated my host to the Windows 10 Fall Update (build 10586.3) last night, which has caused my VBox machines that use a host-only adapter to not boot with this message:

Code: Select all

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

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}
I am using VBox version 5.0.10 r104061, and before the update, the host-only network adapter worked fine, and no changes have been made to its configuration. The guest VMs are running Ubuntu. I have tried reinstalling both VBox versions 5.0.8 and 5.0.10, but receive the same error when starting the machine. The message pops up in a box on the host machine before the guest even shows the VBox boot screen.

Here are the network settings from VBoxManage showvminfo "VMNAME":

Code: Select all

NIC 1:           MAC: 0800276E0BD6, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:           MAC: 0800270A8615, Attachment: Host-only Interface 'VirtualBox Host-Only Ethernet Adapter', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
Here is the VBoxHardening.log: http://pastebin.com/JFiRwBwu. Thanks for any suggestions that you might have!
engineAL
Posts: 2
Joined: 13. Nov 2015, 23:02

Re: Host-Only network adapter failure after updating Win. 10

Post by engineAL »

The fix was found in this forum post: viewtopic.php?f=6&t=68590&start=450#p345379

"VirtualBox NDIS6 Bridged Networking Driver" was switched off in the "VirtualBox Host-Only Network" adapter properties. After switching it back on, the host-only adapter resumed functioning properly.
Post Reply