Startup problems with VirtualBox and Vagrant Boxes with private network

[swo11]

I have recently experienced two problems with both my VirtualBox Manager and Vagrant boxes in Windows 10.

I first experienced a problem doing "vagrant up" on a ubuntu/bionic64 Vagrant box which worked one month ago. I get the error:

":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)."

If I start the box from VirtualBox Manager, I obtain the same error. I could also reproduce it by creating a new box from scratch and adding the line

Code: Select all

  config.vm.network "private_network", ip: "192.168.33.10"

If I remove the line, the error disappears and the Vagrant box starts normally.

Besides this error, VirtualBox Manager (6.0.20, but various 6.1.* show a similar behaviour) itself starts correctly only a small number of times. Mostly, after the main window has opened, an error window is displayed with the message

"VirtualBox Manager has stopped working

A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available."

If I click the Debug button, and choose to debug with Visual Studio Community 2019, I get an Exception unhandled window with the following text:

"Unhandled exception at 0x0000000050E584AA (Qt5WidgetsVBox.dll) in VirtualBox.exe: 0xC000041D: An unhandled exception was encountered during a user callback."

I believe the only differences between the Windows 10 system I'm running and the one I ran one month ago are CUDA, VisualStudio 2019, and a large Windows update.

I have never had a single serious problem with VirtualBox or Vagrant, I do not know how to deal with it or what kind of information could be helpful to diagnose the current problem. Whatever information is required I will provide it.

[scottgus1]

We don't grok Vagrant here, but the VERR_INTNET_FLT_IF_NOT_FOUND error does happen on non-Vagrant-modified Virtualbox too.

Web-search "VERR_INTNET_FLT_IF_NOT_FOUND" for further details, and check in the Network and Sharing Center that the Host Only adapter #2 exists and in its Properties the Virtualbox Bridged binding is checked:



Also try: viewtopic.php?f=6&t=94568#p456926