ilintar
Just FYI, since it might or might not be a permanent issue - it seems that Windows 10 Build 10049 changed the way network components are identified. There no longer is a "ComponentId" value in the registry, instead the corresponding key is "MatchingDeviceId". This leads to OpenVPN not detecting the TAP Adapter even though it is installed. A workaround is to add the "ComponentId" value to the registry, but it might be a good idea to take this into account for future builds.
kristij
Great this worked for me - however I also had to rename the TAP adapter called "Ethernet" to OpenVPN_Tap and then it worked.
flohdaniel
Hey, i have the Problem with Windows 10, too-
Could you please give us some more details to this registry key, I wasn't able to found the right node in registry Editor to add the missing value.
geekinchief
I'm having this problem. Which registry keys do I need to change? Really appreciate the help!
