

Navigate to the following location on your computer by opening the Windows Explorer and clicking on This PC:Ĭ:\Users\YOURUSERNAME\AppData\Local\Microsoft\Windows.In the System Configuration window, navigate to the Boot tab to the right and check the box next to the Safe Boot Click OK and restart your computer in order to boot into Safe Mode.Use the Windows + R key combination on your keyboard in order to start the Run dialog box and type in “ msconfig” before clicking OK. This method is valid for all versions of Windows.It will be recreated automatically and the problem should seize to appear! You can recreate a new database simply by renaming or deleting the Notifications folder on your computer in Safe Mode.
#4shadow stuck notifications event windows 10
Users who have used this method successfully in order to resolve their occurrence of this problem reported that they believe that the Notifications database (wpndatabase.db) became corrupted after the last Windows 10 update. Solution 2: Rename or Delete the Notifications Folder in Safe Mode Try to restart your computer and check to see if the Windows Push Notification User Service continues to crash on your computer.Wait for the “Operation completed successfully” message or something similar to know that the method worked. Type in the following commands in the window and make sure you press Enter after typing each one.Type in “ cmd” in the dialog box which appears and use the Ctrl + Shift + Enter key combination for admin Command Prompt. Additionally, you can also use the Windows Logo Key + R key combination in order to bring up the Run dialog box.Right-click the first entry which will pop up as a search result and select the “Run as administrator” context menu entry. Search for “ Command Prompt” by typing it either right in the Start menu or by pressing the search button right next to it.Follow the steps below in order to do so! It will scan your system files for errors and possible repair or replace them. These problems are rooted deep inside the system files and the only way to try to resolve them is by running the System File Checker (SFC). It has been reported that the Windows Push Notification User Service sometimes causes huge memory leaks which result in massive memory consumption and, ultimately, crashes of the service. Solution 1: Use SFC to Scan for Memory Leaks Avast Antivirus’ Do Not Disturb component – The Do Not Disturb component of Avast prevents users from receiving notifications but it causes this problem even if it’s not turned on.Users have reported that deleting it will cause Windows to recreate it which resolves the problem. Notifications database is corrupt – Notifications database is a file located on your computer which may have gone corrupt and which may cause the service to crash.Make sure you replace these files using the SFC scanner. Memory leaks caused by the service – Huge memory leaks appear as a result of missing or corrupt system files used by the service.
