Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| No app sends banners or sounds | Check the global Notifications switch and Do Not Disturb |
| Only one app is silent | Enable that app and inspect its own notification settings |
| Alerts appear only after opening the app | Check background activity, battery saver and sign-in state |
| Notifications are present but make no sound | Review banner, sound, volume and Focus settings |
Diagnose notification delivery repair before resetting Windows
Notification problems should be separated from a broken shell panel. Compare Windows + N, app notification permissions, Focus settings, and one known app before treating the entire taskbar or shell as damaged.
Press Windows + N to open Notification Center. If the panel opens but no alerts arrive, focus on notification permissions and app settings rather than the shell button itself.
Record when the problem began and what changed immediately beforehand: a Windows update, display-driver change, new theme, Start-menu replacement, taskbar tweaker, debloat script, security utility, work policy or monitor reconnection. “No app sends banners or sounds” suggests check the global notifications switch and do not disturb, while “Only one app is silent” points toward enable that app and inspect its own notification settings. That timing is stronger evidence than a generic event-log warning.
Restart Explorer only if Notification Center itself will not open or the shell panel is frozen. If the center works, stay focused on app permissions and Focus settings.
Test notifications in another account when practical. If alerts work there, inspect the original profile's notification settings and app registration before system repair.
“Alerts appear only after opening the app” means check background activity, battery saver and sign-in state, while “Notifications are present but make no sound” means review banner, sound, volume and focus settings. Change one layer at a time and retest the same action. Avoid third-party registry cleaners, Start-menu repair packs and commands that re-register every Windows app without a verified reason; broad changes create fresh failures and erase the evidence that identifies the original cause.
If notifications changed after an update, install newer fixes first and check whether Focus, Do not disturb, or organization policy controls notification behavior.
Restore Windows and per-app notification permissions
Open Settings > System > Notifications and enable Notifications. Expand the affected app and allow banners, notification-center entries and sounds as needed. Windows can permit notifications globally while one app remains disabled.
Turn Do Not Disturb off for the test and review automatic rules. Check the current Focus session because it can suppress banners. Use Windows + N to see whether alerts arrived silently in the notification center.
1Create a controlled app test
- Choose one trusted app that can generate a predictable alert.
- Enable its Windows and in-app notification settings.
- Trigger one test and check both the banner and notification center.
2Check sound separately
- Open Volume mixer and confirm System sounds are audible.
- Verify the app's notification sound option.
- Test without Bluetooth audio or a muted external output.
Check app delivery, account and battery boundaries
Open the app and confirm you remain signed in and that its own quiet hours or channel settings allow the alert. Browser notifications also require permission for the individual website; remove unknown site permissions rather than enabling every site.
Battery saver and background restrictions can delay some apps. Change background permission only for the trusted app that needs timely alerts. Do not disable power management globally.
Repair notification center only when it is broken
If Windows + N does not open, use the Quick Settings and notification-center guide boundary: restart Explorer, install updates and test another account. A missing banner with a working center is still an app-delivery problem.
Run DISM then SFC when notifications, Quick Settings and other shell surfaces fail across accounts. Use a clean boot if a focus utility, security suite or shell extension appears to suppress delivery.
Verify the repair before making more changes
Test a trusted test app shows a banner and notification-center entry with the intended sound three ways: with the pointer, with the documented keyboard shortcut and again after a full Restart. Confirm the feature still works after opening several apps and, when relevant, after disconnecting and reconnecting an external display.
Re-enable only the app notification settings, Focus rules, or startup items changed during diagnosis. Avoid resetting unrelated shell features once alerts return.
Technical order checked against Microsoft's current notifications and Do Not Disturb guidance. Device-specific menus and driver availability vary by manufacturer.
Frequently asked questions
Why are notifications in the center but no banner appeared?
Banner display may be disabled, or Do Not Disturb and Focus may have suppressed it.
Why does only one app fail to notify me?
Its Windows permission, in-app setting, account, background delivery or channel may be disabled.
Can Battery saver delay notifications?
It can restrict background activity for some apps; adjust only the trusted affected app when possible.