VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one...?

[jmar83_the2nd]

Hi there

Environment:

- Windows 10 Pro x64 with most current updates on 2021-01-05
- VirtualBox 6.1.97 (but the problem is NOT because of that test (TPM-supporting) version... is was also occured before)

Screenshots here:

1.)

1.jpg (22.85 KiB) Viewed 5515 times

2.)

2.JPG (45.03 KiB) Viewed 5515 times

3.)

3.JPG (110.11 KiB) Viewed 5515 times

Why that? And: How to solve that issue?

Thank you very much for your feedbacks...

[jmar83_the2nd]

https://stackoverflow.com/questions/320 ... -windows-1

Result:

4.JPG (84.2 KiB) Viewed 5512 times

[jmar83_the2nd]

When i search Windows registry for the word "Adapter #2", there also nothing will be found...

[jmar83_the2nd]

Oh no, i was wrong - now i've found the adapter #2 in windows registry.

So: Can i remove that key safely!?

5.jpg (86.12 KiB) Viewed 5495 times

[jmar83_the2nd]

Key is:

HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\NetworkDriverBackup\Control\NetworkSetup2\Interfaces\{7B79BDC3-B168-4137-8F2E-9C8B665F6EF7}\Kernel

[jmar83_the2nd]

That's strange, the key i've found with the word is HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\NetworkDriverBackup\Control\NetworkSetup2\Interfaces\{7B79BDC3-B168-4137-8F2E-9C8B665F6EF7}\Kernel and it's accessible...

BUT: When i read https://stackoverflow.com/questions/320 ... -windows-1 i should be able to access

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces\...
instead of:
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\NetworkDriverBackup\Control\NetworkSetup2\Interfaces\...

[jmar83_the2nd]

-> https://github.com/jschicht/RunAsTI/issues/10

[jmar83_the2nd]

Output of VBoxManage.exe list bridgedifs:

Code: Select all

Name:            Hyper-V Virtual Ethernet Adapter
GUID:            ddd8f4ff-8bf2-42c9-8e67-db53b7e54b48
DHCP:            Disabled
IPAddress:       192.168.1.21
NetworkMask:     255.255.255.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 90:1b:0e:26:d8:2d
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-Hyper-V Virtual Ethernet Adapter

Name:            VirtualBox Host-Only Ethernet Adapter #2
GUID:            7b79bdc3-b168-4137-8f2e-9c8b665f6ef7
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-VirtualBox Host-Only Ethernet Adapter #2

Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            7707ce60-996c-4ac0-839f-7e6a1f1a1545
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-VirtualBox Host-Only Ethernet Adapter

Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            d7bd4982-fd34-4bf2-8bd5-c4173ffc5436
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-VirtualBox Host-Only Ethernet Adapter

Name:            Hyper-V Virtual Ethernet Adapter #2
GUID:            a74038f9-0d09-4b8b-9f74-777fdcd0f9db
DHCP:            Disabled
IPAddress:       198.18.0.254
NetworkMask:     255.254.0.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 90:1b:0e:0b:cc:03
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-Hyper-V Virtual Ethernet Adapter #2

Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            15cc1c56-e74b-439c-bf9a-5cc4bb667bb1
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-VirtualBox Host-Only Ethernet Adapter

[jmar83_the2nd]

-> If you need more informations, so please don't hesitate to ask me for... thx...

[mpack]

This is normal behaviour on Windows. When you do an feature update it will copy all the NICs. I'm sure it's a bug, but its a bug in Windows that affects all the NICs on that PC, and that Windows bug has existed for years.

Go into device manager, show hidden devices, and delete the devices you don't need any more. It may also be possible to rename them - Google for that.

[jmar83_the2nd]

"Go into device manager, show hidden devices, and delete the devices you don't need any more. It may also be possible to rename them - Google for that."


OK,, thx... but, the thing is: : There are not other devices than 1 virtualbox host-only adapter - but not the one with ´#2´ in its name.

Here, the windows device manager screenshot again:

3.JPG (110.11 KiB) Viewed 5472 times

You can CLEARLY see that there is only one (1) VirtualBox host only adapter - the "good" one (without #2), not the "bad" one (with #2)

[jmar83_the2nd]

-> And the "show hidden devices" options is also activated in menu...

[jmar83_the2nd]

-> https://github.com/jschicht/RunAsTI/issues/10

Got it!!

[jmar83_the2nd]

OK - so now it has CLEARLY shown that VirtualBox ist NOT ABLE to handle that issue correctly (maybe on uninstall or whereever, but that's the developer's task).

SO: Where to submit that bug?

Thank you for your feedbacks!

[scottgus1]

This "bug" is caused by Windows OS updating behavior, not by Virtualbox.

You can post a Bugtracker ticket. But this may need to be solved by Windows, not Virtualbox.

This has happened before, though I don't remember how it was resolved. Try some web-searching.