virtualbox.org

After Win10 did a big slow feature update this morning, I can no longer start a Win 10 VM with the stated reason that it no longer finds the network interface.

Could not start the machine Hxxx_Win10x64 because the following physical network interfaces were not found:

Intel(R) Dual Band Wireless-AC 7260 (adapter 1)

You can either change the machine's network settings or stop the machine.

When I try to change the network settings, there is no choice for the Bridged Adapter. Then I cancel and this error is reported:

Failed to open a session for the virtual machine Hxxx_Win10x64.

Nonexistent host networking interface, name 'Intel(R) Dual Band Wireless-AC 7260' (VERR_INTERNAL_ERROR).

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

Back at the VB Maanger program, I use the menu item Host Network Manager... on the File menu. There are no Network items in the list. I try to Create one, and get this error message:

Failed to create a host network interface.

Could not find Host Interface Networking driver! Please reinstall.

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

I did a Repair installation action using the VirtualBox-6.1.12-139181-Win.exe download and it does not fix the issue.

I still have the same network hardware on the host computer and my connection information is reported as follows.

Name: Local Area Connection
Description: Intel(R) Ethernet Connection I217-LM
Physical address (MAC): 6c:c2:17:e2:5f:4f
Status: Not operational
Maximum transmission unit: 1500
IPv4 address: 169.254.56.204/16
IPv6 address: fe80::8e2:714338cc%11/64
DNS servers: 192.168.1.1
Connectivity (IPv4/IPv6): Disconnected

Name: Local Area Connection* 2
Description: Microsoft Wi-Fi Direct Virtual Adapter
Physical address (MAC): a0:a824:4f:92
Status: Not operational
Maximum transmission unit: 1500
IPv4 address: 169.254.218.88/16
IPv6 address: fe80::79b75573:da58%7/64
DNS servers: fec0:0:0:ffff::1%1, fec0:0:0:ffff::2%1, fec0:0:0:ffff::3%1
Connectivity (IPv4/IPv6): Disconnected

Name: Local Area Connection* 3
Description: Microsoft Wi-Fi Direct Virtual Adapter #2
Physical address (MAC): a2:a824:4f:91
Status: Not operational
Maximum transmission unit: 1500
IPv4 address: 169.254.73.182/16
IPv6 address: fe80:3037:f83e:49b6%8/64
DNS servers: fec0:0:0:ffff::1%1, fec0:0:0:ffff::2%1, fec0:0:0:ffff::3%1
Connectivity (IPv4/IPv6): Disconnected

Name: Wireless Network Connection
Description: Intel(R) Dual Band Wireless-AC 7260
Physical address (MAC): a0:a824:4f:91
Status: Operational
Maximum transmission unit: 1500
Link speed (Receive/Transmit): 468/468 (Mbps)
DHCP enabled: Yes
DHCP servers: 192.168.2.12
DHCP lease obtained: ‎Saturday, ‎August ‎01, ‎2020 9:03:19 AM
DHCP lease expires: ‎Sunday, ‎August ‎02, ‎2020 9:03:19 AM
IPv4 address: 192.168.2.118/24
IPv6 address: fe80::ed12:d3ce:c239:ad79%13/64
Default gateway: 192.168.2.12
DNS servers: 192.168.2.12
DNS domain name:
DNS connection suffix:
DNS search suffix list:
Network name: three dog night unleashed
Network category: Private
Connectivity (IPv4/IPv6): Connected to Internet / Connected to local network

Any help is appreciated. I will try a complete reinstall next.

OK, I have some good news. As Administrator, I did an uninstall, reboot, and then re-install.

Now things are back to working and my VMs were still present and listed by the manager after the re-install.

The Host Network Manager... now shows a Host-Only item.

Great you got things going! A Run As Admin is often needed to get a good install of Virtualbox on Windows. Expect the same glitch next major Windows version update.

virtualbox.org

Win 10 Feature Update 2004 breaks host networking

Win 10 Feature Update 2004 breaks host networking

Re: Win 10 Feature Update 2004 breaks host networking

Re: Win 10 Feature Update 2004 breaks host networking