Support 256 Posted September 24, 2020 Report Share Posted September 24, 2020 Release torguard-v4.1.2, 2020-09-24 =================================== - Windows: solve problems related to the missing "ComponentId" key in registry --This resolved the "outside DNS blocker" error - Windows: adapter cleanup improved in some Windows builds =================================== Downloads 2 Quote Link to post Share on other sites
1 zerotikin 0 Posted September 26, 2020 Report Share Posted September 26, 2020 Problems creating wireguard network adapter W10 64 new version. I can no longer connect via WG only OpenVPN Quote Link to post Share on other sites
0 C.C. 0 Posted September 24, 2020 Report Share Posted September 24, 2020 Sorry I was unable to get back right away in the previous thread about the 2nd test build there, "torguard-setup-v4.1.2-pre.8+g42cdcbe.test" but to confirm things, it seems like that version and this version the final 4.1.2 build, resolve whatever issue became apparent in 4.1.1 based on what was changed in 4.1.1 , and I am now getting a "ComponentID missing, trying MatcfhingDeviceID message" which I am sure is the intent. "Blocking outside DNS" includeCurrentVPN true includeAllVPNs false includeLoopback false includeUp false includeDown false "Adapter[adapterName={redacted},friendlyName=Ethernet,ifType=6,ifIndex=26,ifIndexIPv6=0,staticNameServers=[],componentId=PCI\\VEN_redacted&DEV_redacted&SUBSYS_redacted&REV_redacted]" includeCurrentVPN false includeAllVPNs false includeLoopback false includeUp false includeDown true Adapter rejected ComponentId missing, trying MatchingDeviceId... "Adapter[adapterName={redacted-wg-guid},friendlyName=wg-torguard,ifType=53,ifIndex=18,ifIndexIPv6=0,staticNameServers=[10.9.0.1,10.8.0.1],componentId=wintun]" includeCurrentVPN true includeAllVPNs true includeLoopback false includeUp true includeDown false Adapter has our componentID -> appended to the list -------------------- snip iterates through adapaters repeating above, either rejecting, or using componentID ------------------- Blocking Outside DNS... "{redacted-wg-guid}" "" Blocking IPv4 port 53 (DNS) Blocking IPv6 port 53 (DNS) No VPN executable to allow Allow TAP adapter IPv4 port 53 (DNS) Allow TAP adapter IPv6 port 53 (DNS) includeCurrentVPN true includeAllVPNs false includeLoopback false includeUp false includeDown false Thanks for the hard work Quote Link to post Share on other sites
0 TDog 1 Posted September 30, 2020 Report Share Posted September 30, 2020 WireGuard problem. System works fine with Open VPN. Windows defender has been disabled and no other A/V program on this system. Windows 10 Pro 64 bit v2004 See attached Quote Link to post Share on other sites
Question
Support 256
Release torguard-v4.1.2, 2020-09-24
===================================
- Windows: solve problems related to the missing "ComponentId" key in registry
--This resolved the "outside DNS blocker" error
- Windows: adapter cleanup improved in some Windows builds
===================================
Downloads
Link to post
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.