Installed VirtualBox-6.1.34a-150636-Win on July 13 on Windows 11 dell laptop. I was able to bring up a pretty consistant vm in Linux mint.
Should note that I am using a bridged adapter so that I can hit the linux guest with SSH and SFTP
I installed the update today VirtualBox-6.1.36-152435-Win and now when I launch the VM I get this error message
Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Wi-Fi 6 AX201 160MHz' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
It was working fine before the update.
Potential bug with VirtualBox-6.1.36-152435-Win and bridged adapters
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Potential bug with VirtualBox-6.1.36-152435-Win and bridged adapters
I believe this means that the Bridged component failed to attach to the adapter for some reason.
Uninstall Virtualbox and reboot.
Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
Reboot again.
If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
Reinstall Virtualbox using right-click-Run-As-Administrator.
Uninstall Virtualbox and reboot.
Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
Reboot again.
If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
Reinstall Virtualbox using right-click-Run-As-Administrator.
Re: Potential bug with VirtualBox-6.1.36-152435-Win and bridged adapters
That worked. I believe the actual culprit here may have been the VPN.... Some how. Cannot prove it now but anyone experiencing this issue may want to check that as well.