Newest TAP9 driver shows as Unknown adapter

[klepp0906]

So i'm a torguard user. They're still installing 9.0.0.21 with their client. I was informed of the newest driver and updated it manually through device manager.

Everything works, apart from some differences such as interface metric which can be manually changed etc.

One thing I cant figure out how to "set right" is the adapter type so to speak.

If I do a ipconfig /all with the torguard installed adapter - it returns "Ethernet adapter Ethernet 3"
The Ethernet 3 portion is inconsequential as I know that can be changed.

the newly updated/current win10 driver however comes up as "Unknown adapter Local Area Connection" (and oddly enough gives it an interface metric higher (lower) than my actual physical connection.

How do i get "Unknown adapter " to become "Ethernet adapter "?

I had assumed it was something in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces but the few things I was willing to toy with, seemed to have no effect.

Hoping someone with a bit less rudimentary experience can set me right!

[ramondeklein]

I noticed that the newer TAP adapters register with a different ComponentId in the registry. Our company uses a custom-developed VPN solution that uses the TAP-adapter and we also had issues with later versions of the TAP adapter. Our software looked for TAP-adapters that are registered with ComponentId with value tap0901, but later versions of the TAP adapter register with root\tap0901. These were not found, so it's not recognized by the software.

You can check the HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318} in the registry and iterate your adapters. You'll probably notice that your newer TAP-adapters use root\tap0901 instead of tap0901 in the ComponentId.

See also commit OpenVPN/tap-windows6@a9fb4a3.