sodcalculator

10 Tech How-To

Fix Windows Push Notification User Service Stopped Error

Guide 10-49910 · Updated · Step by step

If you’re seeing “Windows Push Notification User Service has stopped working” or notifications simply aren’t appearing, the service that delivers toast alerts from apps like Mail, Calendar, and Microsoft Store has crashed or been disabled. This guide walks you through the most reliable fixes, from restarting the service to repairing system files, so your notifications work again.

What You’ll Need

  • Administrator access to your Windows PC (to change services and run commands).
  • Your Windows account password if prompted by User Account Control.

Step-by-Step

  1. Restart the Push Notification service. Press Win + R, type services.msc, and press Enter. Scroll to Windows Push Notification User Service. Right-click it and choose Restart. If it’s not running, right-click and select Start. Then close the Services window and check if notifications work.
  2. Set the service to Automatic. In the same Services window, double-click Windows Push Notification User Service. Set Startup type to Automatic (not Automatic (Delayed)). Click Apply then OK. This prevents the service from failing to start after a reboot.
  3. Run the Windows Store Apps troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters. Find Windows Store Apps and click Run. Follow the prompts; this tool can fix corrupted app registrations that affect notifications.
  4. Re-register the Windows Store apps. Open PowerShell as administrator (right-click Start and select Windows PowerShell (Admin) or Terminal (Admin)). Run this command and wait for it to finish:
    Get-AppxPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

    This re-registers all built-in apps, which often resolves notification issues. Restart your PC afterward.

  5. Check notification settings per app. Go to Settings > System > Notifications. Make sure Notifications is turned on at the top. Scroll through the list and ensure the apps you want notifications from are enabled. Also check that Focus assist is not set to Alarms only or Priority only during the times you expect notifications.
  6. Run System File Checker and DISM. Open Command Prompt as administrator (right-click Start and choose Command Prompt (Admin) or Terminal (Admin)). Run sfc /scannow and wait for it to complete. Then run DISM /Online /Cleanup-Image /RestoreHealth. This repairs corrupted system files that may be causing the service to crash. Restart your PC after both commands finish.
  7. Create a new user account (if nothing else works). Go to Settings > Accounts > Family & other users. Under Other users, click Add account and follow the prompts to create a new local account. Log into that account and test notifications. If they work, the issue is tied to your original user profile; you can migrate your files and settings.

Common Mistakes

  • Setting the service to Disabled. Some “optimization” guides suggest disabling this service to save resources. That will break notifications entirely. Always keep it set to Automatic.
  • Only restarting the service without setting it to Automatic. If the startup type is still Manual or Disabled, the service may not start after a reboot, and the error returns.
  • Skipping the PowerShell re-registration. This step fixes app-specific registration issues that the troubleshooter sometimes misses.
  • Forgetting to turn on notifications after a Windows update. Updates can reset some settings; always verify the master toggle in Settings.

Tips

  • Use Restart instead of Shut down when troubleshooting. Windows Fast Startup can cause services to behave oddly after a shutdown; a full restart clears that state.
  • If you use a third-party antivirus, temporarily disable its “notification blocking” or “silent mode” to see if it’s interfering.
  • Keep Windows updated. Microsoft frequently fixes service bugs in cumulative updates.
  • If you’re on a corporate or school PC, group policy may disable this service; contact your IT admin.

Troubleshooting

If the error persists after following the steps above:

  • Check the Event Viewer for details. Press Win + R, type eventvwr.msc, and press Enter. Navigate to Windows Logs > System. Look for errors with source WpnUserService or Service Control Manager. The error details may point to a specific DLL or permission issue.
  • Perform a clean boot. Type msconfig in the Start menu and open System Configuration. On the Services tab, check Hide all Microsoft services, then click Disable all. On the Startup tab, click Open Task Manager and disable all startup items. Restart. If notifications work, re-enable services and startup items one by one to find the culprit.
  • Run the Windows Update troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters and run Windows Update. Corrupted update components can break services.
  • Use System Restore. If the error started recently, restore your PC to a point before the issue began. Search for “Create a restore point” in the Start menu, click System Restore, and follow the wizard.
  • As a last resort, reset Windows. Go to Settings > System > Recovery > Reset this PC. Choose Keep my files to reinstall Windows without losing personal data. This will fix any deep system corruption.

Frequently Asked Questions

Why does the Windows Push Notification User Service keep stopping?

It usually stops because of corrupted system files, a misconfigured service startup type, or a conflict with a third-party app. The steps above address each cause.

Will disabling this service improve performance?

No. The service runs in the background and uses negligible resources. Disabling it only breaks notifications and can cause errors in other apps.

Can I fix this without admin rights?

No. Changing service settings and running system commands requires administrator privileges. If you’re on a managed device, contact your IT department.

Does this error affect all apps or just some?

It affects any app that uses Windows toast notifications, including Mail, Calendar, Microsoft Store, and many third-party apps. Some apps have their own in-app notification systems that may still work.

Will these steps delete my apps or files?

No. The steps in this guide do not delete apps or personal files. The PowerShell re-registration only resets app configurations, not data. The reset option in Troubleshooting is the only step that reinstalls Windows, and even then you can choose to keep your files.

How long does the PowerShell command take?

It can take a few minutes, depending on how many apps are installed. Let it run until the prompt returns. It may show red errors for some apps, but that’s normal and doesn’t mean the process failed.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →