VirtualBox can't find Virtual adapters for vlans on Windows 7

[cdlt]

VirtualBox 5.1.10 , 5.0 and 4.0 can't find Realtek Virtual adapters on Windows 7. It is not possible install "VirtualBox NDIS6 Bridged Networking Driver" service on these adapters. I need these adapters to communicate vlans with virtual machines. Two realtek physical adapters are used with 7.82.317.2014 driver version. I use Realtek Ethernet Diagnostic utility ver 2.0.2.8 to create virtual adapters over physical adapters.

[cdlt]

I found other way to resolve this problem. I have removed all of the virtual adapters and I uninstall Realtek Ethernet Diagnostic utility. Due the vlan lock by Windows I set the Adapter Settings and setting "Priority & VLAN" to "Priority & VLAN disabled" . This was not enough to resolve the problem. I add windows register values:

The key "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E972­E325­11CE­BFC1­- 08002BE10318}\00nn" needs to have 4 values. ' 00nn' is the specific key that has the information for the adapter you intend on capturing on. Add or edit the following four REG_SZ :

MonitorModeEnabled ‐ 1

MonitorMode ‐ 1

*PriorityVLANTag ‐ 0

SkDisableVlanStrip ‐ 1

Thank you for this reference ​https://ask.wireshark.org/questions/5996/how-to-configure-realtek-pcie-gbe-family-controller-to-capture-vlan-tag-packet/53113

[DmitryDoe]

I was able to install "VirtualBox NDIS6 Bridged Networking Driver" service to "Realtek Virtual Adapter" (VLAN, created with RTL utility) by changing
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00nn\Ndi\Interfaces
LowerRange (REG_SZ) to "ethernet" So I was able to create bridge VM interface with this VLAN interface.

[tetley]

I had the same problem binding the VirtualBox NDIS6 Bridged Networking Driver to the Realtek Virtual Adapter to allow bridging to a VLAN-tagged virtual adapter. The VirtualBox NDIS6 Bridged Networking Driver wasn't an option under Realtek Virtual Adapter properties, and could not be installed as a service.

DimitryDoe's suggestion of setting LowerRange to ethernet worked except I wasn't able to achive this by editing the registry key (this didn't seem to have any effect). Instead, I had to do this by editing the .inf file and reinstalling the driver:

1) Find the directory installed by "Realtek Ethernet Diagnostic Utilty" containing the RtVlan640.inf and RtVlan640.sys files (usually Program Files (x86)\Realtek\Realtek Ethernet Diagnostic Utility\RtVlanPt\WIN10).

2) Copy that directory to a temporary location.

3) Edit RtVlan640.inf and change the line containing:

HKR, Ndi\Interfaces,    LowerRange, 0,  "nolower"

to:

HKR, Ndi\Interfaces,    LowerRange, 0,  "ethernet"

4) Note: to allow the driver to install, the modified driver will either have to be re-signed (look up how to self-sign a driver), or Windows' driver digital signature enforcement will have to be disabled prior to installing the driver. For the latter, it may be necessary to delete the .cat file (containing the now invalid signature) and the reference to the .cat file in the .inf file (i.e. comment out the CatalogFile = RtVlan640.cat line by prepending a ;).

5) Reinstall the 'fixed' driver: Realtek Virtual Adapter > Properties > Configure > Driver > Update Driver. Then "Browse my computer for drivers" and "Let me pick from a list of available drivers on my computer" and "Have Disk" and select the temporary directory containing the modified driver.

6) After reinstalling the driver, VirtualBox NDIS6 Bridged Networking Driver can now be bound to the Realtek Virtual Adapter. The fact that this works suggests it's a Realtek driver problem rather than a VirtualBox problem.

Tested with these software versions:

Windows 10 Version 10.0.19043 Build 19043; VirtualBox 6.1.32; Realtek Drivers version 10.56; Realtek Diagnostic Program 2.0.72 (providing Realtek Virtual Adapter Driver 10.4.1117.2020 dated 2020-11-17)