-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
toaster does not work on Windows 10 version 1709 #206
Comments
The same, I rolled back to the previous version of 1703 |
Running SnoreToast.exe directly from command line works very fine on 1709 but |
I can confirm. I just updated Windows and no more notifications :( |
I had a similar problem, solved with anthonyraymond comment |
Could you please be more specific in what I need to do to fix it? |
I am using,
Works for me if I use 'Custompath' to 'toast' instead of 'SnoreToast'. Here is the code
|
By running SnoreToast manually then setting |
Hi, I am using SnoreToast in a simple compiled batch file. After 1709, my exe never returned to my code after the SnoreToast request. The problem was resolved by stopping passing over appid. My previous code was: snoretoast -t "NAS %nasname%" -m "Shared storage mapped to drive %drive%" -appid MapNAS -p ls-wxl.png -w Now I am using: snoretoast -t "NAS %nasname%" -m "Shared storage mapped to drive %drive%" -p ls-wxl.png -w The appid in the toast message appears as SnoreToast (previously MapNAS). |
This should work as expected now. Reopen if any issue |
I tested the node-notifier on following environment using
npm run example:windows
command.However, a toast never shows up. When I test it on older version of Windows, it works perfectly.
Any others have the same issue?
The text was updated successfully, but these errors were encountered: