How to Turn Off Windows Notifications on One PC or a Whole Fleet

Turning off Windows notifications takes about four seconds on one machine. Doing it across a client estate, and having it stay off, is a different job with three failure modes that the Settings screen never mentions. This guide covers both: the fast local answer first, then Group Policy, the registry and Intune, then the part where the notifications come back and you find out why. It also covers the two switches you should leave alone, because one of them quietly breaks your own remote wipe.

TL;DR

• One machine. Settings > System > Notifications, then toggle Notifications off.
• One app. Same screen, scroll to the app list, toggle just that app.
• A fleet. Group Policy "Turn off toast notifications" under Start Menu and Taskbar > Notifications, or the same value pushed through Intune.
• It came back. Windows system features ignore that policy, and per-user keys never reach a new profile.
• Leave on. Defender alerts, BitLocker prompts, and WNS.

What "Windows Notifications" Means Before You Start Switching Things Off

"Notifications" is six different subsystems sharing one word, each with its own switch. Turning off the one you found first is why people end up back on the same search a week later.

Sort out which of these the user is complaining about before you touch anything. A technician who kills toasts when the complaint was about Start menu account nags has changed nothing the user can see.

Turn Off Windows Notifications on One Machine

Settings > System > Notifications, then switch Notifications off at the top. That stops banners and sounds for every app at once, on both Windows 10 and Windows 11.

Two adjacent controls are worth knowing on the same screen. Do Not Disturb (called Focus Assist on older builds) suppresses notifications on a schedule or during full-screen apps while leaving them enabled underneath, which is the better answer when someone wants quiet during meetings rather than silence forever. And the expandable section at the bottom, labelled "Additional settings" in Windows 11, is where the Windows tips, suggestions and welcome-experience checkboxes live. Those three are a separate source of popups from anything an app produces, and they survive the master toggle.

Turn Off Notifications for a Single App

Same screen, scroll past the master toggle to the app list, and switch off the one app. Click the app name rather than the toggle and you get finer control: banners off but Notification Center entries kept, sounds off but banners kept, and a priority setting that decides where it sits in the panel.

This is usually the better fix for a support ticket. The complaint is nearly always one chatty app, and blanket-disabling notifications on a work machine means the user stops seeing Teams calls and Outlook reminders too. Fix the app that is causing the problem and leave the rest working.

Turn Off Windows Notifications Across a Fleet

Here is where the consumer guides stop and the work starts. Three delivery methods, same underlying values.

Group Policy

All of these sit under Start Menu and Taskbar > Notifications, and every one is documented in the ADMX_WPN policy reference on Microsoft Learn.

Read the Scope column before you build the GPO, because it is the thing that breaks fleet deployments. Only the first policy exists at machine level. Everything else is User Configuration, which means it applies to the user account, not the computer, and a new profile on that same machine starts with defaults.

Removing the Notification Center itself

Separate policy, separate key, and a much blunter instrument. Start Menu and Taskbar > Remove Notifications and Action Center takes away the panel behind the clock, so notifications stop being collected anywhere the user can reach. It writes DisableNotificationCenter to Software\Policies\Microsoft\Windows\Explorer and needs an Explorer restart to show.

Use it on kiosks, shared terminals and shop-floor machines where the panel is a distraction with nothing useful in it. On a normal work machine it is the wrong tool, because toasts still fire and now there is nowhere to go back and read the one the user missed.

Registry

The values above land in SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\PushNotifications, under HKLM or HKCU depending on the scope. Set the DWORD to 1 to enable the policy, which turns the notifications off. Account notifications are the exception and live in their own key, SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\AccountNotifications.

As a script, the machine-scope version is three lines:

powershell
$key = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\PushNotifications'
New-Item -Path $key -Force | Out-Null
New-ItemProperty -Path $key -Name 'NoToastApplicationNotification' -PropertyType DWord -Value 1 -Force

Pushing that through your RMM is how this usually gets done on machines that were never joined to a domain. Just push to the right hive. A script that writes the User Configuration values to HKLM runs cleanly, reports success, and changes nothing, which is the single most common way this job gets marked complete without working.

Intune

These are ADMX-backed policies, so they appear in the Settings Catalog under Start Menu and Taskbar. Filter on "notification" and the same names come up. For anything the catalog doesn't surface, the OMA-URI is ./User/Vendor/MSFT/Policy/Config/ADMX_WPN/NoToastNotification for the user scope, or ./Device/... for the machine scope on the one policy that supports it. ADMX-backed policies need the SyncML chr data type rather than a plain integer, which is the usual reason a custom profile reports success and does nothing.

How to Confirm the Policy Applied

Three checks, in the order that finds problems fastest.

Read the value back on the endpoint with reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\PushNotifications" /v NoToastApplicationNotification, swapping the hive for HKCU on the user-scope policies. If the value is missing, the delivery failed and nothing downstream matters.

Run gpresult /h report.html and open it to see whether the GPO reached the machine, and whether something else overrode it. On Intune, the equivalent is the per-setting status on the configuration profile rather than the profile's overall state, because a profile can report Succeeded while one setting inside it failed.

Then check the Settings screen. A correctly applied policy greys out the master toggle and shows the managed-by-organisation note. A toggle the user can still move means the policy is not in force on that account, whatever the console says.

Why Notifications Come Back After You Turn Them Off

Three reasons, and Microsoft documents the first one itself.

System features ignore the toast policy. The official note on "Turn off toast notifications" says plainly that Windows system features aren't affected and must be disabled individually. So Windows Update restart prompts, Defender alerts, storage warnings and setup nags keep arriving on a machine where a technician has set every notification policy to Enabled. Nothing is broken. The policy never covered them.

Per-user keys don't reach new profiles. Four of the five policies above are User Configuration. Reimage a machine, add a second user, or hand the laptop to a new starter, and the new profile gets Windows defaults. If the setting has to survive a profile change, it needs to come from Group Policy or Intune targeting the user, not a one-time registry write on the machine.

New apps default to on. The per-app toggles are per-app. Install something new and it arrives switched on, which is why the master toggle or the toast policy is the durable answer and a tidy-up of the app list is not.

What You Should Leave Switched On

Two of these switches cost more than they save on a managed fleet.

Notifications network usage. This one turns off the connection to the Windows Push Notification Service, and Microsoft's own documentation carries a warning about it: the policy "may cause some MDM processes to break," naming remote wipe, unenroll, remote find and mandatory app installation as the tasks that stop working. Those are the actions you need on the day a laptop goes missing. Disabling WNS to stop a user seeing Facebook popups is a trade nobody would take if the cost were written on the same screen as the toggle, and it isn't.

Security and integrity prompts. Defender threat alerts, BitLocker recovery-key prompts and update-restart warnings all arrive as notifications. A blanket "turn everything off" build makes a compromised machine look exactly like a clean one to the person sitting in front of it, and your first sign of trouble becomes the ticket that gets raised three days later. If notifications are being disabled as a standard image setting, keep these alerts and take the noise somewhere your team watches instead, which is the argument for routing endpoint alerts through an RMM rather than a user's taskbar. What the user doesn't need to see, your security stack still does.

What to Do Next

For one complaining user, fix the one app. For a build image, set "Turn off toast notifications" at machine scope, handle the tips and suggestions checkboxes separately, and leave WNS alone.

Then check the thing everyone skips: log in as a fresh user on a machine you have already configured and see what shows up. That is the test that catches a per-user policy sitting in the wrong hive, and it takes two minutes now rather than a ticket in six weeks. If you are standardising this across client estates, it belongs in the same place as the rest of your baseline, alongside patch policy and update rings.