Windows 11 notifications not working? Test the delivery path

Define what “not working” means

Windows can show a notification as a banner, save it in Notification Center, play a sound, display an app badge, or do some of those without the others. A missing banner is not the same as a notification that never arrived.

Pick one recent example and write down the app, expected time, account, device state, and what you expected to see. Keep message text, email addresses, calendar subjects, one-time codes, and customer data out of screenshots.

• In Notification Center, but no banner: keep the check with display settings, Do Not Disturb, Focus, or the app’s banner choice.
• Banner appears without sound: check the app’s sound choice and the current audio output.
• One app is missing: test that app’s Windows and in-app notification settings.
• Every app is missing: inspect Windows notification delivery, Do Not Disturb, Focus, and policy.
• Alerts arrive late: save the sent and received times and whether the app was open, closed, or sleeping.

Run one controlled notification test

Use a harmless event you can trigger and recognize. For example, send a message to a test account you control or create a calendar reminder with no private details. Keep the computer awake, connected, and unlocked. Note the exact send time.

Wait for the app’s normal delivery window, then press Windows key + N to open Notification Center. Do not change settings between sending and checking. The result tells you whether Windows received the notification but displayed it differently, or whether the event never reached the notification list.

Repeat the test once after each change. A settings window opening successfully is not the outcome. The outcome is that a new test notification arrives in the intended place at the intended time.

Check the main switch and the app switch

Open Settings > System > Notifications. Confirm that Notifications is on. Then find the affected app in “Notifications from apps and other senders.” Select it rather than changing every app.

Microsoft’s current Windows guidance separates the app’s notification switch from choices such as showing banners, showing notifications in Notification Center, playing a sound, and setting priority. Turn on only the parts you actually want. If the alert was already in Notification Center, focus on the banner and priority choices rather than toggling the main switch repeatedly.

If the app is not listed, open the app normally and confirm that it is the installed version and account you expect. Some apps do not register with Windows until they have run and requested notification permission. Use the app maker’s current instructions rather than adding a registry entry by hand.

Check Do Not Disturb

In Settings > System > Notifications, inspect Do Not Disturb. When it is on, Windows can send notifications directly to Notification Center instead of interrupting you with banners. That can look like a delivery failure even though the alert arrived.

Turn Do Not Disturb off for one controlled test if you are allowed to do so. Then review “Turn on do not disturb automatically.” Microsoft documents automatic rules for certain times, duplicating a display, playing a game, using an app full screen, and the first hour after a Windows feature update. The exact options shown can vary by Windows build.

If alerts disappear only during one of those conditions, adjust that rule rather than disabling all quiet-time protection. Keep a schedule that prevents interruptions when you need it.

Finish or pause an active Focus session

Windows Focus sessions automatically turn on Do Not Disturb by default and can hide flashing or badges on taskbar apps. Open Notification Center with Windows key + N and look for an active Focus timer, or open Settings > System > Focus.

End or pause the session for one test. If the banner returns, review the Focus choices for Do Not Disturb, taskbar badges, and flashing. Do not remove a useful Focus setup when a single option explains the behavior.

Compare one app with another

Use a second app you already trust and that normally sends notifications. Trigger one harmless event in each app under the same Windows state. Keep Do Not Disturb and Focus unchanged during the comparison.

• Only one app fails: the likely scope is that app, its account, its own notification setting, or its connection.
• Both reach Notification Center but neither shows a banner: keep the scope with Windows display rules, Do Not Disturb, or Focus.
• No app reaches Notification Center: widen the check to the main Windows switch, policy, Windows state, and account.
• The app shows an alert only while open: save that state; background delivery or the app’s own behavior may be involved.

Do not install an unfamiliar app just to create a second notification. A built-in or already trusted app is enough.

Check the app’s own settings and account

Many apps have a second notification layer. An email app may let you choose accounts or folders. A chat app may mute one conversation, workspace, or quiet schedule. A browser may control each website separately.

Confirm the signed-in account and the narrowest relevant in-app setting. Save the current state before changing it. If the app says notifications are enabled but Windows does not list the app, check the publisher’s current support page and update path.

For Outlook specifically, Microsoft’s current support flow checks both Windows notification settings and Outlook’s in-app choices. That does not make an Outlook-only problem a Windows-wide failure.

Restart the smallest affected scope

Close and reopen the affected app, then trigger a new harmless notification. If one app was the only failure, do this before restarting Windows. If every app was affected, save open work and restart the PC once.

After restart, do not use an old notification as proof. Create a new test and confirm the banner, Notification Center entry, sound, or badge you actually need. If the problem returns later, note the time and what changed before it returned.

Install current supported updates carefully

Check Settings > Windows Update for the update state and restart requirement. Also check the affected app’s normal update source. Keep the PC on reliable power, save work, and let an update complete.

Record the Windows edition, version, and build from winver, the app version, and the update history before and after. An update being present near the start of a problem is useful timing evidence, but it does not prove the update caused the failure.

Do not use a third-party driver updater or uninstall unrelated security updates to test notifications.

Know when policy or account state controls the result

On a managed work or school PC, an administrator can control notification behavior, app installation, background activity, and account access. If a setting is greyed out, says it is managed, or changes back after sign-in, save that exact message and contact the administrator.

Also check whether the app itself is online and signed in. A mail, calendar, chat, or browser service cannot alert you about an event it never received. Compare the same account on the service’s trusted website without exposing private content.

Do not delete the notification database as a first fix

Forum instructions sometimes recommend deleting system folders, editing registry keys, re-registering packages, or running broad repair commands. Those steps can erase useful state and create a second problem. Microsoft’s current consumer notification guidance starts with settings, Do Not Disturb, Focus, and app-specific checks.

If the controlled tests show that no application can deliver to Notification Center even after a normal restart and supported updates, preserve the evidence and escalate. A repair should match the confirmed Windows build and failure scope.

Build a useful evidence card

• Windows edition, version, and full build from winver
• affected app, app version, and account type
• expected time and actual arrival time
• whether the alert appears in Notification Center
• banner, sound, badge, and priority settings
• Do Not Disturb state and automatic rules
• Focus state and relevant Focus choices
• one-app versus all-app comparison
• app restart, Windows restart, and update results
• managed-setting or policy messages

Where OmniMend fits

OmniMend 2.0.2 for Windows can help keep the Windows build, affected scope, settings checked, recent changes, and before-and-after notification tests together. It does not read private messages, send a real notification on an app’s behalf, change organization policy, bypass account controls, delete the notification database, or guarantee delivery.

Review what OmniMend can and cannot inspect, use the help center, or browse the evidence-first guide library. Keep message text, email addresses, tenant names, one-time codes, private calendar details, and unredacted logs out of anything you share.