TeamsFixer
de en

Teams will not start

Teams refuses to open or closes immediately. These steps bring the client back - with instructions for Windows and macOS.

Last verified:

Affected systems

windows macos

Quick fixes

  • Kill Teams in Task Manager and relaunch
  • Clear the cache
  • Verify WebView2 (Windows) or Rosetta (macOS Apple Silicon) is installed

Quick test

Kill all Teams processes and relaunch. This often suffices after sleep or screen lock.

Windows

Press Ctrl + Shift + Esc, go to the “Processes” tab and end every entry containing “Microsoft Teams”. Then relaunch Teams.

macOS

Open Activity Monitor (Cmd + Space, “Activity Monitor”), search for “Teams” and Force Quit all processes. Then relaunch Teams.

Clear cache (the main fix)

More than half of all cases respond to a cache reset.

Windows

Classic client:

%appdata%\Microsoft\Teams

New client:

%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache

In the Run dialog (Win + R), paste the path, press Enter, delete the folder contents.

macOS

Classic client:

~/Library/Application Support/Microsoft/Teams

New client:

~/Library/Group Containers/UBF8T346G9.com.microsoft.teams

In Finder press Cmd + Shift + G, paste the path, Enter, delete contents.

Verify runtime prerequisites

Windows

The new Teams client requires the Microsoft Edge WebView2 Runtime. Look in “Apps and Features” for the entry. If missing, install the Evergreen build from Microsoft:

WebView2 Runtime Download

macOS

On Apple Silicon (M1/M2/M3) Teams does not need Rosetta - the new client runs natively. If you still use the classic client and Rosetta is missing, run in Terminal:

softwareupdate --install-rosetta

Sign-in failures?

If Teams shows a sign-in code, look up the matching error page. Related errors are listed at the bottom.

When nothing works

  • Collect logs and send to IT:
    • Windows: %appdata%\Microsoft\Teams\logs.txt
    • macOS: ~/Library/Application Support/Microsoft/Teams/logs.txt
  • Try https://teams.microsoft.com in a browser - if that works, it is a client-side issue.
  • Microsoft Support for stubborn cases.

Related errors