You can disable background apps in Windows through Settings > Apps > Installed apps, where the "..." menu on each app opens Advanced options with a Background apps permissions dropdown set to "Power optimized (recommended)" by default. That switch only governs packaged Microsoft Store apps. Desktop programs like Steam, Discord, and OneDrive ignore it entirely and need Task Manager's Startup tab, the app's own settings, or a service change. The method you pick has to match the app type, or you'll toggle a switch and watch the process keep running.

That mismatch is where most guides lose people. Microsoft's own support documentation frames the Background apps page as a battery and data saver for Store apps, yet search results promise it will quiet everything. It won't. What follows separates the seven levers by what each one controls, the exact names on screen, and the failure cases that make a toggle look broken.

What the Background Apps Toggle Actually Controls

Windows 11's Background apps page lists only apps installed through the Microsoft Store or shipped as MSIX packages. Open Settings > Apps > Installed apps, and an app with an "Advanced options" link is packaged; a traditional Win32 installer like VLC's desktop build, Chrome, or Steam has no such link. That distinction is the whole ballgame. The toggle exists because packaged apps run under a broker that can suspend them when they're not visible, and Microsoft's default permission, "Power optimized (recommended)," lets the system decide when to pause them rather than blocking them outright.

The list itself is inconsistent in ways that confuse people. Some packaged apps, including many system components, never appear on the Background apps page even though they run in the background. Others appear but resume whenever you launch them manually, which is expected behavior. A user who flips every switch to "Never" and still sees Spotify in Task Manager is usually looking at a desktop install, not a packaged one, or looking at the app while it's open.

Here's the decision rule before you touch anything.

App type Where you see it Background toggle works? Correct lever
Microsoft Store / MSIX app Settings > Apps > Installed apps, has "Advanced options" Yes Background apps permissions
Desktop (Win32) app No "Advanced options" link No App's own settings, Task Manager startup, or service
Windows service Not listed as an app at all No Services console (careful)
Scheduled task Task Scheduler library No Task Scheduler

If you want the fastest real result rather than the prettiest menu, the Startup tab in Task Manager matters more than the Background apps page for everyday slowdowns. Background permission affects whether a packaged app can run when closed; startup approval affects whether anything launches when you sign in. The second one is what most people actually feel.

Method 1: The Per-App Background Permission Switch

This is the sanctioned, reversible method, and it takes about two minutes for a handful of apps. Use it for Store apps you want to keep installed but silent, like a weather app or a news reader. One caveat: the Background apps page moved in recent Windows 11 releases. On 22H2 and later it sits under Settings > Apps > Installed apps with a "Background apps" filter or a separate Advanced app settings entry depending on build, so if you don't see the list at Settings > Apps > Background apps, check Installed apps first.

1: Open Settings with Windows key + I. 2: Go to Apps > Installed apps. 3: Find the app and click the "..." button, then Advanced options. 4: Under "Background apps permissions," open the dropdown. 5: Choose "Never" to block background activity, or leave "Power optimized (recommended)." 6: Repeat per app.

Failure handling: if "Advanced options" is missing, the app is Win32 and this method does not apply β€” move to Method 4 or 5. If the dropdown is greyed out, the app is a system component or is managed by policy; a work or school device with AppLocker or Intune restrictions will lock these settings, and you'll see "Some settings are managed by your organization" at the top of the page. That banner means stop and talk to IT, because registry edits won't stick either.

Microsoft's documentation notes that setting an app to "Never" can stop live tiles and notifications for that app. That's the trade most people accept, but it's a real cost if the app is your mail client or calendar.

Method 2: The Global Background Apps Switch

Windows 11 also offers a single master switch that turns off background permissions for every packaged app at once. It lives on the same Background apps page, labeled "Let apps run in the background," with an On/Off control. Flip it off and every Store app loses background permission in one move. It's the bluntest tool in the box and the one most likely to break something you rely on, like a messaging app's notification delivery.

Before you flip it, know what it doesn't do. It doesn't stop desktop apps, it doesn't stop services, and it doesn't prevent anything from launching at sign-in. It also doesn't survive a reinstall of an app in the sense you'd expect: reinstalling a packaged app can reset its individual permission, though the global switch stays off. If you later turn the global switch back on, individual apps return to "Power optimized," not to whatever you'd set before. That reset behavior trips people up, so note which apps you'd customized.

The real use case for the global switch is a low-power laptop on battery, where you want maximum uptime and don't care about background sync. For a desktop, it's mostly pointless. For a work machine, the managed-by-organization banner may block it. Handle it as a temporary measure: flip it off for a flight, flip it back on at your desk, and accept that you'll re-customize individual apps afterward if you'd set any to "Never."

Method 3: Windows 11's Efficiency Mode for a Specific Process

Efficiency mode is the sleeper feature here. It doesn't block an app from running; it lowers the process's priority and puts it in an efficiency state so Windows schedules it on lower-power cores where available and throttles it when the system is busy. You enable it per process in Task Manager, and it persists across launches for many apps. Right-click a process in the Processes tab and choose "Efficiency mode." The process gets a green leaf icon.

This is the right answer for an app you want available but not hungry β€” a chat client that should stay connected but not chew CPU, or a sync tool that can run slowly. It is not a way to stop an app. Spotify will still stream; it will just use less. The catch is coverage: Efficiency mode availability depends on the app and the Windows build, and some apps opt out or behave oddly, particularly apps that manage their own thread priorities. If a process greys out the option, the app isn't eligible.

One more caveat worth knowing: Efficiency mode settings can reset when the app updates, and Microsoft's documentation has changed the exact behavior across Windows 11 releases. Treat it as a per-session tuning knob you may need to reapply, not a permanent block. It pairs well with Method 1 β€” set background permission to "Never" for apps you want fully silent, and use Efficiency mode for the ones you want alive but polite.

Method 4: Killing Desktop Apps That Ignore the Settings Toggle

For Win32 apps, the honest short-term fix is Task Manager. Open it with Ctrl + Shift + Esc, find the process under Processes, right-click, and choose "End task." That stops it now. It does not stop it from coming back. Steam, Discord, OneDrive, Adobe's Creative Cloud helper, and most game launchers relaunch themselves from a startup entry, a scheduled task, or their own watchdog process, which is why End task feels like Whack-a-Mole.

The durable fix for most of these is inside the app. Steam: Settings > Interface > "Run Steam when my computer starts" off. Discord: User Settings > Windows Settings > "Open Discord" off. OneDrive: right-click the cloud icon > Settings > uncheck "Start OneDrive automatically when I sign in to Windows." Spotify's desktop app has "Open Spotify automatically after you log into the computer" under Settings. Each app names it slightly differently, which is why there's no universal menu.

Use End task for one-off situations β€” a game launcher eating RAM during a video call, an updater that won't quit. Don't use it as your strategy, because the process returns at the next launch trigger and you'll repeat the ritual. If a process refuses to end even as administrator, it's likely protected by a service or running under another user account; check the Details tab for the session and the Services tab for a matching service before you go further.

Method 5: Disabling Startup Entries in Task Manager

Startup approval is the highest-leverage change for most users, and it's the one I'd do first on a slow machine. Task Manager's Startup apps tab (Windows 11) or Startup tab (Windows 10) lists every program registered to launch at sign-in, with an "Impact" rating of Low, Medium, or High that Windows calculates from observed CPU and disk use at startup. Right-click an entry and choose Disable. Nothing is uninstalled; the entry is just skipped.

The impact rating is the practical sorting key. Disable the High items first and reboot, then judge. A word of warning about the ratings: they're historical estimates, not live measurements, and a newly installed app may show "Not measured" until it has run at startup a few times. Also, some entries are intentionally left enabled by the manufacturer β€” audio drivers, touchpad utilities, and fingerprint software often appear here and are worth keeping if you use the hardware feature.

Two failure cases to know. First, disabling a startup entry for a security suite can leave you unprotected or trigger the suite's own tamper protection to re-enable it. Check your antivirus's settings rather than fighting it. Second, Task Manager's Startup tab doesn't show scheduled tasks or services that launch apps, so a disabled entry can still reappear via Task Scheduler. That's the next method.

Method 6: Task Scheduler and Services for Stubborn Launchers

Some apps hide their launch in Task Scheduler, which is why they survive every Startup-tab disable. Open Task Scheduler from the Start menu, click Task Scheduler Library, and scan the middle pane for vendor-named tasks β€” updaters, telemetry jobs, and "run at logon" entries are common. Disabling a task is reversible and doesn't delete it. Be conservative here: Microsoft-signed tasks and tasks labeled with Windows component names are usually doing real maintenance, and disabling the wrong one can break update delivery or disk cleanup.

Services are the last resort and the easiest place to cause damage. Opening Services (services.msc) lets you change a service's startup type to Manual or Disabled. The rule is simple: only touch services whose names clearly belong to a third-party app you installed, and never disable anything you can't identify. Disabling a service can break the app entirely, not just its background behavior, and some services are dependencies for others β€” Windows will warn you if you try to stop a service that other running services need. Set a restore point before you start.

The payoff is real for a specific class of offender: license managers, update brokers, and helper services that respawn the main app. The risk is equally real. A machine that boots to a black screen because a display-related service was disabled is a bad afternoon. If you're unsure, leave services alone and accept the startup-entry fix as the ceiling.

Method 7: Group Policy and Registry on Pro and Enterprise Editions

Windows 11 Pro, Enterprise, and Education expose a policy that can prevent apps from running in the background at the machine level: Computer Configuration > Administrative Templates > Windows Components > App Privacy > "Let Windows apps run in the background," set to "Force Deny." That's the Group Policy Editor (gpedit.msc), which Home edition doesn't include. The same effect is reachable through the registry, but the policy is the cleaner path because it's documented and reversible.

On Home edition, you can set the corresponding registry value under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\BackgroundAccessApplications, but treat registry edits as a last resort: a typo can break sign-in or app launch, and there's no "undo" button. Export the key before you change it. The policy route is also what managed devices use, which explains why some users find the Background apps page greyed out with an organization banner.

The policy has the same limit as the global switch: it governs packaged apps, not Win32 programs or services. It's the right tool for a shared or kiosk-style machine where you want a hard floor on background activity and don't want per-user fiddling. On a single-user laptop, it's overkill compared with Method 1 plus Method 5.

Which Method Fits Which App: A Worked Comparison

Here's the practical mapping, built from the app types above rather than from a menu tour. The columns are the levers, and the cells say whether that lever reaches the app.

App Background permission Global switch Efficiency mode Startup entry App's own setting
Store weather app Yes Yes Yes Sometimes Rarely
Spotify desktop No No Yes Yes Yes
Steam No No Yes Yes Yes
Discord No No Yes Yes Yes
OneDrive No No Yes Yes Yes
Third-party updater service No No No No Services console

The pattern is clear once it's laid out: for Store apps, the Settings page is sufficient; for everything else, you're in the app's own preferences or Task Manager. A reader who only learns the Settings toggle will conclude the feature is broken. A reader who learns the mapping fixes the actual problem in five minutes.

Time cost is worth naming honestly. The per-app Settings walkthrough takes roughly two minutes for three apps. The startup-entry pass takes about five minutes including a reboot to verify. The Task Scheduler and services audit takes twenty minutes or more if you're being careful, which you should be. None of these are one-time costs in the sense of never recurring: app updates can re-add startup entries, and major Windows feature updates can reset some background permissions to default. A quarterly five-minute check keeps a machine quiet.

Failure Cases That Make a Toggle Look Broken

The most common "it didn't work" report is a packaged app you set to "Never" that still shows in Task Manager because you launched it and left it open. Background permission governs what happens when the app is closed or suspended, not what happens while it's on screen. Close the window, don't just minimize it, and check again.

A second failure case is the app that reappears because a second process is launching it. Steam has a bootstrapper and a client process; killing one leaves the other. Discord's updater can relaunch the client after an update. In these cases, the fix is the app's own "start with Windows" setting, not the process kill.

Third, the managed-device banner. If Settings shows "Some settings are managed by your organization," your employer or the device's management profile controls these pages, and local changes will be reverted at the next policy refresh. That's not a bug to work around; it's a boundary. Ask IT.

Fourth, the antivirus tamper-protection case. Security suites often re-enable their own startup entries and services when tamper protection is on, and disabling them can trigger a security alert or leave the machine unprotected. Configure the suite's own settings instead, and keep real-time protection on.

Finally, the update-reset case. Windows feature updates can restore background permissions to default, and app updates can re-add startup entries that you'd disabled. If a machine that was quiet gets chatty after an update, re-run Methods 1 and 5 before assuming something is wrong with Windows itself.

FAQ

Does disabling background apps improve battery life on a laptop?

Yes, but the size depends on which apps you block. Packaged apps that poll for mail or sync data wake the CPU and radio repeatedly, and blocking them measurably reduces idle drain on battery. Desktop apps you actually use β€” a browser, a chat client β€” usually account for more drain than the Store apps the Settings page controls, so pair the toggle with closing what you're not using.

Why does an app still run after I set it to "Never"?

Because the app isn't a packaged Store app, or because it's currently open. Check Settings > Apps > Installed apps for an "Advanced options" link on that app; if it's missing, it's a Win32 program and the permission doesn't apply. Close the app's window fully, then look in Task Manager again before concluding the setting failed.

Is it safe to disable all background apps at once?

It's reversible but disruptive. The global switch stops notifications, live tiles, and background sync for every Store app, including your mail and calendar clients, and it resets individual app permissions when you turn it back on. On a work machine, policy may override it. Use it for a battery-saving session, then restore it.

How do I stop Steam, Discord, or OneDrive from launching at sign-in?

Turn off each app's own "start with Windows" setting: Steam under Settings > Interface, Discord under User Settings > Windows Settings, OneDrive from the cloud icon's Settings dialog. As a backup, disable the matching entry in Task Manager's Startup apps tab. Killing the process in Task Manager stops it once but doesn't prevent the relaunch.

What's the difference between background permission and startup approval?

Background permission controls whether a closed packaged app can run at all; startup approval controls whether a program launches when you sign in. Disabling a startup entry doesn't revoke background permission, and blocking background permission doesn't stop a program that's registered to launch at sign-in. You often need both for a stubborn app.

Can I disable background apps on Windows 11 Home?

Yes, through Settings and Task Manager, but not through Group Policy β€” gpedit.msc isn't included in Home edition. The per-app permission switch, the global switch, Efficiency mode, and startup-entry disabling all work on Home. The registry equivalent of the policy exists but is riskier than the Settings route and unnecessary for a single-user machine.

Do these changes survive Windows updates?

Not reliably. Feature updates can reset background permissions to Microsoft's default "Power optimized," and app updates can re-add startup entries you'd disabled. A quarterly check of Settings and the Startup apps tab takes about five minutes and catches the drift. If a machine gets noisy after a major update, re-run the two quick methods before troubleshooting anything else.

Does blocking background apps break notifications?

For packaged apps set to "Never," yes β€” notifications from that app generally stop, because the app isn't running to generate them. Desktop apps are unaffected by the Settings toggle, so their notifications keep working. If you need an app's alerts, leave it on "Power optimized" and use Efficiency mode instead of blocking it.