Windows 10 Build 10049 - registry structure changed
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
Forum rules
Please report your experience with testing branch. Include what you were using and how
If there is a problem, the more info the better!
Please report your experience with testing branch. Include what you were using and how
If there is a problem, the more info the better!
-
- OpenVpn Newbie
- Posts: 1
- Joined: Thu Apr 02, 2015 4:38 pm
Windows 10 Build 10049 - registry structure changed
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.
-
- OpenVpn Newbie
- Posts: 1
- Joined: Fri Apr 03, 2015 1:48 pm
Re: Windows 10 Build 10049 - registry structure changed
Great this worked for me - however I also had to rename the TAP adapter called "Ethernet" to OpenVPN_Tap and then it worked.
-
- OpenVpn Newbie
- Posts: 2
- Joined: Sun Apr 05, 2015 11:02 am
Re: Windows 10 Build 10049 - registry structure changed
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.
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.
-
- OpenVpn Newbie
- Posts: 1
- Joined: Sun Apr 12, 2015 2:43 pm
Re: Windows 10 Build 10049 - registry structure changed
I'm having this problem. Which registry keys do I need to change? Really appreciate the help!