Windows says 1 notification for me ... but there are none

margrave55 said:

I finally found my fix.
From the command line I can run sc query state= all
If I search the results for these two strings: WpnService and WpnUserService_.
... I get two names: WpnService and WpnUserService_7e8d2
The name of the latter one will vary from time to time. In this case the suffix is 7e8d2. Next time it might be different.

Anyway ... if I run these four commands, all is well again.
net stop WpnService
net start WpnService
net stop WpnUserService_7e8d2
net start WpnUserService_7e8d2

Since I run Cygwin (a Linux emulator), I wrapped up all of that into a script:

Code:

for item in WpnService WpnUserService_
do
  service_name=$(sc query state= all | d2u | grep "$item" | grep "^SERVICE" | sed -e "s/.*: //")
  echo "$service_name"
  echo "y" | net stop  "$service_name"
  echo "y" | net start "$service_name"
done
exit 0

I've been chasing this issue for months. Your narrowing it down to these services is the 1st solution that worked for me margrave55. Specifically it's the WpnUserService_xxxxx service that keeps stopping on me. Running the command you posted to start it got notifications working again, at least for the moment. After 4 to 6 hours of the system running, it stopped again.

I opened services.msc and found the WpnUserService_xxxxx / 'Windows Push Notifications User Service_xxxxx' startup type set to 'Manual' and the service was stopped. I see for my Home version 1803 it should be set to Automatic. So I set startup set to 'Automatic', started it, and waited. After a number of hours I found the service had stopped again. The Action Center icon had gone white in that time, indicating new notifications. But again, it didn't list any notifications when opened.

Have you found the issue was permanently fixed for you margrave55? Any suggestions on how I could resolve the issue permanently?

I've just been leaving the services.msc settings menu open, and when notifications don't appear I open 'Windows Push Notifications User Service_xxxxx' settings and start the service again. I see people who've gotten the 1809 update are having the same problem. So if it's something MS can fix, they'll likely have to issue a newer build.

Notifications stop for me at least once a day. My system is on 24/7. The 1st indication of problems is when I see the thumbnail for MS News on the Start Menu stop cycling animated images. Rebooting fixes both. But restarting the service only fixes notifications.

Is there somewhere we can report this issue to MS?

margrave55 said:

It happened again yesterday. I fixed it yet again by running that script.
Fortunately this problem only appears once every week or so.

Win10 just updated to v1809 build 17763.194 tonight. Previous to this I might go a day without having to restart the service, or have to restart it a couple times a day. I don't see any reference to a build number in this other thread about problems with 1809. Maybe someone can tell me if it was not the build17763.194 I got tonight that people were having problems with.

The 1st thing I'll notice if it hasn't fixed my problems will be seeing the animated News app icon on the start menu not revolving.