WFN cant remember system/svchost

[stavae]

Versions

WFN:     2.0.6636.29380
Win10
Version: 1803
Build:   17134.407

WFN keeps opening notifications for system/svchost (only appears to be happening when my VPN is enabled).

[geotavros]

Not sure if related but I had a similar issue on Win7 x64. The problem was that WFN created a rule with a "wildcard" path to svhost.exe. It was something like %WINDIR%\System32\svhost.exe, when I changed path to be absolute, it fixed the problem. C:\Windows\System32\svhost.exe

[stavae]

Not sure if related but I had a similar issue on Win7 x64. The problem was that WFN created a rule with a "wildcard" path to svhost.exe. It was something like %WINDIR%\System32\svhost.exe, when I changed path to be absolute, it fixed the problem. C:\Windows\System32\svhost.exe

Apparently the rule paths are already absolute (and changing them to relative doesnt work either)

[PaulCordo]

Same here

[indivisible-irl]

I'm running in to the same issue and it's getting quite frustrating since the popups (constantly) steal focus from other (fullscreen) apps interrupting me.
Defaulting to block and getting notifications for DNS requests from svchost.exe every few minutes. No combination of toggled choices (specific or ANY) in the notification remembers the whitelisted rule or, future traffic never matches the created rule(s).

Trying to edit the created rules manually via "windows firewall with advanced security" prompts with the following warning. Related?

Edit: v2.0.6636.29380 on Win 8.1

[AtlasHackert]

I've recently noticed (after updating to the latest version of Windows 10) that it doesn't work for me anymore either. I manually made rules, but they didn't work either: it seems the service-part of firewall rules doesn't work for svchost anymore.

My guess would be that some change done by Microsoft to svchost causes the service-part of the rule to always mismatch for svchost. You'll have to use all-or-nothing (i.e., without specifying a service) rules for svchost, and perhaps complain to Microsoft about this annoying change.

[tcf1]

I'm chiming in that i never had this issue previously, but i did a fresh install of Windows 10 20H2 instead of my previous method of constant updating, and now on Beta 2.5.370.9 AMD 64 i'm getting constant notifications for SYSTEM i cannot accept regardless of which settings i tick in advanced rules

[wokhan]

Hi, thanks for telling, as a work-around you should be able to create the rule manually (using the Windows firewall console), but of course this will have to be investigated!

[tcf1]

Interestingly (or maybe not if i'm showing my ignorance) but deleting the rules created by WFN and creating a single manual rule did fix this problem for me and i'm working well now with BETA 2, thanks.