VirtualBox

Ticket #14428 (new defect)

Opened 4 years ago

Last modified 4 years ago

win 10 host and VB from 5.0 to latest test build = NO bridge networking

Reported by: giusi Owned by:
Component: network Version: VirtualBox 5.0.0
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

hi!

win 10 64 bit host , upgrade from win 8.1, win xp guest

no way to set network -bridge-

hope someone will be able to find a workaround as for the issue of the no sound: https://www.virtualbox.org/ticket/14361#comment:21

cheers

Attachments

VBoxSVC.3.zip Download (2.2 KB) - added by giusi 4 years ago.
r102375
win xp-2015-08-28-14-56-22.log Download (37.8 KB) - added by giusi 4 years ago.
VM log
screenshoots.jpg Download (123.1 KB) - added by giusi 4 years ago.
screenshoots
drivers.jpg Download (134.6 KB) - added by giusi 4 years ago.
drivers
doc1.7z Download (1.3 KB) - added by giusi 4 years ago.
here they are!
doc1.2.7z Download (1.3 KB) - added by giusi 4 years ago.
hope this helps!
network.jpg Download (61.2 KB) - added by giusi 4 years ago.
last!
driverquerycommand_as requested.zip Download (1.4 KB) - added by giusi 4 years ago.
here it is !for yr helping me and for my helping you
here it is.zip Download (1.4 KB) - added by giusi 4 years ago.
the more i give …
Take a Close Look.jpg Download (52.6 KB) - added by giusi 4 years ago.
the more you ask..and so on..and on..

Change History

comment:1 Changed 4 years ago by giusi

Hi!

win 10 home ed 64 bit host win xp sp3 pro guest

with new 5.0.2 the sound issue is SOLVED for me!! thxs so much really indeed! BUT the network -bridged- still not.. same frustrating behaviour to not able to choose my net adapter if i choose -bridge- i have - no way- to select any.. and i've also unistalled and reinstalled the most update driver for my realtek: Realtek PCIe GBE Family Controller driver 10.1.505.2015 mobo:  http://www.gigabyte.com/products/product-page.aspx?pid=4955#dl

any ideas..? have i to set something..? if yes what and moreover -how-...??

so much thxs indeed for all of you !!

cheers!!

:)

comment:2 Changed 4 years ago by giusi

..no one has this issue..?? :(

comment:3 Changed 4 years ago by doerakje

Oh yep, Did an upgrade from Windows 7 to W10 while running VB 4.3.12 and experiencing the same problem you have with the network bridge, but I could solve it:

  1. Export your VMs;
  2. Uninstall VBox; Reboot as requested.
  3. Empty C:\Users\<Username>\.VirtualBox (or place the files in a subdir for backup)
  4. Install VirtualBox V5.0.2 r 102096 with "Run as Administrator"
  5. Import your VMs;
  6. Choose in the Network bridge your network adapter (mine was a wifi adapter).
  7. Start the VM

I was happy again :>)

comment:4 Changed 4 years ago by giusi

hi doerakje !

4) have you also set a particular compability..??..for ex: for win 8 ..or so on..

or you have only set it to run as admin. ?

cheers!!

:)

comment:5 Changed 4 years ago by giusi

any way this not solved for me.. followed all the steps you clearly posted but:

first when i import the vm , step 5, then i was not able to start it...always error.. so i create a new one , guest win xp, but..no way or chance then to choose the network -bridge-..not found the adapter...

comment:6 Changed 4 years ago by giusi

no one has ideas..??!! so strange...

comment:7 Changed 4 years ago by giusi

just for let you know that latest 5.0.3.102290 did not solve the issue

comment:8 Changed 4 years ago by giusi

nor any of the newest test builds

comment:9 Changed 4 years ago by giusi

hi the very newest 5.0.3.102375 is a little step ahead: now i can see my realtek net adapter if i choose network bridge but i'm still not able to use cause if i start the vm i got error and it does not start at all i attach here the vboxsvc.log pls help! if you go to vbox forum you realize we are lot of people in this frustrating situation cheers!

Changed 4 years ago by giusi

comment:10 Changed 4 years ago by aleksey

guisi,

I explicitly asked for VM log, not VBoxSVC log, as well as the description of the error you are getting when your VM fails to start. Less words, more info, please.

comment:11 Changed 4 years ago by giusi

@ aleksey

"I explicitly asked for VM log, not VBoxSVC log, as well as the description of the error you are getting when your VM fails to start. Less words, more info, please."..:

here it is the error:

Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Codice 'uscita: E_FAIL (0x80004005) Componente: ConsoleWrap Interfaccia: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

and i've just attached the log you request

cheers

Last edited 4 years ago by giusi (previous) (diff)

Changed 4 years ago by giusi

VM log

comment:12 Changed 4 years ago by aleksey

Now we're talking. Your log indicates that you do not have the bridging driver loaded. Please uninstall VirtualBox, make sure there are no entries starting with 'VirtualBox Host-Only Ethernet Adapter' in Network Adapters in Device Manager. If there are, right-click and do 'Uninstall'. Reboot the system and install 102375 build, the one you have just uninstalled and probably have somewhere around already. Do not uncheck any components during install. Do not use compatibility mode. Just do install with all defaults unchanged. Run your VM and if it still fails with COMPONENT_NOT_FOUND, provide VM log again, along with the output of 'sc query vboxnetlwf'.

Changed 4 years ago by giusi

screenshoots

comment:13 Changed 4 years ago by giusi

@aleksey :

" Your log indicates that you do not have the bridging driver loaded"..:

pls take a look at my screenshoots attached..

comment:14 Changed 4 years ago by giusi

@aleksey:

just to let you know that downgrading to prior win 8.1 64bit the issue disappear so this is the prof that the only thing that really does matter is the interaction between win 10 as host and Vbox so the fix is really yet to come

comment:15 Changed 4 years ago by aleksey

Are you aware that on Windows 10 VirtualBox installs two network drivers: bridging driver called vboxnetlwf.sys and virtual adapter driver called vboxnetadp6.sys? The later is used to provide virtual network adapters that are used for host-only networking, while the former is used for bridging to host's physical network adapters. The 'sc query vboxnetlwf' command aims to find out if the driver is installed and running. Your log clearly shows that vboxnetlwf.sys is not loaded and vboxnetadp.sys is loaded instead of vboxnetadp6.sys. You have NDIS5 version of host-only adapter driver installed and running, and NDIS5 is not supported under Windows 10.

Changed 4 years ago by giusi

drivers

comment:16 Changed 4 years ago by giusi

@aleksey : pls take a close look to the pic i've attached...the two mentioned by you files

are really on my system in c\windows\system32\drivers... so where is the matter of the issue..??

comment:17 Changed 4 years ago by giusi

..all disappeared again..??.. test build stopped at 102322 since days.. pls do not leave us with this frustrating issue.. and take a close look at the last attach cheers

comment:18 Changed 4 years ago by giusi

Waters sings: "Is there anybody outthere?".....

comment:19 Changed 4 years ago by aleksey

(1) Start your VM (2) After it fails, provide VM log (3) and the output of "sc query vboxnetlwf"

comment:20 Changed 4 years ago by giusi

1)first take a close look at the last pic i've attached

3 ,three, days ago...

thanks

Last edited 4 years ago by giusi (previous) (diff)

comment:21 Changed 4 years ago by giusi

5.0.3.102449 do not solve bridge network..and for me has been a backward step in the countrary direction cause ,instead of r102375,

i not able again to see my realtek adapt if i choose network bridge..

so may be the enumerating issues has come back.. a nightmare..

comment:22 Changed 4 years ago by giusi

latest r102467 restablish the situation of r102375 netadapter realtek now visible and choosable but if selected bridge network vm fails to start as per my last pic attached here

so even with some steps in the right direction the issue is still there..

comment:24 follow-up: ↓ 25 Changed 4 years ago by aleksey

Please provide the output of

driverquery /fo list /v

, which lists all installed drivers and essential information about them.

Last edited 4 years ago by frank (previous) (diff)

Changed 4 years ago by giusi

here they are!

Changed 4 years ago by giusi

hope this helps!

Changed 4 years ago by giusi

last!

comment:25 in reply to: ↑ 24 ; follow-up: ↓ 26 Changed 4 years ago by giusi

Replying to aleksey:

Please provide the output of

driverquery /fo list /v

, which lists all installed drivers and essential information about them.

here they are!!

any ideas now..??!!

cheers!!

:)

comment:26 in reply to: ↑ 25 ; follow-up: ↓ 27 Changed 4 years ago by andyp1973

Replying to giusi:

here they are!!

I have had a quick look at what you uploaded to see how they compare to what I have working here with 5.0.3-102467 and the contents of doc1.7z and doc1.2.7z appear to be the same and don't appear to contain the output of the driverquery command listed above nor of all the commands that you were asked to run on the other ticket.

any ideas now..??!!

As an aside, I appreciate that English isn't your first language but the implied sentiment from this statement is "I have given you what you want now give me what I want" rather than wanting to work in a collaborative manner with those who are giving their time (some freely) to try and help you.

Anyhow, could you check that you have uploaded the right information and not the same thing twice by mistake?

Andy.

comment:27 in reply to: ↑ 26 Changed 4 years ago by giusi

Replying to andyp1973:

Replying to giusi:

here they are!!

I have had a quick look at what you uploaded to see how they compare to what I have working here with 5.0.3-102467 and the contents of doc1.7z and doc1.2.7z appear to be the same and don't appear to contain the output of the driverquery command listed above nor of all the commands that you were asked to run on the other ticket.

any ideas now..??!!

As an aside, I appreciate that English isn't your first language but the implied sentiment from this statement is "I have given you what you want now give me what I want" rather than wanting to work in a collaborative manner with those who are giving their time (some freely) to try and help you.

Anyhow, could you check that you have uploaded the right information and not the same thing twice by mistake?

Andy.

pls consider that i'm -also- helping you with these so many tests in order to solve a frustrating issue i think maingly for Oracle VBox am i wrong..??!!

cheers!!

:)

Changed 4 years ago by giusi

here it is !for yr helping me and for my helping you

comment:28 Changed 4 years ago by andyp1973

OK, I have had a quick look at the driver query output that you uploaded and the first thing I have noticed as a user (I am not an Oracle employee and don't know the VB internals without reading all of the source code) is...

Your listing appears to be that your VBoxNetAdp and VBoxNetFlt drivers are different to the ones that I have on my Windows 10 x64 install (5.0.3-102467). My VBoxNetAdp uses the Windows driver file VBoxNetAdp6.sys whereas yours is VBoxNetAdp.sys. Mine also uses VBoxNetLwf.sys as the VirtualBox NDIS 6.0 bridged driver whereas you have VBoxNetFlt.sys. Incidentally the control on this is set to manual and not started.

It would look to me as though there is a problem with the installer that you are running. Those more in the know might have other suggestions but I would start by removing the extension pack in VirtualBox and then uninstall VirtualBox. Reboot and rerun the driverquery command and make sure there are no VirtualBox related drivers listed.

If we can get you back to a known good state then we can try to move forward...

Andy.

Last edited 4 years ago by andyp1973 (previous) (diff)

comment:29 Changed 4 years ago by giusi

hi and thanks:

if you take a look at the so many attachments i was asked you realize that on my system there are already the 2 files you mention:

VBoxNetAdp6.sys VBoxNetLwf.sys

..so where is the fault..?

thxs so much!

cheers!

comment:30 Changed 4 years ago by andyp1973

Looking at the properties on VBoxNetAdp.sys versus VBoxNetAdp6.sys I believe that the former is from VirtualBox 4.xx and the latter is from VirtualBox 5.xx.

One assumes that with a major version number change there are changes to the interfaces and that 4.xx drivers won't work with 5.xx and it seems as though you may have inadvertently managed to configure a strange combination of the two versions.

I would start by uninstalling everything VirtualBox related which may also require manually deleting VBoxXXXX.sys files from C:\Windows\System32\drivers and any oemXXX.inf files (and their corresponding .pnf files) from C:\Windows\inf that relate to the VirtualBox drivers - the command:

findstr "VirtualBox" C:\Windows\inf\*.inf

run in a command prompt will show you.

Once you are confident that everything VirtualBox related has gone then reboot and try a clean install of VirtualBox and the extension pack and then rerun driverquery to see if things look different.

Obviously before doing any of this you should make sure you have a backup of VM configurations and hard disks just in case anything happens.

Andy.

Last edited 4 years ago by andyp1973 (previous) (diff)

comment:31 Changed 4 years ago by aleksey

giusi,

I appreciate the time you spend helping us to improve our product. And I am perfectly willing to assist you in resolving the matter. The problem is that you somehow won't listen to what I try to say. Quite a while ago (see comment 12) I asked you to follow a sequence of steps which, in my opinion, would have helped you to resolve the problem. As I understand, instead of following the steps you proceeded to persuade me that there was nothing wrong with your installation of VirtualBox, and there was a bug we didn't want to fix. As the output of 'driverquery' clearly shows your installation of VirtualBox uses older NDIS 5.1 drivers (VBoxNetAdp.sys and VBoxNetFlt.sys) instead of newer NDIS 6 ones (VBoxNetAdp6.sys and VBoxNetLwf.sys). This configuration is not supported under Windows 10. VirtualBox expects to find NDIS6 drivers and fails to start VM because these drivers are missing. Now, before we start looking for potential bugs in the installer, could it be that you have done something different while installing, like using compatibility mode or doing some additional steps removing some drivers and installing different ones? There are plenty of "magical" solutions floating around the Internet, which provide some bizarre ways to resolve the issues with VirtualBox bridging and Windows 10.

comment:32 Changed 4 years ago by aleksey

Regarding your observation that your system has VBoxNetAdp6.sys and VBoxNetLwf.sys, yes, it does. This means that at some point the right drivers have been installed. But it does not tell us if they are active and running. And driverquery shows that they are not running. So they are just some leftovers from previous installations, or, if you followed some "magic" solution, you may have inadvertently deactivated them and replaced them with old NDIS 5.1 versions.

comment:33 Changed 4 years ago by giusi

hi! thanks! but is this right..??..:

; $Id: VBoxNetAdp6.inf 100877 2015-06-09 14:23:56Z bird $
; @file
; VBoxNetAdp6.inf - VirtualBox NDIS6 Miniport Driver inf file
;
; Note: We use the same component id as the old NetAdp implementation ?
;
;
; Copyright (C) 2014-2015 Oracle Corporation
;
; This file is part of VirtualBox Open Source Edition (OSE), as
; available from http://www.virtualbox.org. This file is free software;
; you can redistribute it and/or modify it under the terms of the GNU
; General Public License (GPL) as published by the Free Software
; Foundation, in version 2 as it comes in the "COPYING" file of the
; VirtualBox OSE distribution. VirtualBox OSE is distributed in the
; hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
;

[Version]
Signature   = "$Windows NT$"
CatalogFile = VBoxNetAdp6.cat
Class       = Net
ClassGUID   = {4D36E972-E325-11CE-BFC1-08002BE10318}
Provider    = %Provider%
DriverVer = 08/27/2015,5.0.51


[Manufacturer]
%Provider% = VBox,NTx86,NTamd64

[ControlFlags]

[VBox]
%VBoxNetAdp6_Desc% = VBoxNetAdp6.ndi, sun_VBoxNetAdp

[VBox.NTx86]
%VBoxNetAdp6_Desc% = VBoxNetAdp6.ndi, sun_VBoxNetAdp

[VBox.NTamd64]
%VBoxNetAdp6_Desc% = VBoxNetAdp6.ndi, sun_VBoxNetAdp

[VBoxNetAdp6.ndi]
AddReg             = VBoxNetAdp6.ndi.AddReg
Characteristics    = 0x1 ; NCF_VIRTUAL
*IfType            = 0x6 ; IF_TYPE_ETHERNET_CSMACD
*MediaType         = 0x0 ; NdisMedium802_3
*PhysicalMediaType = 14  ; NdisPhysicalMedium802_3
CopyFiles          = VBoxNetAdp6.Files.Sys

[VBoxNetAdp6.ndi.Remove.Services]
DelService       = VBoxNetAdp,0x200 ; Stop the service before uninstalling

[VBoxNetAdp6.ndi.Services]
AddService = VBoxNetAdp, 2, VBoxNetAdp6.AddService

[VBoxNetAdp6.AddService]
DisplayName    = %VBoxNetAdp6Service_Desc%
ServiceType    = 1 ;SERVICE_KERNEL_DRIVER
StartType      = 1 ;SERVICE_SYSTEM_START
ErrorControl   = 1 ;SERVICE_ERROR_NORMAL
ServiceBinary  = %12%\VBoxNetAdp6.sys
LoadOrderGroup = NDIS

[SourceDisksNames]
1=%DiskDescription%,"",,

[SourceDisksFiles]
VBoxNetAdp6.sys=1

[DestinationDirs]
DefaultDestDir = 12
VBoxNetAdp6.Files.Sys   = 12   ; %windir%\System32\drivers

[VBoxNetAdp6.Files.Sys]
VBoxNetAdp6.sys,,,2

[VBoxNetAdp6.ndi.AddReg]
HKR,    ,            *NdisDeviceType, 0x00010001, 1   ; NDIS_DEVICE_TYPE_ENDPOINT
HKR,    ,            BusNumber,  0, "0"
HKR, Ndi,            Service,    0, VBoxNetAdp
HKR, Ndi,            HelpText,    , %VBoxNetAdp6_HELP%
HKR, Ndi\Interfaces, UpperRange, 0, ndis5
HKR, Ndi\Interfaces, LowerRange, 0, ethernet

[Strings]
Provider = "Oracle Corporation"
DiskDescription = "VirtualBox NDIS 6.0 Miniport Driver"
VBoxNetAdp6_Desc = "VirtualBox Host-Only Ethernet Adapter"
VBoxNetAdp6_HELP = "VirtualBox NDIS 6.0 Miniport Driver"
VBoxNetAdp6Service_Desc = "VirtualBox NDIS 6.0 Miniport Service"

because i read..: -UpperRange, 0, ndis5-.....

Last edited 4 years ago by frank (previous) (diff)

comment:34 Changed 4 years ago by andyp1973

According to the  Microsoft Documentation NDIS5 is correct as there is no NDIS6 option.

I can't see anything that suggests that this has changed in Windows 10.

comment:35 Changed 4 years ago by giusi

..but have you seen all the tech replies here..for ex the comment n 31:

"As the output of 'driverquery' clearly shows your installation of VirtualBox uses older NDIS 5.1 drivers (VBoxNetAdp.sys and VBoxNetFlt.sys) instead of newer NDIS 6 ones (VBoxNetAdp6.sys and VBoxNetLwf.sys). This configuration is not supported under Windows 10"...

so now i should need a clear reply consider that i've lost so much time around this issue

thx in advance

cheers

Last edited 4 years ago by giusi (previous) (diff)

comment:36 Changed 4 years ago by andyp1973

That is correct, the network stack in Windows 10 is NDIS6 - specifically I think Windows 10 is NDIS 6.50.

The UpperRange and LowerRange defined in the .inf file relate to where the provided driver (VBoxNetAdp6.sys) sits in the network stack and defines what sits immediately above it and below it.

For reasons known only to Microsoft it appears that they have left this upper boundary value as ndis5 despite the move in the protocol itself to version 6.x

Given the settings in the .inf file work for a very many people then it would suggest that they are correct and that there is something about the installation and configuration of VirtualBox on your PC that are causing the problem hence my suggestion earlier to remove everything VirtualBox related and install the new 5.0.4 version with all the default settings (no Windows 8.1 compatibility, Run As Administrator) etc.

Last edited 4 years ago by andyp1973 (previous) (diff)

comment:37 Changed 4 years ago by giusi

..the more i spent around this issue the more i realize that this matter should be resolved -directly- between Oracle and MS see for ex. what done by Mozilla C.E.O himself..:  http://www.mozillaitalia.org/home/2015/07/31/lettera-aperta-al-ceo-di-microsoft-non-facciamo-un-passo-indietro-in-termini-di-scelta-e-controllo/

because so many things has been decided upon our heads.. and this issue has become very very frustrating at all..

cheers!

comment:38 Changed 4 years ago by andyp1973

Sadly Windows has always been the same - the move from Win 3.1 to Win 9x mandated rewriting a lot of system level software as 32bit rather than 16bit. Windows NT required all hardware IO to be in kernel level drivers, Windows 2000 meant a move to WDM, etc. etc.

You either live with it and try to help figure out any issues, move to a more controlled solution (Apple) or a more open one (Linux) where you can see more of what is going on.

comment:39 Changed 4 years ago by giusi

i totally agree with you the fact is that up to now vbox 5.04 win 10 is not still in the s.o included for a -total compatibility- and this is a real pity isn't it..? still yet people with bridge network issue and so on, if you take a ride on the official support forum..

Last edited 4 years ago by giusi (previous) (diff)

comment:40 Changed 4 years ago by andyp1973

Hi Giusi...

If you just want to debate the how and why of Windows and its issues then this support ticket isn't the right forum and isn't something I want to commit any more time to.

If on the other hand you want to try some of the suggestions made above and feedback on the results then I am happy to take a look at them and see if we can at least get you to the same place as those of us who have got the current Windows 10 version of VirtualBox working.

Andy.

comment:41 Changed 4 years ago by giusi

i furnish so many reports to yr so many suggestions this meant a waste or lost of time such yrs as mine at this time the network bridge issue is still with yr latest 5.04 stable release build unsolved cheers

comment:42 Changed 4 years ago by andyp1973

I see no sign of you having uploaded a new output from running the driverquery command following the uninstall, cleanup and reinstall of 5.0.4.

comment:43 Changed 4 years ago by giusi

here it is! and this is still the -issue- :

Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Codice 'uscita: E_FAIL (0x80004005) Componente: ConsoleWrap Interfaccia: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Changed 4 years ago by giusi

the more i give ...

Changed 4 years ago by giusi

the more you ask..and so on..and on..

comment:44 Changed 4 years ago by frank

Removed the last inappropriate comment. Please focus on the actual problem.

comment:45 follow-up: ↓ 46 Changed 4 years ago by andyp1973

OK, so it seems as though the installer has used the same version of the drivers as before as there are the same entries in the output from the driverquery command.

I would suggest that your next step should be to uninstall VirtualBox, reboot your system, configure it to log what the installer is doing as per the steps shown here, re-run the installation process and submit the install log files as listed in that web page.

comment:46 in reply to: ↑ 45 Changed 4 years ago by giusi

Replying to andyp1973:

OK, so it seems as though the installer has used the same version of the drivers as before as there are the same entries in the output from the driverquery command.

I would suggest that your next step should be to uninstall VirtualBox, reboot your system, configure it to log what the installer is doing as per the steps shown here, re-run the installation process and submit the install log files as listed in that web page.

i'll be very glad to do so when finally i'll read : "The user manual provides a list of supported hosts. Windows 10 is still not among them." -no more- .

i really do not want to waste any other precious yrs and expecially mine time see for ex. the last post of another unlucky vb's user:

Re: Windows 10 Hosts

Postby Huswif » 9. Sep 2015, 17:02

 https://forums.virtualbox.org/viewtopic.php?f=6&t=68590&p=334850&sid=f7a3557945e690eca481e6efc87001e7#p334850

thanks so much for yr kind helping and also thanks to me,i say it by myself, for all of my precious time gifted to virtualbox

hope the a/m condition will be fullfilled asap

regards

comment:47 Changed 4 years ago by andyp1973

As I can't reproduce your issue with VirtualBox and the Realtek Ethernet adapter and as there hasn't been any feedback from them I am guessing the developers can't either then the only place we can get the information needed to figure out what is going on is from you.

If you don't want to run any more tests then that is up to you but don't be surprised if this issue doesn't get magically fixed in whichever version of VirtualBox becomes the first that officialy supports Windows 10 hosts.

comment:48 Changed 4 years ago by giusi

latest r102588 doesn't solve: network bridge bidirectional drag n drop

comment:49 Changed 4 years ago by giusi

same situation r102614

comment:50 Changed 4 years ago by giusi

same issue with r102676...

comment:51 Changed 4 years ago by giusi

same frustrating situation with latest r102814

comment:52 Changed 4 years ago by giusi

same with latest 102947

comment:53 Changed 4 years ago by giusi

same with latest 5.06..

comment:54 Changed 4 years ago by giusi

same latest test 5.07..: Apertura di una sessione per la Macchina Virtuale windows xp sp3 pro 2005 non riuscita.

Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Codice 'uscita: E_FAIL (0x80004005) Componente: ConsoleWrap Interfaccia: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

comment:55 follow-up: ↓ 56 Changed 4 years ago by p060477

hi

this is exact the same situation of mine also with latest vb 5.08 where in its manual is written compatible with win 10 RTM 10240 stable

any ideas??

comment:56 in reply to: ↑ 55 Changed 4 years ago by MichalT

I have the same problem on VB 5.0.10. The VM which has been working with bridged networking previously doesn't start with the message: Could not start the machine MintVM because the following physical network interfaces were not found:

Realtek PCIe GBE Family Controller #2 (adapter 1)

You can either change the machine's network settings or stop the machine.

This interface exists and in fact is the only connected interface. I also checked that it uses NDIS6. However, if I change configuration of the Realtek #2 adapter by turning off or on IP v6 protocol, VB starts to see the interface and bridged networking works. This is repeatable, I can provide logs or other info. Let me know what you need.

comment:57 Changed 4 years ago by Hezd

Hi

I've had same problem and tried all the recommendations. Turns out the real culprit was improved protection in Windows 10 and my Kaspersky, that is I noticed that the NDIS Bridge service did not get added to my network card upon install. An d I had problems manually adding it too. But when disabling Kaspersky and windows defender I could either manually add the virtualbox NDIS bridge service or just do reinstall and then the bridge service would be there. Afterwards I had absolutely no problems enabling bridge networking on several different linux guest machines, even with Kaspersky antivirus or windows defender enabled. So in short, just disable antivirus and defender during virtualbox install.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use