VirtualBox

Opened 5 years ago

Last modified 5 years ago

#18260 new defect

Not able to Start VM in Virtual Box when Bridge Adapter Network Setting is Selected After latest update to Windows 10

Reported by: Linda Owned by:
Component: other Version: VirtualBox 6.0.0
Keywords: VM not Starting With Bridged Adapter Network Setting on VB Cc:
Guest type: Linux Host type: Windows

Description

Hi Team,

I am Not able to start VM on virtual box when Bridge Adapter Network Setting is Selected and This is seen after latest update to Windows 10.

Have tried all the possible solutions listed in google, Nothing Worked.

Have tried 5.2.18, 5.2.22 and also 6.0 versions of VB but observing same Error on all these version.

Below Error is Observed:

Failed to open a session for the virtual machine .

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}

Change History (6)

in reply to:  description comment:1 by Socratis, 5 years ago

Replying to Linda:

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

  1. You need to re-install VirtualBox to make sure that the Bridged adapter filter is properly installed. You'll need to do that with every Win10 major upgrade, because the Win10 upgrade is not an upgrade, it's a re-installation of a new OS with migration from the previous install. And the migration fails. This has been discussed ad nauseam in the forums, see next.
  1. It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".
Last edited 5 years ago by Socratis (previous) (diff)

comment:2 by Linda, 5 years ago

Hi ,

Thanks for the quick response. But I have already tried uninstall/reinstall of VB.

comment:3 by Socratis, 5 years ago

A technique that we've used in the forums that has solved a lot of headaches is:

  • Uninstall VirtualBox. Your VMs are going to be untouched. Reboot.
  • You may want to clean up your registry and/or filesystem at this point. CCleaner is a freeware utility that could help you. Mind the installation, it comes with "offers" from 3rd parties, known as "bundleware". Also, check out the Device Cleanup program that helps you to remove any unused devices from your computer.
  • Download (if you haven't already) the latest VirtualBox and its matching ExtPack. Store them in a common location, i.e. not on "Desktop", or "Documents", but to "Public/Downloads" for example.
  • Uninstall (don't simply disable) all 3rd party antivirus. If you're afraid about your computer being vulnerable, pull the Ethernet plug, disconnect your WiFi, don't go browsing around.
  • Locate the downloaded file in Windows Explorer. Right-click on the installer and select "Run-as-Administrator", even if you are the administrator. At the end of the installation, choose to "Start Oracle VM VirtualBox". Do not worry if your VMs do not show up.
  • If you're going to install the ExtPack, go to File » Preferences » Extensions. Click on the icon with the orange, down-pointing arrow on the right. Select the ExtPack from the previous steps.
  • Quit VirtualBox. Re-start VirtualBox as you would normally, i.e. from the Desktop shortcut or the Start menu.
  • Update the Guest Additions (GAs) in your guest(s), if the GAs are available for a specific guest.

comment:4 by Linda, 5 years ago

Hi ,

I tried this solution. But I am seeing the same issue.

in reply to:  3 comment:5 by Linda, 5 years ago

Hi ,

I tried this solution. But I am seeing the same issue.

comment:6 by Socratis, 5 years ago

Linda,

Did you completely uninstall the antivirus (all of them, except Defender), or you simply disabled them? Anything else "funky" running on your host?

Because if that's the case, something is preventing the Bridged filter to be installed, and I have no clue from over here what that "something" is.

I know it won't happen on a fresh Win10 installation, that's for sure...

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use