DEV Community: Amathlai Softs

Windows 11 notifications silently stopped working? It's a known bug — and "reset Windows" isn't the only fix

Amathlai Softs — Fri, 19 Jun 2026 17:08:55 +0000

If your Windows 11 notifications have quietly stopped working — no toast popups, or a sound plays but no banner, or the Action Center stays empty even though the little count badge keeps climbing — you're not imagining it, and it's almost certainly not something you misconfigured.

It's a known Windows 11 bug. And Microsoft's official answer to it is worse than the bug itself.

The symptom

It usually shows up like this:

The notification count badge keeps ticking up, but no banner ever actually pops.
You open the Action Center expecting a backlog — and it's empty, or stale.
A sound might still play, so you know something came in. You just never get to see it.
Apps swear they sent the notification. Windows swears everything is fine.

The worst part is what you don't notice: the message from your bank, the calendar reminder, the "your driver is arriving" — they arrived, and you never saw them.

It's not your settings

The first thing everyone does is dig through Settings. Notifications are on. Focus Assist / Do Not Disturb is off. The app is allowed. You run the built-in Notifications Troubleshooter and it cheerfully reports "everything is configured correctly."

So you toggle things off and on, maybe reinstall an app, maybe poke at Group Policy. Nothing sticks — because the problem isn't in any of those switches. It's a known intermittent fault in Windows 11 (22H2 and later) that tends to show up after sleep/wake cycles. Microsoft has acknowledged it. There just isn't a Settings page that addresses it.

Why "just restart" only buys you a few days

Rebooting brings notifications back — for a while. That's why most advice online stops there: "restart your PC."

But a restart doesn't address what actually went wrong; it only resets things for a bit. A few days later — usually after the next time the laptop sleeps and wakes — they silently die again. People end up rebooting every few days just to keep notifications working, never quite sure what they missed in between.

A reboot is a band-aid, not a cure.

Microsoft's official fix is nuclear

Follow the support path to the end and here's where it lands: "you may need to reset Windows or create a new user profile."

Read that again. The official remedy for "my notifications stopped popping" is to reset your PC or abandon your user account — reinstall your programs, reconfigure everything, move your files to a brand-new profile. For most people that's hours of work and real risk, to fix something that was never their fault.

That's the gap I wanted to close.

The fix that doesn't blow up your PC

I built a small Windows utility called WNF (Windows Notification Fixer) that repairs the underlying problem directly — no reset, no new profile, nothing of yours touched. You run it, notifications start working again, and that's the whole experience: one click, it just works.

The part I'm proudest of is that you only deal with it once. WNF can run quietly on a schedule, so if the bug tries to come back after a sleep/wake, it's already handled — usually before you'd ever notice a notification went missing. No more reboot roulette, no more wondering what you didn't see.

One click — notifications back, nothing else disturbed
Optional automatic schedule, so it never silently breaks again
Plain activity log so you can see exactly when it ran
Code-signed, runs on Windows 10 and 11, free trial

Disclosure: I'm the author. https://amathlai.com/windows-notification-fixer.html

As far as I've found, it's the only tool that actually targets this specific failure — most "fix Windows notifications" guides just walk you back through the same Settings toggles that didn't work the first time.

TL;DR

Windows 11 (22H2+) has a known bug where the notification count climbs but nothing ever pops and the Action Center stays empty — often after sleep/wake.
It's not your settings; the built-in Troubleshooter even reports everything is fine.
A restart fixes it only until the next time — so people reboot over and over.
Microsoft's official escalation is to reset Windows or make a new user profile — nuclear, for a notification bug.
WNF fixes the actual problem in one click, with an optional schedule so it stays fixed. https://amathlai.com/windows-notification-fixer.html

The 5-layer Windows shell customization system Microsoft hides from Settings

Amathlai Softs — Fri, 19 Jun 2026 16:19:10 +0000

Open File Explorer. Right-click any file. Count the menu items you actually use.

Now count the ones you don't recognize.

That second number is usually 10 to 30 — and it's the visible tip of a much larger customization system that Windows keeps out of Settings entirely. There's no Settings page for what's in your right-click menu. None for which app owns your file thumbnails. None that lists File Explorer's sidebar entries. The system is real, it's powerful, and it's almost completely invisible.

After years of digging through it, I've found it breaks down into 5 layers.

The 5 layers

When you install a Windows app, it can wire itself into your shell across up to five layers — and most apps touch three or four of them without ever telling you:

Right-click verbs — the entries that appear when you right-click a file, folder, drive, or empty space. Each surface is separate, which is why the same app can show up in one menu and not another.
File-type behaviors — thumbnails, the preview pane, the metadata columns in Details view, and whether Search can look inside a file. All per-extension, all owned by whichever app claimed them last.
Sidebar / namespace entries — the items in File Explorer's left rail (OneDrive, This PC, Network, the "Linux" entry WSL adds). Each is a registered extension, not a folder.
Dispatchers — the routing tables Windows checks when something happens: what opens a mailto: link, which apps appear under "Open With", what fires when you insert a USB stick.
Suppressors — the hidden layer that can hide any of the above even when it's correctly installed. This is the one almost nobody knows exists.

Settings exposes maybe 5% of layer 1 and essentially nothing from layers 2 through 5.

Layer 1 — the right-click menu is a merge, not a list

The menu you see isn't stored in one place. Windows builds it on the fly by merging entries from many separate surfaces — all-files, folders, the empty space inside a folder, drives, and per-file-type rules — and then layers per-user overrides on top of machine-wide ones. Windows 11 added a second, newer kind of entry on top of that (the reason "Show more options" exists at all).

The practical upshot: an entry you want gone can be defined in a place you'd never think to look, and a per-user rule can quietly override a system one.

Layer 2 — why one file type loses its thumbnails

Ever had thumbnails break for exactly one format — HEIC, RAW, DWG — while everything else is fine? That's this layer. Each file type points at the app responsible for its thumbnail, its preview, its indexing. When an app is removed but its claim isn't, the pointer dangles and the thumbnail dies. There's no Settings screen that tells you which app owns .heic previews versus .raw.

Layer 3 — the sidebar is extensions, not folders

Every item in Explorer's left rail is a registered namespace extension, not a real folder. That's why you can't just "delete" OneDrive from the sidebar the way you'd delete a folder — and why removing it cleanly is a documented hassle Microsoft handles through group policy rather than a simple button.

Layer 4 — the menus full of dead apps

Open your "Open With" menu. Odds are it lists apps you uninstalled long ago. That's because Windows assembles that list from several independent sources, and most uninstallers clean only one of them. The same pattern explains AutoPlay popups for hardware you no longer own, and default-app handlers that point nowhere.

Layer 5 — the hidden hand

This is the surprising one. An entry can be correctly installed in layers 1–3 and still not appear, because a separate suppression layer can hide it shell-wide. So "I removed OneDrive from File Explorer" can mean five different things depending on which layer actually did the work — and if two layers disagree, you get the classic "I deleted it but it's still there" (or the reverse).

The 15-overlay cap nobody warns you about

One concrete favorite. Those little badges on icons — the OneDrive green check, Dropbox's arrows, Git status marks — are "icon overlay" handlers, and Windows hard-caps the number it will display at 15. They're loaded in alphabetical order, and anything past the 15th is silently dropped.

Install OneDrive, Dropbox, Box, and Google Drive and they eat most of the slots. Git's badges sort later in the alphabet, fall off the end, and vanish — with no error, no warning, nothing. The popular "rename your handlers with leading spaces so they sort first" trick works only until the next update rewrites the entries. The real fix is to turn off the overlays you don't use so the cap stops mattering.

Why a 5-year-old Windows install is full of junk

Each app wires into several of these layers on install. On uninstall, it deletes its program files and a key or two — but leaves the shell wiring behind, because that wiring was added by a different mechanism than the uninstaller knows about. Multiply by every app you've ever installed and a mature Windows install is carrying hundreds of dead shell entries pointing at files that no longer exist. They don't crash anything — Windows just skips the broken ones — but they slow Explorer down and clutter every menu.

The tool

You can see all of this yourself if you know every place to look — but the places aren't documented in one spot, and there's no Microsoft tool that shows the whole picture at once.

So I built one. Kontext scans more than 40 shell-component locations across all three registry hives at once and lays them out in one searchable list — with icons and, for the apps it recognizes, real names instead of raw identifiers, so you can finally tell what each entry actually is. Flip anything off with a checkbox; every change is backed up the instant before it's applied, and one click restores it exactly as it was — including bringing back entries you turned off earlier.

Disclosure: I'm the author. It's code-signed, runs on Windows 10/11 (x64), and has a free trial. https://amathlai.com/kontext.html

It isn't the only context-menu editor out there — ShellExView, ContextMenuManager and others exist — but as far as I've found, it's the only one that covers all five layers instead of just the right-click subset.

TL;DR

Windows shell customization is a 5-layer system, and Settings shows about 5% of it.
The right-click menu is merged live from many sources — that's why entries hide in unexpected places.
Icon overlays silently cap at 15; extra ones just disappear.
A hidden suppression layer can override everything else.
Uninstallers leave most of their shell wiring behind, which is why old Windows installs feel cluttered.