There is a special frustration in watching your laptop crawl through the first five minutes after boot, only to discover the biggest resource hog is an app you never opened: Microsoft Teams, cheerfully auto-started, consuming RAM like it owns the place. On Windows 11 24H2 the situation got worse — the update re-enabled Teams autostart for users who had painstakingly disabled it, and the new Teams client launches both personal and work flavors for good measure.

Teams is not malware, but its autostart behavior deserves the same treatment: systematic removal across every layer where it registers itself. This guide kills the zombie properly — in-app settings, Windows startup lists, scheduled tasks, and the 24H2-specific re-enablers — plus lighter alternatives for staying reachable. For the full startup audit, see disabling startup programs in Windows 11 ; for general slowness, read speeding up a slow Windows 11 laptop .

Why this happens

  • Electron app with browser-sized footprint: Teams runs a full Chromium runtime, consuming hundreds of MB of RAM and real CPU from launch.
  • Auto-start enabled by default: Installers and updates enable autostart without asking, joining the most congested seconds of boot.
  • Both personal and work clients launching: 24H2 systems often auto-start two separate Teams apps, doubling the cost unknowingly.
  • Updates re-enabling disabled autostart: Feature updates reset Teams’ startup registration, resurrecting what users had killed.
  • Multiple redundant autostart mechanisms: In-app setting, Startup folders, Task Scheduler tasks — disabling one leaves the others.
  • Background activity after launch: Even idle, Teams syncs, checks presence, and renders its UI on timers, holding CPU and network.
  • Chat taskbar integration in 24H2: The built-in Chat/Teams taskbar experience adds another always-on Teams component.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Disable autostart inside Teams itself

The in-app toggle is layer one — and the one most people stop at, which is why Teams returns.

  1. Open Teams > Settings (gear icon) > General and uncheck Auto-start Teams (wording varies slightly between classic and new Teams).
  2. In new Teams, also check Settings > General > Open application in background and On close, keep the application running — disable both if you want it fully gone.
  3. For the built-in Chat (personal Teams): Settings > Apps > Installed apps > Microsoft Teams (personal) > Advanced options — restrict background and login behavior.
  4. Quit Teams completely afterward (system tray > right-click > Quit) — closing the window often just minimizes it.
  5. Reboot and check Task Manager — if Teams still appears, other layers are active; continue below.

Fix 2: Remove Teams from Windows startup lists

Layer two: the OS-level startup registrations.

  1. Open Task Manager > Startup apps and disable every Teams entry — there may be two (personal and work/school).
  2. Go to Settings > Apps > Startup and toggle off all Teams entries there too — Windows 11 maintains this separate list.
  3. Check the Startup folders: Win+R > shell:startup and shell:common startup — delete any Teams shortcuts found.
  4. Reboot and verify in Task Manager > Processes that no Teams.exe exists 5 minutes after login.
  5. If it is still there, the scheduled-task layer is responsible — next fix.

Fix 3: Kill the scheduled tasks that resurrect Teams

Layer three: the updater tasks that re-register autostart on every Teams update.

  1. Open Task Scheduler (taskschd.msc) and look under Task Scheduler Library for Microsoft Teams update tasks.
  2. Also check the Microsoft > Office branch — work/school Teams registers its updaters alongside Office tasks.
  3. Right-click Teams-related update/login tasks and Disable them (do not delete — disabling is reversible).
  4. Note the tradeoff: disabled update tasks mean Teams will not self-update; update it manually from within the app monthly.
  5. Reboot once more — with all three layers disabled, the zombie stays dead.

Fix 4: Handle the 24H2 Chat taskbar integration

24H2’s built-in Chat is a separate Teams-flavored resident from the installed app.

  1. Right-click the taskbar > Taskbar settings and toggle Chat (or Teams Chat) Off if you never use it.
  2. In Settings > Apps > Installed apps, find the built-in Teams/Chat package — uninstall it if your workflow uses only the work client or the browser.
  3. If you keep it, open its settings and disable every auto-start and background option it exposes.
  4. Check Settings > Privacy & security > Background apps for Teams entries and set them to Never.
  5. Confirm the taskbar is Chat-free and no Teams processes run at idle after a reboot.

Fix 5: Replace always-on Teams with on-demand habits

Stay reachable without paying the permanent resident cost.

  1. Use Teams on the web (teams.microsoft.com) in your browser for light use — zero autostart, zero background footprint when the tab closes.
  2. Pin Teams to the taskbar or Start for one-click launching when the workday starts — the 10-second manual launch beats the 24/7 tax.
  3. Keep Outlook notifications for meeting invites — the Join button opens Teams exactly when needed.
  4. If your org requires presence status, open Teams at day start and quit it at day end — presence during work hours, silence otherwise.
  5. Measure the difference: boot time and idle RAM before versus after — the numbers usually end the debate. Microsoft documents startup management at Windows support .

Fix 6: Lighten Teams if you must keep it starting

For users whose org mandates auto-start: make the mandatory as cheap as possible.

  1. In Teams Settings > General, enable every efficiency option available (reduced data, hardware acceleration off if it causes issues).
  2. Close Teams to the tray rather than leaving the full window open — the minimized state uses fewer UI resources.
  3. Limit Teams to one client: if both personal and work auto-start, kill the one you never use.
  4. In Settings > Privacy, disable read receipts, link previews, and animated content to cut background rendering.
  5. Schedule a weekly Teams restart — long-running Electron processes accumulate memory cruft; a fresh launch is leaner.

Fix 7: Audit the whole boot for fellow travelers

Teams is rarely alone in the boot stampede. While you are here, fix the rest.

  1. Task Manager > Startup apps, sorted by Startup impact: disable everything High-impact that you do not need in the first minute.
  2. Common companions to evict: chat apps, game launchers, Adobe updaters, cloud tools you rarely touch.
  3. Keep: security software, audio drivers, and manufacturer power/thermal controls.
  4. Time your boot (phone stopwatch, power button to usable desktop) before and after the audit.
  5. A disciplined startup list is the gift that keeps giving — every future boot, every future update, starts clean.

Closing

Teams autostart is death by a thousand cuts — an Electron app’s appetite multiplied across two clients, three autostart layers, and updates that resurrect what you killed. Disable all the layers, not just the obvious one, and the boot stampede loses its biggest participant. Your laptop will thank you every single morning, in the currency of seconds that feel like minutes.

Frequently asked questions

Why does Microsoft Teams slow down my laptop so much?
Teams is built on Electron — essentially a full Chromium browser plus Node.js runtime dedicated to one app — so it consumes hundreds of megabytes of RAM and meaningful CPU from the moment it launches. When set to auto-start, it joins the boot stampede, competing with everything else for disk and CPU during the most congested seconds of startup. On 8 GB machines, Teams alone can account for a tenth or more of total memory before you open anything.
What's the difference between Teams personal and work versions starting up?
Windows 11 24H2 can launch both the consumer Teams (Chat, built into the taskbar) and the work/school Teams client, and many users have both auto-starting without realizing it. They are separate apps with separate autostart toggles in different places — Task Manager Startup, Settings Apps Startup, and inside each app’s own settings. You must disable both if both are present; killing one while the other launches changes nothing.
Will disabling Teams autostart break meetings and notifications?
No — disabling autostart only stops Teams from launching at boot. The app works perfectly when you open it manually, and scheduled meetings still appear in Outlook and open Teams when you click Join. The only thing you lose is instant availability the second you log in, plus background notifications before you first open the app. For most users, opening Teams when the workday starts is a better trade than paying its boot cost daily.
Why does Teams keep re-enabling itself after updates?
Teams has multiple autostart mechanisms that restore each other: the in-app ‘Auto-start Teams’ setting, the Windows Startup apps list, and installer-level tasks that re-register on update. Disabling only one layer lets the others resurrect it — this is the infamous Teams zombie behavior. The permanent fix is disabling all layers: in-app setting, Task Manager Startup, Settings Startup, and the scheduled tasks. Miss one and it comes back.