Windows 11 notifications going silent — missed Teams pings, Outlook emails never popping up, mobile-style banners not appearing, the Action Center showing nothing despite obvious activity — almost always traces to one of four causes: Focus Assist quietly enabled, app-specific permissions toggled off, the notification system service in a stuck state, or a Group Policy block on managed machines. For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.
Quick orient: open Settings → System → Notifications. The top-level “Notifications” toggle must be On. Under it, each app appears with its own toggle. If the master switch is off, nothing notifies — anywhere. If the master is on but the app you’re missing alerts from is individually off, that app is silenced specifically. Most “no notifications” reports resolve at this exact page.
Focus Assist — the silent culprit
Focus Assist (renamed “Focus” or “Do not disturb” in newer Windows 11 builds) suppresses notifications during specified hours, while gaming, or when duplicating displays. It enables itself automatically based on rules you may not remember setting. The result: notifications appear in Action Center quietly, no banner, no sound.
Check it: Settings → System → Focus → see if any automatic rules are active. Common defaults that catch people out:
- “When duplicating my display” → silenced during presentations and projector use
- “For the first hour after a Windows feature update” → silenced after big updates
- “When I’m playing a game” → silenced during full-screen apps Windows thinks are games
- “During these hours” (sometimes set during initial Windows setup) → silenced at scheduled times
Disable any rules you don’t actually want. Or check the right side of the taskbar clock — if there’s a moon icon next to it, Do Not Disturb is on right now. Click the clock → toggle Focus / Do Not Disturb off → notifications resume immediately.
App-specific notification settings
Sometimes Windows allows notifications globally but the app itself has them disabled internally. Two layers can suppress alerts — Windows or the app — and each needs to be checked.
For Teams: Teams → profile picture → Settings → Notifications → confirm “Messages” and “Mentions” are set to “Banner and feed” or at least “Banner.” If set to “Off” inside Teams, Windows-side settings can’t override it.
For Outlook: File → Options → Mail → Message arrival section → “Display a Desktop Alert” must be checked.
For Slack: Slack → Preferences → Notifications → confirm desktop notifications are on for the channels you care about.
For Chrome and Edge browser notifications: per-site permissions matter. chrome://settings/content/notifications → confirm the site is “Allowed” and not “Blocked.” Many users accidentally block notifications when the browser asks the first time.
Restart the notification service
Windows has a background service that handles notification delivery. When it gets stuck, notifications stop appearing even though everything looks correctly configured. A service restart costs nothing and often fixes the issue:
- Win+R →
services.msc - Find “Windows Push Notifications System Service” → right-click → Restart
- Also find “Windows Push Notifications User Service” → restart
- Test by triggering a notification (send yourself an email; ask someone to message you)
If notifications start working again: the service was stuck. Possible long-term fix: confirm both services are set to “Automatic” startup (right-click → Properties → Startup type). Manual or Disabled means they don’t always come up at boot.
Action Center isn’t accumulating notifications
If you click the Action Center icon (or the clock area in Windows 11) and it’s always empty even though apps should be sending notifications: notifications aren’t reaching the Action Center either. This is different from “I missed the popup but it’s still in Action Center” — this is total loss.
Usually traces to one of:
- Background app permissions denied — Settings → Apps → “Installed apps” → find the app → Advanced options → “Background apps permissions” → set to “Always” or “Power optimized,” not “Never”
- The “Show notifications in the action center” option is off for the app — Settings → System → Notifications → click the app name (not just the toggle) → uncheck “Hide content when notifications are at top of screen” and check “Show in action center”
- Notification time-out cleared old notifications — they appeared briefly then auto-cleared
Our guide on Windows 11 freezing and stability covers the broader background service issues that sometimes cause notifications to fail alongside other features, and our Microsoft Teams troubleshooting covers the Teams-specific notification configuration. For broader notification policy and developer-side notification handling, Microsoft’s Windows 11 notification documentation covers the system-level architecture in detail.
Banner vs sound vs Action Center — three separate signals
Windows 11 notifications have three independent components. Each can be enabled or disabled separately, and users sometimes don’t realise they’re separate things:
| Component | What it does | Setting location |
| Banner | Pop-up on screen briefly | App-level “Show notification banners” |
| Sound | Audible chime when notification arrives | App-level “Play a sound when a notification arrives” |
| Action Center entry | Persistent notification in Action Center | App-level “Show notifications in action center” |
You might have one of these working and another not. “I see notifications in Action Center but never hear or see them when they arrive” = sound and banner off, Action Center entries on. “I hear the sound but the banner doesn’t pop up” = sound on, banner off. Each is configured per-app in Settings → System → Notifications → click the app name (not just its toggle) → see the three separate options.
Volume mixer affecting notification sound
Windows 11 has per-app volume controls. If Notifications has been muted in Volume Mixer, sounds don’t play even with everything else enabled.
Right-click speaker icon → Open Volume Mixer → look for “Notifications” or “System sounds” entry → confirm it’s not muted (no red X on the speaker icon) and the slider is up. Some applications create their own entries in Volume Mixer; if you’ve ever muted Teams or Outlook here specifically, their notification sounds remain muted.
This is one of the easiest things to miss because nothing in Settings indicates it. Volume Mixer is a separate layer beyond app and system notification settings.
Notifications not appearing on lock screen
The lock screen has its own notification visibility settings, separate from the desktop. Settings → System → Notifications → scroll to “Additional settings” (or further options depending on Windows build) → “Show notifications on the lock screen” must be on for any to appear.
Per-app: Settings → System → Notifications → click the app → “Show notification banners on the lock screen” toggle. Some apps don’t allow lock screen notifications at all (banking apps, messaging apps with privacy modes); that’s a per-app design choice and not changeable through Windows.
Background apps and battery saver
Background app permissions affect whether apps can deliver notifications when not actively in focus. Battery saver mode also blocks background activity for non-essential apps, which can silently kill notifications for those apps.
Settings → System → Power & battery → confirm Battery saver isn’t currently on. Lower threshold or change to “Never automatically turn on” if you want notifications to keep working at low battery.
For specific app background activity: Settings → Apps → Installed apps → find the app → click → Advanced options → Background apps permissions. “Always” is most reliable but uses more battery. “Power optimized” lets Windows decide. “Never” disables background activity entirely — and with it, most push notifications.
Browser push notifications specifically
Chrome, Edge, and Firefox push notifications work through Windows’ notification system. If they stop working while regular Windows app notifications work fine, the issue is browser-specific.
Chrome: chrome://settings/content/notifications → confirm “Sites can ask to send notifications” is on, and confirm the specific site isn’t in the “Blocked” list. Sometimes users accidentally block notifications when the browser prompt appears and they were too quick on the decline button.
Edge: edge://settings/content/notifications → same checks.
Browser notifications also need the browser to be running (at least in the background) to deliver. Chrome typically keeps a background process running even when closed (chrome://settings/system → “Continue running background apps when Google Chrome is closed”). If you’ve disabled that, no notifications when Chrome is closed.
| Problem | Most likely cause | Try first |
| No notifications anywhere | Focus Assist active or master toggle off | Click clock → toggle Focus off; check master notification toggle |
| Specific app silent | App-level toggle off or app’s own settings | Settings → Notifications → app → check all three components |
| Banner appears, no sound | Sound disabled per-app or in Volume Mixer | Per-app “Play sound” check; Volume Mixer entry |
| Action Center always empty | Notification service stuck | Restart Windows Push Notifications service |
| Browser notifications missing | Site blocked or browser not in background | chrome://settings/content/notifications |
| Notifications stopped after update | Service or registry state changed | Restart notification services; reset specific app’s notification settings |
The first checks (Focus state, master toggle, app-level toggle) catch the vast majority of cases. The service restart catches the trickier “everything looks right but nothing works” scenarios. Deeper interventions (Group Policy on managed machines, background app permissions, Volume Mixer per-app mute) only apply to specific situations.
Group Policy on managed machines
On work or school computers, IT often configures notification behaviour through Group Policy. Symptoms: notification settings show “Some settings are managed by your organization” — you can’t change them locally.
Open gpedit.msc (Pro/Enterprise editions only) → User Configuration → Administrative Templates → Start Menu and Taskbar → Notifications → look for any enabled policies that disable notifications. If you find any: that’s the constraint. Cannot be changed locally on a managed device; speak to IT if you need the policy adjusted for a legitimate reason.
For domain-joined Home edition machines (uncommon but possible): Group Policy isn’t accessible directly, but the underlying registry entries are. Check HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsExplorer for “DisableNotificationCenter” values — but don’t modify these on a managed device, talk to IT.
When the notification database is corrupted
Windows stores notification state in a database that occasionally corrupts after botched updates or improper shutdowns. Symptoms: notifications stop appearing system-wide, services run fine, Settings look correct.
Reset the database:
- Stop the Windows Push Notifications services (services.msc → stop both User Service and System Service)
- Win+R →
%localappdata%MicrosoftWindowsNotifications - Rename the entire folder to “Notifications.old”
- Restart Windows
- Windows recreates the notification database from scratch on first login
You lose notification history (the persistent entries in Action Center from before the reset), but notifications resume normally afterward. Use this when standard fixes haven’t worked and notifications are stubbornly broken.
PowerShell quick-fix command
Sometimes Windows’ notification system needs the UWP framework re-registered to recover. Open PowerShell as Administrator and run:
Get-AppxPackage Microsoft.Windows.ShellExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}This re-registers the ShellExperienceHost package which handles the Action Center and notification rendering. Restart after running. If notifications were broken because of a corrupted ShellExperienceHost state (common after a botched update), this often restores them.
Don’t run this casually — it’s a deeper system intervention. But it’s safer than reinstalling Windows, and effective for specific notification-related corruption.
Per-priority notification handling
Windows 11 Focus modes let you customise which notifications break through during focused work. For instance: in Focus, allow only Teams calls and Outlook from specific senders, block everything else.
Settings → System → Focus → “Customize priority list” → add specific apps that should always notify, and specific people (for messaging apps that support contact-level priority) who can interrupt. Useful for reducing distraction without missing genuinely urgent things.
If notifications you expect aren’t appearing during Focus: confirm the originating app/person is in the priority list. Otherwise they’re silenced by design, not broken.
For most users, the practical resolution path goes: check the clock for a moon icon (Focus on?), check Settings → System → Notifications for master and app toggles, check the specific app’s own notification preferences, restart the notification service. Those four checks cover 90% of cases in under 5 minutes. The deeper interventions (database reset, PowerShell re-registration, Group Policy investigation) only matter when standard fixes haven’t worked, and most users never need them.
One small tip worth knowing: if you need a quick “everything urgent should reach me” mode, configure Focus with a priority list of just your essential apps (Teams, Outlook, phone calling) and toggle Focus on. Now only those things break through. When you’re done with focused work, toggle Focus off and everything resumes normally. More effective than disabling notifications entirely while staying productive.
A small environmental note: if you’ve been having notification problems specifically when using multiple monitors, Windows 11 sometimes routes notifications to whichever monitor has the most recent active window, which can be the one you’re not looking at. Settings → System → Notifications → look for any “Show notifications on” or display-related options. On most builds the option doesn’t exist (notifications always appear on the primary display), but on some it does. If you have a separate display set as primary that you don’t usually look at, change the primary display assignment (Settings → System → Display → click the monitor you actually use → “Make this my main display”). Notifications then appear where you’re already looking. Our guide on Windows 11 System Restore Not Working covers an adjacent issue.
