This project has moved. For the latest updates, please go here.
1
Vote

No notifications on Win10 (Alpha12)

description

First of all, thank you for this awesome tool. I've been using it for years and it worked flawlessly. Recently I got a new laptop with W10 (creators update). WFN starts fine, schedules its task, but never ever fires a notification (block & prompt mode). If I test the notification or run Notifier.exe, the demo notification pops up all right. I probably tried all the combinations in settings, I tried running the app as admin, I tried reinstalling a few times and I see the processes in task manager.

It just won't prompt.

Here are a few lines from the log file (same line every second, nothing else):

2017/05/11 16:36:10 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 10.0.15063.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Program Files\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/05/11 16:36:11 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 10.0.15063.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Program Files\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/05/11 16:36:12 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 10.0.15063.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Program Files\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/05/11 16:36:13 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 10.0.15063.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Program Files\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/05/11 16:36:13 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 10.0.15063.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Program Files\WFN\ / Version: 2.0.6280.24564 (32 bit)
2017/05/11 16:36:14 - SYSTEM [False] - [INIT] OS: Microsoft Windows NT 10.0.15063.0 (64 bit) / .Net CLR: 4.0.30319.42000 / Path: C:\Program Files\WFN\ / Version: 2.0.6280.24564 (32 bit)


Let me know if I can help you with resolving this issue. Thanks again for your great work!

Michal

comments

DanielPharos wrote May 15 at 5:28 PM

There's probably a rule somewhere that WFN is misinterpreting to mean "block all", causing the Notifier to not pop-up. I wouldn't be surprised if this is a rule that's supposed to only be applied to Apps, a known issue in the current version of WFN.

I have some code in the works that should let WFN deal with such rules properly; I'll re-respond to this ticket when I release that in a new version of WFN. (Won't be long now!)

elendir wrote May 18 at 9:53 AM

Thanks for your response. I don't know if it helps, but I manually selected and removed all firewall rules using native Win firewall UI, problem prevails. Thanks again!

Michal

Domush wrote May 18 at 7:42 PM

The reason it's messing up with notifications is because the app doesn't support spaces in directory names.

If you run the app from a directory off the root it works as intended

DanielPharos wrote May 19 at 7:07 AM

The reason it's messing up with notifications is because the app doesn't support spaces in directory names.
Owww, that's a very stupid bug (that I probably introduced myself). I'll get that fixed ASAP!

wrote May 19 at 7:08 AM

DanielPharos wrote Sat at 8:57 AM

I have just released a new version of WFN, with the space-in-path bug fixed![https://wfn.codeplex.com/releases/view/631360]

Thank you Domush for figuring out what the problem was!

@Michal: Can you please test this new release, and let me know if this fixes the problems for you? (You may have to (re-)install the new WFN by running DisableWFN.cmd and re-activating WFN through WFN.exe.)

elendir wrote Mon at 8:24 AM

Hi Daniel, thanks for the quick update! Domush was right, if I copy WFN to non-whitespace folder, it works. This applies even to the newest Beta build - the issue is still there if I run it from "Program files" folder.

So I'm running it from C:\wfn at the moment, everything's fine and I'm ok with the solution. But if I can help you with some more testing, I'm available, just let me know.

Thank you!

Michal

DanielPharos wrote Mon at 4:37 PM

Ah, "Program Files"... Currently, WFN needs to be able to write to its folder (mainly for the log-file), so running it from the Program Files folder doesn't work too well. The fix in this newest beta build should at least let WFN work properly from a folder containing spaces, but where it also has writing permission. Fixing running from Program Files is still on the to-do list...