Windows 2004 - HostOnly Adapter

[jmecsei]

Hi,
Now I got a new update for Windows called 2004. After this update my virtual machines can not start again.
I found a problem, that: If a virtual machine has a Host-OnlyAdapter it can not start.

Code: Select all

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).
Result code: E_FAIL (0x80004005)
Komponens: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Here are a Vagrantfile, what you can reproduce the problem:

Code: Select all

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "bento/debian-9"

  config.vm.provider "virtualbox" do |v|
    v.memory = 256
    v.cpus = 1
  end

  config.vm.network "private_network", ip: "192.168.100.126", nic_type: "82545EM"
  config.vm.provision "docker" do |d|
    d.run "mysql", image: "mysql:8",
      args: "-p 3306:3306 -e MYSQL_DATABASE=partner-service -e MYSQL_ROOT_PASSWORD=root"
  end
end

And I also attached a more detailed log message.

Virtualbox version: 6.1.8 r137981 (Qt5.6.2)
Vagrant version: 2.2.9

[scottgus1]

We don't support Vagrant-altered Virtualbox, they have their own support channels.

FWIW, when Windows 10 changes major versions, like 1903 to 2004, for instance, it often re-numbers the Host-Only network adapters. Try changing the guest's Host-Only network adapter dropdown to what Host-Only adapter is present.

[jmecsei]

I add the Vagrantfile to test quickly.
This error also happen if I add a new Network Interface to an existing vmachine.
(of course i create it in virtualbox)

I tried to uninstall and install it again, but not solve my problem.

[scottgus1]

Can you please put up a screenshot of your "Control Panel > Network and Sharing Center > Change adapter settings"? Look like this (I'm on Details view):

network connections.png (13.51 KiB) Viewed 1776 times

[jmecsei]

Of course

[scottgus1]

OK, so you do have a Host-Only adapter #2. Right-click that adapter, choose Properties, then Check that the Virtualbox NDIS6 Bridged Networking Driver binding is checked:

[jmecsei]

Yes it is checked

[jmecsei]

Here is my log from Vbox when I want to create a new machine with HostOnlyAdapter

[jmecsei]

I tried a hard restart instead of a normal start menu -> restart.
(shutdown /s /f /t 0)
And and and and ... now its work!
Thanks for all, but I curiously what was the problem

[scottgus1]

Hmmm... Interesting! Thanks for letting us know what fixed it for you.

With NDIS checked, I was stuck. This has happened before, I couldn't remember more of the solution.

Have fun!