Microsoft Teams usually keeps opening itself because it is set to launch at sign-in or a background process is restarting it. Start by disabling Teams in startup apps and ending all Teams processes. If you skip that, the app can keep relaunching, drain battery, interrupt meetings, and keep sign-out from sticking. This guide shows how to stop Teams from reopening on Windows and Mac, then checks cache problems and managed-device policies.
Why Teams keeps opening on its own
The usual trigger is simple: something is launching Teams again after you close it. That can be a startup setting, a hidden process, a cache problem that keeps restoring the app state, an Office or Teams update loop, or a managed-device policy change on a work account.
Start with startup and background-process checks. Those are the fastest fixes and the most common reason Teams opens again after you close it.
| Symptom trigger | Likely cause | Fastest test | Exact fix | How to verify it’s fixed |
|---|---|---|---|---|
| Teams opens right after Windows or Mac sign-in | Startup enabled | Check startup apps or login items | Turn off Teams in Windows Startup apps or remove it from Mac Login Items | Restart the device and confirm Teams stays closed until you open it |
| Teams reappears after you close the window | Hidden background Teams process | Open Task Manager on Windows or Force Quit on Mac | End every Teams process, then relaunch once | Close Teams again and confirm no Teams process remains active |
| Teams opens, shows a blank or stuck window, then relaunches | Corrupted cache | Clear the Teams cache folders | Delete the cache folders in the correct Teams location for your app version | Open Teams, sign in, close it, and confirm it does not reopen on its own |
| Teams and other Microsoft apps keep changing together | Office or Teams update loop | Check Office account update options | Run Update Now, then Quick Repair or Online Repair if needed | After the repair, restart and confirm Teams opens normally once |
| Only a work or school device has the problem | Org-managed policy or Intune | Check whether the device is managed | Ask IT to review Intune, Microsoft Endpoint Manager, licensing, and policy changes | IT confirms the policy change is removed or corrected and Teams stops relaunching |
📊 Microsoft's support page says Microsoft 365 sign-in is available on Windows, macOS, iOS, Android, and web. Source: Sign in to Microsoft 365.
Check startup settings first
If Teams opens at sign-in, stop it at the source first. This is the cleanest fix, and it separates a startup setting from a real app fault. On managed devices, a policy can turn the setting back on later, so verify after the change.
Windows: turn off Teams in Startup apps
- Open Settings > Apps > Startup.
- Find Microsoft Teams or Teams.
- Turn the switch Off.
- Restart Windows.
- After sign-in, wait one minute and confirm Teams does not open by itself.
Say your laptop opens Teams before you click anything after sign-in. Turning off the startup entry should stop that behavior on the next restart, unless another process or policy brings it back.
Mac: remove Teams from Login Items
- Open System Settings > General > Login Items.
- Look for Microsoft Teams or Teams in the list.
- Select it and choose Remove or click the minus button if shown.
- Log out or restart the Mac.
- Check whether Teams stays closed after the next sign-in.
If Teams still opens, move to the process check. Login Items only cover one path.
End the stuck Teams process
Teams can stay alive in the background after you close the window. That hidden process can reopen the app, keep a sign-in loop going, or stop a clean relaunch. End the process first, then open Teams again only after the old instance is gone.
Windows: close Teams in task Manager
- Press Ctrl + Shift + Esc to open Task Manager.
- On the Processes tab, find Microsoft Teams and any related Teams entries.
- Select each one and choose End task.
- Check the task list again to confirm no Teams process remains.
- Open Teams once and see whether it still reopens after you close it.
A common first-time mistake is pinning Teams to the taskbar and then reopening it repeatedly after every notification appears. If the old instance is still active, the new launch can look like a fresh start while the background copy keeps running.
Mac: force quit Teams if it will not quit
- Try Teams > Quit Microsoft Teams first.
- If it will not quit, open the Apple menu and choose Force Quit.
- Select Microsoft Teams.
- Click Force Quit.
- Relaunch Teams only after it disappears from the Force Quit list.
If Teams opens again after a force quit, the next likely step is cache cleanup.
Clear the Teams cache safely
Cache damage can make Teams reopen, hang, or come back in a broken state. Keep the classic and new Teams paths separate, because the folder locations are not the same. Back out of Teams before deleting anything, then relaunch and sign in again.
Windows: clear classic Teams cache folders
- Close Teams and end it in Task Manager.
- Open the Run box with Windows + R.
- Paste %appdata%\Microsoft\Teams\ and press Enter.
- Delete the cache-related folders: Cache, blob_storage, databases, GPUCache, IndexedDB, tmp, and Local Storage.
- Open Teams again and sign in.
That folder set matches the common cache-reset pattern for classic Teams, including application cache, blob_storage, databases, GPUCache, IndexedDB, tmp, and Local Storage.
Windows: clear new Teams cache folders
- Close Teams and end it in Task Manager.
- Open File Explorer.
- Go to %LocalAppData%\Packages\MSTeams_8wekyb3d8bbw.
- Open the app data area for Teams and remove the cache folders that match the app’s local storage, including Cache, blob_storage, databases, GPUCache, IndexedDB, tmp, and Local Storage where present.
- Launch Teams again and sign in.
Suppose Teams opens, shows a blank white panel, then disappears and relaunches. That pattern often points to a bad local cache rather than a sign-in setting.
Mac: clear Teams cache folders
- Quit or force quit Teams.
- Open Finder, choose Go > Go to Folder, and enter the Teams app data path used on your Mac account.
- Remove the Teams cache folders that correspond to Cache, blob_storage, databases, GPUCache, IndexedDB, tmp, and Local Storage.
- Open Teams again.
- Sign in and check whether it stays closed after you quit it.
If the cache comes back or Teams still relaunches, move on to update and repair checks.
Could an update or repair loop be the cause?
If Teams or Microsoft 365 changed recently, an update loop or broken install can keep the app relaunching. Use the app’s own update path first. Repair is the next step on Windows when the app keeps misbehaving after startup and cache checks.
Check for Microsoft 365 or Office updates
- Open any Office app, such as Word or Outlook.
- Go to File > Account.
- Select Update Options.
- Choose Update Now.
- Restart the device and check whether Teams still opens by itself.
Run repair on Windows
- Open Settings > Apps > Installed apps.
- Find Microsoft 365 or Office.
- Select Modify or Change, then choose Quick Repair.
- If that does not help, repeat the path and choose Online Repair.
- Restart and verify whether Teams still reopens on its own.
When reinstalling is worth trying
- Use the Office repair path first.
- If Teams still restarts, uninstall Office or Microsoft 365 from Installed apps.
- Run the Office uninstall support tool to remove remaining traces of Office 365.
- Reinstall the app package your tenant or subscription uses.
- Open Teams and confirm whether the reopening behavior is gone.
Technipages recommends the Office account update path, Quick Repair, Online Repair, and reinstalling Office 365 if Teams still restarts.
What if your account or device is the problem?
If startup, process, cache, and repair checks fail, the issue may be tied to the user profile or to device management. That is more common on business tenants, where Intune or Microsoft Endpoint Manager can change app behavior after licensing or policy updates.
Test a new Windows user profile
- Open Settings > Accounts > Other users.
- Add a new local or Microsoft account profile.
- Sign out of the current profile.
- Sign in to the new profile and open Teams there.
- If Teams behaves normally in the new profile, the old profile likely has local corruption.
The same source suggests creating a new user account if Office was not the problem.
Check whether Intune or Endpoint Manager is involved
- Confirm whether the device is enrolled in Intune or Microsoft Endpoint Manager.
- Check whether Teams changed after a license or policy update.
- Ask IT to review app assignment, sign-in policy, and device compliance settings.
- If possible, compare behavior on another managed device with the same account.
- Have IT confirm whether a policy is relaunching Teams at sign-in.
Spiceworks reports an Intune-related change after premium licenses caused logon issues, and another report says configuring Intune made Teams and Outlook start working normally.
Still not working?
Use a built-in Windows repair path, then move to vendor support if the app still opens by itself. If the issue appears only on one managed device or one Windows profile, that points away from a general Teams outage and toward a local or policy-based cause.
Use the Windows troubleshooter
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Run the Windows Store Apps troubleshooter.
- Finish the prompts and restart the device.
- Open Teams and see whether it still relaunches.
Gather the exact details before escalation
- Note whether the app is classic Teams or the newer Teams app.
- Write down whether it opens at sign-in, after you close it, or after a meeting link or Office app launch.
- Record whether the device is personal, work-managed, or school-managed.
- Tell support whether you already checked startup items, Task Manager, cache folders, and repair options.
- If the device is managed, ask IT to review Intune, licensing, and Teams policy first.
Microsoft’s support sign-in paths cover personal Microsoft accounts and work/school accounts on Windows, macOS, iOS, Android, and web, so the account type matters when you report the problem.
Frequently asked questions
Why does microsoft teams keep opening automatically?
The fastest explanation is a startup setting or a background process. Turn off Teams in Windows Settings > Apps > Startup or remove it from Mac System Settings > General > Login Items, then end any live Teams process before you reopen it.
Why does microsoft teams keep opening randomly?
That usually means something is relaunching it after you close it. Check Task Manager on Windows or Force Quit on Mac, then clear the correct cache folders. If it happens only on a work device, ask IT to review policy or Intune changes.
How do I stop microsoft teams from opening in the background?
Open Task Manager on Windows and end every Teams process, or use Force Quit on Mac. Then relaunch Teams once. If a background copy keeps coming back, clear the cache folders and check whether startup launch is still enabled.
Why does my microsoft teams keep opening on its own?
Most often, it is either set to open at sign-in or it is recovering from a stuck local state. Start with startup items, then background processes, then cache folders. If the device is managed, a policy or license change may be restoring the launch behavior.
Why does microsoft teams open automatically?
Teams can open automatically when the app is pinned to startup, when a hidden process remains active, or when the local profile is damaged. On Windows, test a new user profile if repair and cache cleanup do not help, because that separates profile damage from app damage.