How to Stop Microsoft Teams From Slowing Down Your Laptop at Startup

You press the power button, log in, and then… wait. And wait. The desktop appears but nothing responds, the fan spins up, and eventually Microsoft Teams pops open — an app you didn’t ask to launch, consuming resources you need for actual work. Teams auto-start is one of the most common startup slowdowns on Windows 11 laptops, especially work machines where it was preinstalled.

Teams is heavy: the desktop client bundles an entire browser engine, syncs conversations, checks calendar, and preloads calling infrastructure. Having it fight for CPU and RAM during the critical first minutes after login is a recipe for a sluggish morning. Here’s how to stop it properly — in all the places it hides — and what to do if it keeps coming back.

Why this happens

• Teams registered as a startup app: The installer adds itself to Windows startup, launching at every login.
• Heavy Electron-based client: Teams loads a full Chromium runtime, using hundreds of MB RAM before you even use it.
• Sign-in and sync storm: At launch it authenticates, syncs chats/files, and checks for updates simultaneously.
• Startup contention: Teams competes with antivirus, OneDrive, and other startup apps for disk and CPU.
• Re-enables after updates: Teams installers routinely re-add the startup entry during updates.
• Preinstalled by IT policy: Work laptops may have Teams forced on via group policy or provisioning.
• Background processes linger: Even closed, Teams leaves update and notification helpers running.

How to fix it

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

Fix 1: Disable auto-start inside Teams

Start with the app’s own setting — it’s the most direct.

1. Open Microsoft Teams and sign in if needed.
2. Click the three dots (…) next to your profile picture (top-right) > Settings > General.
3. Uncheck Auto-start Teams. In the new Teams client, this is under Settings > General > Application > Auto-start Teams.
4. Also uncheck On close, keep the application running if you want Teams to fully exit when you close its window rather than lingering in the tray.
5. Close Teams completely (right-click its tray icon > Quit) and reboot to verify it doesn’t launch. If it still appears, continue — Teams has more than one startup hook.

Fix 2: Remove it from Windows startup locations

Teams registers in multiple places — clear them all.

1. Open Settings > Apps > Startup and toggle Microsoft Teams to Off.
2. Open Task Manager (Ctrl + Shift + Esc) > Startup apps tab, find Microsoft Teams, right-click > Disable. Check the Startup impact column — Teams is often rated High.
3. Press Win + R, type shell:startup, and press Enter — if a Teams shortcut sits in your personal Startup folder, delete it.
4. Also check shell:common startup (the all-users Startup folder) for a Teams entry, though this needs admin rights to modify.
5. Reboot and confirm: no Teams window, no Teams tray icon, and Task Manager’s Startup tab still shows it Disabled. Our startup programs guide covers hunting stubborn entries.

Fix 3: Stop the re-enable cycle after updates

Teams updates are notorious for resurrecting auto-start — break the cycle.

1. After every Teams update, re-check Settings > Apps > Startup — make verifying this part of your routine for a few update cycles until you’re confident it sticks.
2. In the new Teams client, ensure you’re signed into the work/school account properly — sign-in state confusion sometimes triggers the app to “repair” its startup registration.
3. If your laptop is IT-managed, check with your administrator: group policies like “prevent Teams autostart” exist, but so do policies that enforce it. You can’t win a fight against enforced policy locally.
4. Consider switching to the new Teams client if you’re still on classic — the new client is lighter, starts faster, and respects the auto-start toggle more reliably.
5. As a last resort for personal machines, uninstall Teams entirely if you only join occasional meetings — the web app at teams.microsoft.com in Edge or Chrome covers meetings with zero startup footprint.

Fix 4: Reduce Teams’ resource footprint (if you keep it)

If you need Teams daily, make it lighter rather than banishing it.

1. In Teams Settings > General, enable Enable GPU hardware acceleration only if your GPU handles it well — on weak integrated graphics, disabling it can actually reduce stutter.
2. Turn off Register Teams as the chat app for Office if you don’t use Office integration — it adds background hooks.
3. In Settings > Notifications, disable notifications for channels and teams you don’t actively follow — each notification wakes the app.
4. Close Teams fully (tray icon > Quit) when you’re done for the day instead of leaving it running overnight — it accumulates memory over long sessions.
5. Keep Teams updated: … > Check for updates. Performance fixes ship regularly, and an outdated client is often heavier than the current one.

Fix 5: Speed up overall startup so Teams matters less

Even with Teams tamed, a lean startup helps everything.

1. Audit all startup apps in Task Manager > Startup apps — disable updaters, game launchers, chat apps, and utilities you don’t need instantly at login.
2. Open Settings > Apps > Startup and be aggressive: if you can launch it manually in 5 seconds when needed, it doesn’t need to auto-start.
3. Check for OneDrive and other sync clients starting at boot — stagger heavyweights so they don’t all hammer the disk simultaneously.
4. Run Task Manager > Performance during boot (open it quickly after login) to see whether CPU, disk, or memory is the bottleneck — disk at 100% points to too many simultaneous starters.
5. For the full startup-optimization walkthrough, see disabling startup programs and speeding up a slow Windows 11 laptop .

Fix 6: Handle IT-managed and preinstalled Teams

Work laptops play by different rules — know your options.

1. Check whether Teams was installed per-user or machine-wide: Settings > Apps > Installed apps — machine-wide installs (in Program Files) are typically IT-managed.
2. Look for a company portal or software center app — IT often provides an approved removal or configuration path there.
3. If policy enforces auto-start, the pragmatic compromise: let it start, but delay its impact by setting Teams to start minimized and disabling its most expensive features (video previews, GIF autoplay in Settings > Appearance).
4. Ask IT about the Teams autostart policy — many admins will exempt users who request it, since forced autostart generates helpdesk complaints.
5. Document the business case if needed: measure your boot-to-usable time with and without Teams autostart (use Task Manager’s Last BIOS time plus a stopwatch) — numbers persuade IT faster than complaints. Microsoft documents Teams deployment options at Windows support .

Closing

Teams autostart is a solvable annoyance: disable it in the app, in Windows startup, and in the Startup folder, then guard against update resurrection. Your laptop boots to a usable desktop in seconds instead of minutes — and Teams is there when you choose to open it, not when it chooses to open itself.

Frequently asked questions