Opened 9 years ago
Last modified 2 years ago
#15060 new defect
Can't start virtual machine with bridged interfaces
| Reported by: | Sam Morris | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 5.0.14 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Windows |
Description
When resuming a saved virtual machine, I get the message:
Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (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}
This is on Windows 10.0.10586, but didn't start when upgrading to this version... I've been using Virtualbox fine for the last couple of weeks until this morning.
I did some searching and it seems that others were able to resolve the same issue by enabling the 'VirtualBox NDIS6 Bridged Networking Driver' for their network adapters, but I checked each adapter and it's already enabled for them all.
The virtual machine logs contain:
00:00:03.187772 IntNet#0: szNetwork={HostInterfaceNetworking-Realtek PCIe GBE Family Controller} enmTrunkType=3 szTrunk={\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}} fFlags=0x14000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:03.187821 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DrvIntNet.cpp(1753) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.187846 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller'
00:00:03.187879 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DevE1000.cpp(7715) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.187883 VMSetError: Failed to attach the network LUN
00:00:03.187893 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:03.190010 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.197890 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.204536 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.211773 GIM: KVM: Resetting MSRs
00:00:03.341518 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_INTNET_FLT_IF_NOT_FOUND).
00:00:03.341550 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:03.341693 Console: Machine state changed to 'PoweredOff'
00:00:03.352282 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))
Attachments (6)
Change History (36)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
I have had the same problem on Windows 8.1 for a long time. Something about enabling a second host-only adapter causes this issue.
comment:3 by , 9 years ago
here is my error and logs
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).
Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
00:00:02.937132 IntNet#0: szNetwork={HostInterfaceNetworking-Intel(R) Ethernet Connection I217-LM} enmTrunkType=3 szTrunk={\DEVICE\{0AF7C152-73C0-4EB2-BB16-C9647DB2E7AA}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false 00:00:02.937775 IntNet#1: szNetwork={HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter} enmTrunkType=3 szTrunk={\DEVICE\{253C52B4-60E2-4AB4-A050-E9CC6D6F27B7}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false 00:00:02.938241 IntNet#2: szNetwork={HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2} enmTrunkType=3 szTrunk={\DEVICE\{7909BBCE-7B21-4339-A458-8427EE763BEB}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false 00:00:02.938312 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DrvIntNet.cpp(1753) int cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:02.938331 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' 00:00:02.938384 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DevE1000.cpp(7715) int cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:02.938387 VMSetError: Failed to attach the network LUN 00:00:02.938416 PDM: Failed to construct 'e1000'/2! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found. 00:00:03.075713 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 #2' (VERR_INTNET_FLT_IF_NOT_FOUND). 00:00:03.075744 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false aResultDetail=0 00:00:03.076318 Console: Machine state changed to 'PoweredOff' 00:00:03.088381 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005)) 00:00:03.235545 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600 00:00:03.235721 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={7303a66d-433b-25a4-f9a8-fcadf87e0c2a} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
comment:4 by , 9 years ago
C:\Program Files\Oracle\VirtualBox>VBoxManage.exe list hostonlyifs Name: VirtualBox Host-Only Ethernet Adapter #2 GUID: 7909bbce-7b21-4339-a458-8427ee763beb DHCP: Disabled IPAddress: 192.168.99.1 NetworkMask: 255.255.255.0 IPV6Address: fe80:0000:0000:0000:3cd7:cadd:cb89:6e15 IPV6NetworkMaskPrefixLength: 64 HardwareAddress: 0a:00:27:00:00:00 MediumType: Ethernet Status: Up VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2
Name: VirtualBox Host-Only Ethernet Adapter GUID: 253c52b4-60e2-4ab4-a050-e9cc6d6f27b7 DHCP: Disabled IPAddress: 192.168.245.1 NetworkMask: 255.255.255.0 IPV6Address: fe80:0000:0000:0000:41c3:c24f:2466:fb6d IPV6NetworkMaskPrefixLength: 64 HardwareAddress: 0a:00:27:00:00:00 MediumType: Ethernet Status: Up VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
comment:8 by , 8 years ago
Note the more verbose error logging:
00:00:04.344899 IntNet#0: szNetwork={HostInterfaceNetworking-Realtek PCIe GBE Family Controller} enmTrunkType=3 szTrunk={\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}} fFlags=0x14000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:04.344962 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DrvIntNet.cpp(1753) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:04.345159 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller'
00:00:04.345251 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DevVirtioNet.cpp(2082) int __cdecl vnetConstruct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:04.345255 VMSetError: Failed to attach the network LUN
00:00:04.345271 PDM: Failed to construct 'virtio-net'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:04.347482 AIOMgr: Async flushes not supported
00:00:04.377368 AIOMgr: Async flushes not supported
00:00:04.447264 AIOMgr: Async flushes not supported
00:00:04.453208 AIOMgr: Async flushes not supported
00:00:04.460953 TxTimer stats (avg/min/max): 0 usec -1 usec 0 usec
00:00:04.461436 GIM: KVM: Resetting MSRs
00:00:04.592346 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_INTNET_FLT_IF_NOT_FOUND).
follow-up: 19 comment:13 by , 7 years ago
Could you run “VBoxBugReport <vm_name>” with r121161 installed and send the resulting archive to aleksey dot ilyushin at oracle dot com?
comment:19 by , 5 years ago
comment:20 by , 5 years ago
I've noticed the following event in the Windows System Event Log when I boot up. It may be related:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="VBoxNetLwf" /> <EventID Qualifiers="49156">12</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-10-27T11:38:21.734816600Z" /> <EventRecordID>5632</EventRecordID> <Channel>System</Channel> <Computer>tycho</Computer> <Security /> </System> - <EventData> <Data>\Device\VBoxNetLwf</Data> <Binary>0000000001000000000000000C0004C0080000000000000000000000000000000000000000000000</Binary> </EventData> </Event>
VBoxNetLwf is "the light-weight filter driver for NDIS6". If it fails to load then that may explain the VERR_INTNET_FLT_IF_NOT_FOUND error.
As for what event id 12 is... I've no idea. Event Viewer only gives the following for the description:
The driver detected an internal driver error on \Device\VBoxNetLwf.
by , 4 years ago
| Attachment: | vbox interfaces.png added |
|---|
by , 4 years ago
| Attachment: | vbox interfaces.2.png added |
|---|
comment:23 by , 4 years ago
I have noticed that the list of network interfaces available for bridging in VM settings contains way more entries than it should:
I expect to see only two entries:
PS C:\> Get-NetAdapter | Format-List Name : VirtualBox Host-Only Network #2 InterfaceDescription : VirtualBox Host-Only Ethernet Adapter #2 InterfaceIndex : 23 MacAddress : XX-XX-XX-XX-XX-XX MediaType : 802.3 PhysicalMediaType : 802.3 InterfaceOperationalStatus : Up AdminStatus : Up LinkSpeed(Gbps) : 1 MediaConnectionState : Connected ConnectorPresent : False DriverInformation : Driver Date 2020-10-16 Version 6.1.16.40961 NDIS 6.0 Name : Local Area Connection 2 InterfaceDescription : Realtek PCIe GBE Family Controller InterfaceIndex : 17 MacAddress : XX-XX-XX-XX-XX-XX MediaType : 802.3 PhysicalMediaType : 802.3 InterfaceOperationalStatus : Up AdminStatus : Up LinkSpeed(Gbps) : 1 MediaConnectionState : Connected ConnectorPresent : True DriverInformation : Driver Date 2015-04-10 Version 9.1.410.2015 NDIS 6.40
I have tried to start VMs with each of the Realtek interfaces shown by VirtualBox and they both don't work.
The Edimax interface used to exist on this PC... about seven years ago. There is no remnant of it anywhere that I can find other than as displayed by Virtualbox.
As to why both the current (existing) and removed (non-existing) Realtek and Edimax (respecively) interfaces appear twice: this happened after I replaced my motherboard a long time ago. As far as I remember, this bug predates the motherboard swap.
But I would still like to know where on earth VirtualBox is getting this weird list of network adapters!
by , 3 years ago
| Attachment: | VB_Error.png added |
|---|
comment:25 by , 3 years ago
I had a similar issue on a fresh install of 6.1.32, but was able to fix it. Not sure if my issue was related, but it looked pretty similar. I copied a .vdi VM from another machine, then added it to VirtualBox. Modified the NIC properties, so the bridge would use the appropriate physical NIC on the current host. Started the VM and got this error.
2650.4f8: supHardNtVpFreeOrReplacePrivateExecMemory: Free attempt #1 succeeded: 0x0 [00007ff7708d0000/00007ff7708d0000 LB 0/0x8000] 2650.4f8: supHardNtVpFreeOrReplacePrivateExecMemory: QVM after free 0: [0000000000000000]/00007ff7708d0000 LB 0x7f0a20000 s=0x10000 ap=0x0 rp=0x00000000000001 2650.4f8: 00007ff7708d8000-00007fff612effff 0x0001/0x0000 0x0000000 2650.4f8: *00007fff612f0000-00007fff612f0fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff612f1000-00007fff612f2fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff612f3000-00007fff612f3fff 0x0040/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff612f4000-00007fff612f4fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff612f5000-00007fff612f5fff 0x0040/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff612f6000-00007fff612f7fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff612f8000-00007fff612f8fff 0x0040/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff612f9000-00007fff6138efff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff6138f000-00007fff61391fff 0x0040/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff61392000-00007fff61392fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff61393000-00007fff61393fff 0x0040/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff61394000-00007fff61407fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff61408000-00007fff6144efff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff6144f000-00007fff61459fff 0x0008/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff6145a000-00007fff61467fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: 00007fff61468000-00007fff61468fff 0x0004/0x0080 0x1000000 \Device\HarddiskVolume4\Windows\System32\ntdll.dll 2650.4f8: Error (rc=-5644): 2650.4f8: Too many regions for ntdll.dll. 2650.4f8: Error (rc=-5644): 2650.4f8: supHardenedWinVerifyProcess failed with Unknown Status -5644 (0xffffe9f4): Too many regions for ntdll.dll. 2650.4f8: Error -5644 in supR3HardNtChildPurify! (enmWhat=5) 2650.4f8: supHardenedWinVerifyProcess failed with Unknown Status -5644 (0xffffe9f4): Too many regions for ntdll.dll. 2650.4f8: supR3HardNtEnableThreadCreationEx:
I disabled the VM network adapter (bridged to physical NIC), and the VM booted. I re-enabled the network adapter, and same error. I checked event viewer, but didn't see any errors about VBoxNetLwf.ndi. This makes me think my root problem may be different than the OP's. Next, I tried disabling IPv6 on the "VirtualBox Host-Only Network" adapter, and disabled/enabled the NIC. After that the VM fired right up. I went back and re-enabled IPv6 on the network adapter, restarted the VM and everything was fine. Currently I have the "VirtualBox Host-Only Network" adapter disabled (since I'm not using it), and it's working fine.
So this probably isn't the same problem the OP is having, but if you were lead here like I was with the similar error messages, here's something simple to try. Restart your PC, or just disable/enable the "VirtualBox Host-Only Network" adapter.
comment:27 by , 2 years ago
Regarding these log messages:
00:00:07.049670 IntNet#0: szNetwork={HostInterfaceNetworking-Realtek PCIe GBE Family Controller} enmTrunkType=3 szTrunk={\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}} fFlags=0x14000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:07.049751 VMSetError: F:\tinderbox\win-6.1\src\VBox\Devices\Network\DrvIntNet.cpp(1765) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:07.050007 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller'
00:00:07.050098 VMSetError: F:\tinderbox\win-6.1\src\VBox\Devices\Network\DevVirtioNet.cpp(2331) int __cdecl vnetR3Construct(struct PDMDEVINSR3 *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:07.050101 VMSetError: Failed to attach the network LUN
00:00:07.050144 PDM: Failed to construct 'virtio-net'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
It appears VirtualBox is trying to attach to {\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF} and this interface can't be found.
In the VM settings, the list of adapters that VirtualBox presents for bridging too appears to be based off the InterfaceDescription property:
PS C:\> Get-NetAdapter Name InterfaceDescription ifIndex Status MacAddress LinkSpeed ---- -------------------- ------- ------ ---------- --------- Local Area Connection 2 Realtek PCIe GBE Family Controller 18 Up 90-E6-BA-XX-XX-XX 1 Gbps
I believe my system has somehow managed to end up with multiple interfaces with the same description (bloody Windows...), and VirtualBox is not handling this case, and attaching to the wrong interface.
I discovered the super-secret registry key, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}\Kernel. Only NetSetupSvc and TrustedInstaller are permitted to access this key. Note the GUID in the path to the key: it matches the interface identified in the log message above.
The values for this key are:
| ifAlias | Local Area Connection |
| ifDescr | Realtek PCIe GBE Family Controller |
Note that the ifAlias does _not_ match the Name property from Get-NetAdapter, above.
There is another cousin key, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces\{95A5360B-A4D4-4EFB-9DEE-1C6DEEF029C5}\Kernel; its values are:
| ifAlias | Local Area Connection 2 |
| ifDescr | Realtek PCIe GBE Family Controller |
Note that the ifAlias of this key _does_ match the Name property of Get-NetAdapter.
Based on the above, I believe VirtualBox is searching for the Realtek PCIe GBE Family Controller interface and finding & trying to attach to {CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}, which does not exist on my system, resulting in the VERR_INTNET_FLT_IF_NOT_FOUND error.
VirtualBox should be be finding {95A5360B-A4D4-4EFB-9DEE-1C6DEEF029C5}, which does exist on my system.
I think VirtualBox needs to account for the possibility of multiple interfaces with the same ifAlias. Rather than presenting/storing/searching for the interface by its description, it should probably be using the interface name, which is unique. Of course, that will break everyone's VM configurations. Alternatively, VirtualBox could not stop searching after the first interface description match, and continue on, trying to attach to each matching interface until one of the attachments is successful.
But those are code changes, which I don't want to hold my breath for.
In the mean time, I need to find a way to clean out all trace of this {CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF} interface which has made life so miserable for the last 7 years.
comment:28 by , 2 years ago
Doing some more digging in the registry, it seems that the GUIDs above are also present within HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318} (according to System-Defined Device Setup Classes Available to Vendors this GUID is the class identifier for network adapters.
PS C:\> $adapters = "HKLM:\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}"
PS C:\> Get-ItemProperty $(Join-Path -Path $adapters -ChildPath "\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}\Connection")
Name : Local Area Connection
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}\Connection
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}
PSChildName : Connection
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry
PS C:\> Get-ItemProperty $(Join-Path -Path $adapters -ChildPath "\{95A5360B-A4D4-4EFB-9DEE-1C6DEEF029C5}\Connection")
Name : Local Area Connection 2
PnPInstanceId : PCI\VEN_10EC&DEV_8168&SUBSYS_83A31043&REV_03\4&61613ac&0&00E7
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{95A5360B-A4D4-4EFB-9DEE-1C6DEEF029C5}\Connection
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{95A5360B-A4D4-4EFB-9DEE-1C6DEEF029C5}
PSChildName : Connection
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry
Note, the good adapter has a PnpInstanceId that corresponds to the network adapter as shown in Device Manager; the bad adapter has no such property.
comment:29 by , 2 years ago
Deleting this key didn't help:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}
comment:30 by , 2 years ago
This command prints the list of interfaces that VirtualBox offers for bridging, with much more detail than is available in the GUI.
PS C:\> & 'C:\Program Files\Oracle\VirtualBox\VBoxManage.exe' list bridgedifs Name: Realtek PCIe GBE Family Controller GUID: 95a5360b-a4d4-4efb-9dee-1c6deef029c5 DHCP: Enabled IPAddress: XXX NetworkMask: 255.255.255.0 IPV6Address: XXX IPV6NetworkMaskPrefixLength: 64 HardwareAddress: XX:XX:XX:XX:XX:XX MediumType: Ethernet Wireless: No Status: Up VBoxNetworkName: HostInterfaceNetworking-Realtek PCIe GBE Family Controller Name: Realtek PCIe GBE Family Controller GUID: ca0a5fea-99b8-4f54-89cc-c3f81004a5ff DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Wireless: No Status: Down VBoxNetworkName: HostInterfaceNetworking-Realtek PCIe GBE Family Controller Name: Edimax 802.11g Wireless PCI Card GUID: 57ae599d-acd0-4676-90a6-c7b3df372c12 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Wireless: No Status: Down VBoxNetworkName: HostInterfaceNetworking-Edimax 802.11g Wireless PCI Card Name: Edimax 802.11g Wireless PCI Card #2 GUID: d1890157-bd27-4a89-9ca7-b8b03e97af53 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Wireless: No Status: Down VBoxNetworkName: HostInterfaceNetworking-Edimax 802.11g Wireless PCI Card #2 Name: Realtek PCIe GBE Family Controller #2 GUID: 8cb90d6b-2c50-49cd-9b2f-4c671ea640c3 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Wireless: No Status: Down VBoxNetworkName: HostInterfaceNetworking-Realtek PCIe GBE Family Controller #2
We can see there are two entries with the same name, with GUIDs corresponding to the values we see in the registry & Get-NetAdapters.
Also present are entries for my Edimax wireless card that hasn't been present on this system for like 9 years.
comment:31 by , 2 years ago
Right, here goes nothing. Deleting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF...
O frabjous day! Callooh! Callay!
I can use bridged networking for the first time in 7 years!
Leaving this open because I think VirtualBox shouldn't be trawling around inside the completely undocumented .
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces to discover available network interfaces (and getting the wrong data when duplicate interfaces with the same description are present)
VirtualBox uses INetCfg <https://learn.microsoft.com/en-us/previous-versions/windows/hardware/network/ff547694(v=vs.85)> to enumerate network interfaces which, I guess, is trawling through
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces. In doing so, VirtualBox needs account for fact that the interface description is not unique across the interfaces returned by INetCfg.
And a hearty curse at Windows for keeping the crucial registry key that would have let me solve this problem years ago locked away in a way that prevents administrators from even reading it. God, I wish I could bill Microsoft for the many hours of my life that they have wasted.
This appears to be the same issue I am having. Been using 5.0.10 r104061 . I am on the Windows 10 fast track developer ring so I get new Windows 10 builds all the times. For me as of Windows 10 Build 14251.rs1_release.160124-1059 cannot startup my VMs anymore. I have a strong feeling this is identical to the previous poster. I have 2 VMs so far and both are having the same problem
12a8.12ac: Log file opened: 5.0.10r104061 g_hStartupLog=0000000000000058 g_uNtVerCombined=0xa037ab00 12a8.12ac: \SystemRoot\System32\ntdll.dll: 12a8.12ac: CreationTime: 2016-01-25T04:23:03.228793500Z 12a8.12ac: LastWriteTime: 2016-01-25T04:23:03.228793500Z 12a8.12ac: ChangeTime: 2016-01-28T18:40:23.580832700Z 12a8.12ac: FileAttributes: 0x20 12a8.12ac: Size: 0x1c3d38 12a8.12ac: NT Headers: 0xd8 12a8.12ac: Timestamp: 0x56a54488 12a8.12ac: Machine: 0x8664 - amd64 12a8.12ac: Timestamp: 0x56a54488 12a8.12ac: Image Version: 10.0 12a8.12ac: SizeOfImage: 0x1ca000 (1875968) 12a8.12ac: Resource Dir: 0x162000 LB 0x66370 12a8.12ac: ProductName: Microsoftﾂｮ Windowsﾂｮ Operating System 12a8.12ac: ProductVersion: 10.0.14251.1000 12a8.12ac: FileVersion: 10.0.14251.1000 (rs1_release.160124-1059) 12a8.12ac: FileDescription: NT Layer DLL 12a8.12ac: \SystemRoot\System32\kernel32.dll: 12a8.12ac: CreationTime: 2016-01-25T04:22:39.523783500Z 12a8.12ac: LastWriteTime: 2016-01-25T04:22:39.523783500Z 12a8.12ac: ChangeTime: 2016-01-28T18:40:23.018335200Z 12a8.12ac: FileAttributes: 0x20 12a8.12ac: Size: 0xa9790 12a8.12ac: NT Headers: 0xf0 12a8.12ac: Timestamp: 0x56a54538 12a8.12ac: Machine: 0x8664 - amd64 12a8.12ac: Timestamp: 0x56a54538 12a8.12ac: Image Version: 10.0 12a8.12ac: SizeOfImage: 0xab000 (700416) 12a8.12ac: Resource Dir: 0xa9000 LB 0x528 12a8.12ac: ProductName: Microsoftﾂｮ Windowsﾂｮ Operating System 12a8.12ac: ProductVersion: 10.0.14251.1000 12a8.12ac: FileVersion: 10.0.14251.1000 (rs1_release.160124-1059) 12a8.12ac: FileDescription: Windows NT BASE API Client DLL 12a8.12ac: \SystemRoot\System32\KernelBase.dll: 12a8.12ac: CreationTime: 2016-01-25T04:23:03.353803000Z 12a8.12ac: LastWriteTime: 2016-01-25T04:23:03.353803000Z 12a8.12ac: ChangeTime: 2016-01-28T18:40:23.049586900Z 12a8.12ac: FileAttributes: 0x20 12a8.12ac: Size: 0x1ef520 12a8.12ac: NT Headers: 0xf0 12a8.12ac: Timestamp: 0x56a544c9 12a8.12ac: Machine: 0x8664 - amd64 12a8.12ac: Timestamp: 0x56a544c9 12a8.12ac: Image Version: 10.0 12a8.12ac: SizeOfImage: 0x1f2000 (2039808) 12a8.12ac: Resource Dir: 0x1da000 LB 0x540 12a8.12ac: ProductName: Microsoftﾂｮ Windowsﾂｮ Operating System 12a8.12ac: ProductVersion: 10.0.14251.1000 12a8.12ac: FileVersion: 10.0.14251.1000 (rs1_release.160124-1059) 12a8.12ac: FileDescription: Windows NT BASE API Client DLL 12a8.12ac: \SystemRoot\System32\apisetschema.dll: 12a8.12ac: CreationTime: 2016-01-25T04:22:57.775234300Z 12a8.12ac: LastWriteTime: 2016-01-25T04:22:57.775234300Z 12a8.12ac: ChangeTime: 2016-01-28T18:40:19.518330300Z 12a8.12ac: FileAttributes: 0x20 12a8.12ac: Size: 0x16710 12a8.12ac: NT Headers: 0xc0 12a8.12ac: Timestamp: 0x56a54713 12a8.12ac: Machine: 0x8664 - amd64 12a8.12ac: Timestamp: 0x56a54713 12a8.12ac: Image Version: 10.0 12a8.12ac: SizeOfImage: 0x18000 (98304) 12a8.12ac: Resource Dir: 0x17000 LB 0x400 12a8.12ac: ProductName: Microsoftﾂｮ Windowsﾂｮ Operating System 12a8.12ac: ProductVersion: 10.0.14251.1000 12a8.12ac: FileVersion: 10.0.14251.1000 (rs1_release.160124-1059) 12a8.12ac: FileDescription: ApiSet Schema DLL 12a8.12ac: NtOpenDirectoryObject failed on \Driver: 0xc0000022 12a8.12ac: supR3HardenedWinFindAdversaries: 0x0 12a8.12ac: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox' 12a8.12ac: Calling main() 12a8.12ac: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2 12a8.12ac: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox' 12a8.12ac: SUPR3HardenedMain: Respawn #1 12a8.12ac: System32: \Device\HarddiskVolume2\Windows\System32 12a8.12ac: WinSxS: \Device\HarddiskVolume2\Windows\WinSxS 12a8.12ac: KnownDllPath: C:\WINDOWS\system32 12a8.12ac: '\Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe' has no imports 12a8.12ac: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe) 12a8.12ac: supR3HardNtEnableThreadCreation: 12a8.12ac: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff97819c150 pvNtTerminateThread=00007ff978211400 12a8.12ac: supR3HardenedWinDoReSpawn(1): New child 12b0.12b4 [kernel32]. 12a8.12ac: supR3HardNtChildGatherData: PebBaseAddress=00000000002e3000 cbPeb=0x388 12a8.12ac: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ff978170000 uNtDllChildAddr=00007ff978170000 12a8.12ac: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ff97819c150 12a8.12ac: supR3HardenedWinSetupChildInit: Start child. 12a8.12ac: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms. 12a8.12ac: supR3HardNtChildPurify: Startup delay kludge #1/0: 266 ms, 17 sleeps 12a8.12ac: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION 12a8.12ac: *0000000000000000-fffffffffffeffff 0x0001/0x0000 0x0000000 12a8.12ac: *0000000000010000-fffffffffffeffff 0x0004/0x0004 0x0020000 12a8.12ac: *0000000000030000-000000000001afff 0x0002/0x0002 0x0040000 12a8.12ac: 0000000000045000-0000000000039fff 0x0001/0x0000 0x0000000 12a8.12ac: *0000000000050000-fffffffffff53fff 0x0000/0x0004 0x0020000 12a8.12ac: 000000000014c000-0000000000148fff 0x0104/0x0004 0x0020000 12a8.12ac: 000000000014f000-000000000014dfff 0x0004/0x0004 0x0020000 12a8.12ac: *0000000000150000-000000000014bfff 0x0002/0x0002 0x0040000 12a8.12ac: 0000000000154000-0000000000147fff 0x0001/0x0000 0x0000000 12a8.12ac: *0000000000160000-000000000015dfff 0x0004/0x0004 0x0020000 12a8.12ac: 0000000000162000-00000000000c3fff 0x0001/0x0000 0x0000000 12a8.12ac: *0000000000200000-000000000011cfff 0x0000/0x0004 0x0020000 12a8.12ac: 00000000002e3000-00000000002dffff 0x0004/0x0004 0x0020000 12a8.12ac: 00000000002e6000-00000000001cbfff 0x0000/0x0004 0x0020000 12a8.12ac: 0000000000400000-ffffffff8081ffff 0x0001/0x0000 0x0000000 12a8.12ac: *000000007ffe0000-000000007ffdefff 0x0002/0x0002 0x0020000 12a8.12ac: 000000007ffe1000-000000007ffd1fff 0x0000/0x0002 0x0020000 12a8.12ac: 000000007fff0000-ffff800a875bffff 0x0001/0x0000 0x0000000 12a8.12ac: *00007ff678a20000-00007ff6789f4fff 0x0002/0x0002 0x0040000 12a8.12ac: 00007ff678a4b000-00007ff677e15fff 0x0001/0x0000 0x0000000 12a8.12ac: *00007ff679680000-00007ff679680fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679681000-00007ff679687fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679688000-00007ff679688fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679689000-00007ff679689fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff67968a000-00007ff67968afff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff67968b000-00007ff679697fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679698000-00007ff679699fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff67969a000-00007ff6796a2fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff6796a3000-00007ff6796a3fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff6796a4000-00007ff679707fff 0x0020/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679708000-00007ff679708fff 0x0080/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679709000-00007ff679713fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679714000-00007ff679714fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679715000-00007ff679745fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679746000-00007ff679747fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: 00007ff679748000-00007ff679753fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume2\Ztech\programs\Oracle\VirtualBox\VirtualBox.exe 12a8.12ac: Error (rc=-5644): 12a8.12ac: Too many regions for VirtualBox.exe. 12a8.12ac: Error (rc=-5644): 12a8.12ac: supHardenedWinVerifyProcess failed with Unknown Status -5644 (0xffffe9f4): Too many regions for VirtualBox.exe. 12a8.12ac: Error -5644 in supR3HardNtChildPurify! (enmWhat=5) 12a8.12ac: supHardenedWinVerifyProcess failed with Unknown Status -5644 (0xffffe9f4): Too many regions for VirtualBox.exe. 12a8.12ac: supR3HardNtEnableThreadCreation:
I will continue checking forums and bug reports until I find a workaround as I need Virtual Box to run some older programs to help with my java development of some cutting edge software. In the meantime I hope this helps the Oracle team as I used to work at Oracle and want to help.