Your laptop is ‘idle’ — no apps open — yet the fan hums, the battery drains, and Task Manager shows dozens of processes busy. That’s background apps: programs Windows lets run tasks, sync data, and push notifications while you’re not looking. A few are useful. Most are just spending your battery and CPU on updates you’ll never see.
Windows 11 changed how background permissions work compared to Windows 10 — the old global ’let apps run in the background’ toggle is gone, replaced by per-app settings plus battery-based controls. That makes cleanup slightly more fiddly but also more precise: you can silence the freeloaders while keeping your email and messenger live.
Below are three methods, from the simple per-app switches to the set-and-forget policy block. If startup programs (a different thing — apps launching at login) are your bigger problem, see our guide to fixing slow app launches which covers those.
Why this happens
- Default-allowed Store apps — Fresh Windows 11 installs grant background permission to dozens of inbox apps — news, weather, games, Clipchamp — most of which you’ll never open, let alone need live.
- Manufacturer utilities phoning home — Dell, HP, and Lenovo utilities run background tasks for update checks, telemetry, and ‘optimization’ scans that wake the system regularly.
- Chat and Teams integrations — Windows 11’s Teams Chat integration and other messaging apps maintain persistent background connections — constant, low-level CPU and network activity.
- Cloud sync clients — OneDrive, Dropbox, and Google Drive sync engines run continuously, watching the file system and uploading changes — legitimate but costly on battery.
- Browser background processes — Chrome and Edge keep background processes alive for notifications and updates even with no window open, unless configured otherwise.
- Gaming overlays and launchers — Steam, Epic, Discord, and GeForce Experience all run background services for updates, friends lists, and overlays — pure overhead when you’re working.
- Windows features you don’t use — Widgets board refreshes, Phone Link syncing, and search highlights all run background work for features many users never touch.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Method 1: Per-app background settings (precise)
The built-in, supported way — best for most people.
- Open Settings > Apps > Installed apps.
- Click the ⋯ next to an app > Advanced options.
- Under Background apps permissions, change Let this app run in background from ‘Power optimized’ to Never.
- Work through the list: set Never for games, media apps, manufacturer bloatware, and anything you open manually. Leave Power optimized (or Always) for email, messaging, and cloud sync you rely on.
Fix 2: Method 2: Task Manager startup + background cleanup
Background apps and startup apps are different — handle both.
- Open Task Manager (Ctrl + Shift + Esc) > Startup apps — Disable updaters, launchers, and chat apps you don’t need at login.
- In Processes, sort by CPU and Power usage columns to spot the busiest background dwellers — match them to apps you can restrict in Method 1.
- For Store apps specifically, Settings > System > Power & battery > Battery usage shows per-app drain — the worst offenders go on your Never list.
- Restart and compare: idle CPU in Task Manager should sit near 0-2% with nothing open.
Fix 3: Method 3: Group Policy block (durable, Pro only)
The set-and-forget option that survives updates and app reinstalls.
- Press Win + R, type
gpedit.msc, and go to Computer Configuration > Administrative Templates > Windows Components > App Privacy. - Open Let Windows apps run in the background, set it to Enabled, then choose Deny in the dropdown — this blocks background activity for all Store apps.
- For finer control, the per-app settings in Method 1 still work alongside; the policy is the backstop.
- Windows 11 Home users: the equivalent is a registry value, but per-app settings (Method 1) are safer and sufficient — skip the registry unless you manage multiple machines.
Fix 4: Calm the big-ticket background consumers
A few specific apps deserve individual attention beyond the generic switches.
- Widgets: right-click taskbar > Taskbar settings > toggle Widgets off — or see our widgets.exe CPU fix if it’s burning CPU.
- Phone Link: if you never use it, Settings > Bluetooth & devices > Phone Link > turn it off.
- Teams Chat: Settings > Apps > Installed apps > Microsoft Teams > Advanced options > background Never (unless you live in Teams).
- OneDrive: right-click tray icon > Pause syncing during battery-critical work; or Settings > Account > Choose folders to shrink what’s watched.
Fix 5: Tame browser background activity
Browsers are the sneakiest background residents.
- Chrome: Settings > System > disable Continue running background apps when Google Chrome is closed.
- Edge: Settings > System and performance > disable Continue running background extensions and apps when Microsoft Edge is closed.
- In both, review On startup pages — ‘Continue where you left off’ with 40 tabs is a background workload disguised as a convenience.
- These two toggles alone reclaim meaningful idle CPU on many laptops.
Fix 6: Audit gaming and utility background services
Launchers and RGB tools don’t need to run 24/7.
- Open
services.mscand set game-launcher and RGB/fan-control services you rarely need to Manual instead of Automatic — they start when you open the app. - In each launcher (Steam, Epic, Discord): Settings > disable Run on startup / Start minimized options.
- Keep security software and hardware-monitoring services on Automatic — don’t touch those.
- The goal: when you’re working, only work-related background activity runs.
Closing
Background apps are death by a thousand cuts — no single one matters, but thirty of them do. Twenty minutes with the per-app settings, the two browser toggles, and a pass through startup entries buys you quieter fans, a cooler lap, and real battery life back. Revisit after each feature update; Windows has a habit of re-inviting guests you uninvited. Microsoft’s Windows support hub documents the background-app permission model if you want the official reference.
