Solution:
Root Cause: Windows Push Notification Service (WpnUserService) Database Corruption
All notification registration tokens, push channels, and toast queues are managed by the per-user
WpnUserService. The service stores data in a local SQLite database (
wpndatabase.db). File corruption in this database—caused by ungraceful shutdowns or disk write collisions—causes the entire Push Notification Framework to freeze in a silent fail-safe state where no toasts or log items can process.
# Diagnostic Verification:
Inspect Event Viewer under Applications and Services Logs > Microsoft > Windows > PushNotifications-Platform > Operational for Event ID 1008 or 1012 indicating database read/write faults.# Step-by-Step Fix:
1. Identify Active WpnUserService Instance Name:
Open Admin PowerShell and find the exact service instance: powershell
$svc = Get-Service -Name "WpnUserService*"
Write-Output $svc.Name
2. Stop WpnUserService and Windows Push Notifications System Service:
Stop the service using elevated permissions: powershell
Stop-Service -Name $svc.Name -Force
Stop-Service -Name "WpnService" -Force -ErrorAction SilentlyContinue
3. Rename/Purge Corrupted
wpndatabase.db File:
Execute the following command string: powershell
$DbDir = "$env:LOCALAPPDATA\Microsoft\Windows\Notifications"
Rename-Item -Path "$DbDir\wpndatabase.db" -NewName "wpndatabase.db.bak" -Force
4. Restart Push Notification Services:
Restart the services to force Windows to rebuild a clean database schema: powershell
Start-Service -Name $svc.Name
5. Reboot the computer to re-register active application push channels.
# Prevention & Long-Term Monitoring:
Maintain clean shutdown procedures and run regular disk checks (chkdsk) to ensure file integrity in local AppData repositories.