WFN V2.0 ALPHA keeps popping up for svchost.exe

Mar 13 at 9:32 AM
Edited Mar 13 at 9:33 AM
VERSIONS USED: WFN v2.0 ALPHA 11 and 12

WFN keeps popping up for Host Process for Windows Services (svchost.exe).

I am using a VPN service that routes traffic through svchost.exe and therefore it keeps popping up at least 6 times per minute. I already allowed more than 400 instances of svchost.exe. See screenshots below.

Image

Image

I found one old thread about the svchost.exe keeping popping up: http://www.ghacks.net/2011/07/28/windows-firewall-notifier/

Also, I tried to manually add svchost.exe and allow the instance, but it keeps popping up and driving me crazy.

Are there more people with this problem or is there a simple trick to fix this?

I get the following log when I press on Allow
\2017-03-13 10:28:56 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017-03-13 10:28:57 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017-03-13 10:28:57 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017-03-13 10:28:57 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017-03-13 10:28:57 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:28:57 - User [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:28:57 - User [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:28:57 - User [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:28:57 - User [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:28:57 - User [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:28:59 - User [True] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017-03-13 10:29:16 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017-03-13 10:29:16 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017-03-13 10:29:16 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017-03-13 10:29:16 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:29:16 - User [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:29:16 - User [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:29:16 - User [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:29:16 - User [False] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/03/13 10:29:19 - User [True] - [INIT] OS: Microsoft Windows NT 6.3.9600.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Users\User\Documents\WFN\ / Version: 2.0.6280.24564 (32 bit)
Developer
Mar 13 at 6:01 PM
Can you try disabling the "Service: DNS Client" checkbox when creating the rule?
Mar 13 at 6:18 PM
Edited Mar 13 at 6:20 PM
I already tried disabling each checkbox one by one, still the same result unfortunately.

Also, the service is not always 'DNS Client'. It is different on each pop-up.
Developer
Mar 14 at 7:08 AM
svchost.exe is hosting a lot of services, and many of these services use a lot of ports. Are you sure you're not simply seeing these dozens of combinations? In other words, do you really get duplicates rules, or are they all for different ports/services/protocols?
Mar 14 at 8:40 AM
Edited Mar 14 at 8:41 AM
Yes, most of them are really duplicates. I opened two random rules from the firewall list and compared them, see the image below.

Image

The 'Application Packages' setting is set to 'Apply to all programs and application packages' and the 'Services' setting is set to 'Apply to all programs and application services'

I even get a pop-up for svchost.exe when I manually add a rule to allow everything from it regarding the protocol or port.
Developer
Mar 14 at 5:54 PM
Hmm, crap, I had hope I'd fixed all of these bugs by now... Can you tell me what VPN software you're using, so I can try to reproduce the issue?
Mar 14 at 9:11 PM
I am using Windscribe. I already tried to completely uninstall with Revo Uninstaller and reinstall the program again, but still the same issue appears. Let me know if I can do more to help fixing the problem.
Mar 23 at 12:52 PM
Is there any news on this issue? I completely removed WFN for a week now because it was driving me crazy with pop-ups every few seconds.
Developer
Mar 26 at 8:43 AM
Edited Mar 26 at 10:11 AM
I think I've managed to track down the issue: WFN isn't handling different network interfaces, and this VPN software installs a new network adapter. This may take some time to implement... :|

Edit: Nope, it's something else altogether. When the VPN activates, traffic starts flowing through it and the used ports are marked as special by the Windows Firewall. Unfortunately, the mechanism used (called "PortsInUse") is poorly documented, and it appears there's not way for WFN to get access to it. This will require someone to reverse engineer this part of Windows. So for now, I'm afraid there's not going to be a solution. :(
Mar 26 at 12:32 PM
Thanks for answering the question and everything you are doing for WFN. I am going to contact Windscribe for this issue, because I don't have any problems with most other VPN providers I tested. So I think it's a combination of both and maybe they can give an answer of how they handle there service.