Hi Guys,
Since a couple of days ago I noticed the my VM's fail to boot up as they used too.
I used the version 6.1.28, but after searching the forums i noticed that there is a bug when using this version with Win10.
I decided to downgrade to 6.1.26, and since then, i'm having this issue with all my VM's ( I have a few Ubuntu VM's and Centos VM).
My windows 10 version is: 21H1 19043.1348
This is the error message i'm getting after a few seconds, during the machine boot:
Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (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}
Important facts to add with my issue:
* The installation doesn't create a dedicated network card as it used too. (That was my 1st time i started notice something is not right).
* In the Device Manager i didn't noticed any drivers need to be installed under the network category.
* in the original network card that is plugged to my PC, i see in the NIC properties that the NDIS of virtual box is checked ( and yes, i tried to remove the "v" and then pressing the Ok, and then opening the NIC properties again, and re-enabling the NDIS, it didn't help.
* I installed the build 6.1.26 r145957 as and Administrator didn't help.
* I installed in a different hard drive - didn't help.
* I rebooted the PC after every time i uninstalled and reinstalled on a different drive. didn't help
* I used Device cleanup utility but didn't find something which was relevant to my issue. didn't help
The logs are very short in my case, so here they are:
00:00:08.697899 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
00:00:08.698001 Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND)}, preserve=false aResultDetail=-3700
00:00:08.698462 Console: Machine state changed to 'PoweredOff'
00:00:08.717391 Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, rc=E_FAIL (0X80004005))
00:00:09.218754 GUI: UIMachineViewScale::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:09.218812 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up (Display::setVideoModeHint)}, preserve=false aResultDetail=0
00:00:09.219362 GUI: Aborting startup due to power up progress issue detected...
End of logs
Sure hope to solve this thing with you.
I would appreciate your help in this issue.
Host Interface Networking issue.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Host Interface Networking issue.
I suspect that the downgrade did not remove something it should have. Please try this:
Uninstall Virtualbox and reboot.
Check that the Host Only adapter is gone from the host's network adapters. If there is still a Host-Only adapter there, try to delete it.
Check that there are no .sys files starting with "VBox" in "C:\Windows\System32\drivers\". A normal Virtualbox install should have up to 5 such files in Drivers. You should have none now.
Right-click the 6.1.26 installer and Run As Administrator.
Don't forget the 6.1.26 Extension Pack.
What does Virtualbox do now?
Uninstall Virtualbox and reboot.
Check that the Host Only adapter is gone from the host's network adapters. If there is still a Host-Only adapter there, try to delete it.
Check that there are no .sys files starting with "VBox" in "C:\Windows\System32\drivers\". A normal Virtualbox install should have up to 5 such files in Drivers. You should have none now.
Right-click the 6.1.26 installer and Run As Administrator.
Don't forget the 6.1.26 Extension Pack.
What does Virtualbox do now?
Re: Host Interface Networking issue.
Hey Scott, how are you?
Looks like now Virtualbox is working great.
The problem i had was like you mentioned, some .sys vbox files were in the c:\windows\system32\drivers folder, one i deleted them i reinstalled the Vbox (as administrator), and all is good.
Thanks a lot for your assistance.
Looks like now Virtualbox is working great.
The problem i had was like you mentioned, some .sys vbox files were in the c:\windows\system32\drivers folder, one i deleted them i reinstalled the Vbox (as administrator), and all is good.
Thanks a lot for your assistance.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Host Interface Networking issue.
Great! Glad you're up and running.