Why Won’t Microsoft Teams Open? | Quick Fix Playbook

If the desktop app stalls on the splash screen, never appears, or quits right away, you can fix it with a short checklist. This guide walks through fast causes and fixes that solve the bulk of launch problems on Windows and macOS, plus a fallback that gets you into meetings in minutes.

Fast Checks Before Deeper Fixes

Start with the basics. These steps take under two minutes and resolve many launch stops.

• Reboot the device, then try to start the app again.
• Confirm you are online and sign in to your Microsoft account in other Microsoft apps.
• Open the web version at teams.microsoft.com to rule out a local client glitch.
• Close lingering background processes named “Teams” in Task Manager or Activity Monitor, then relaunch.

Symptom-To-Fix Table

Use this map to spot the cause and jump to the right remedy.

Clear Cached Data And Tokens

Corrupted cache blocks launch more than any other issue. Clearing it does not remove chats or teams; those sync from the cloud on the next sign in.

Windows Steps

1. Quit the app. In Task Manager, end any “Teams” processes.
2. Press Win+R, paste %AppData%\Microsoft\Teams, and press Enter.
3. Delete the contents of these folders if present: Cache, IndexedDB, Local Storage, tmp.
4. Start the app and sign in again.

macOS Steps

1. Quit the app. In Activity Monitor, stop any “Teams” processes.
2. In Finder, press Shift+Cmd+G and go to ~/Library/Application Support/Microsoft/Teams.
3. Delete the same cache folders listed above, then relaunch and sign in.

You can also follow Microsoft’s deeper cache reset that removes the group container on macOS and the app data bundle on Windows. See the official guide on clearing the Teams client cache.

Check Service Health

If meetings will not load or everyone in your org reports trouble, the service may be degraded. Look at the Microsoft 365 health page and any admin messages. When there is an active incident, local tweaks will not fix launch until the issue clears. You can view the live dashboard at the Microsoft 365 service health site.

Repair Or Reset The Desktop App

When cache clears fail, repair or reset the app to restore default files.

Windows

1. Open Settings > Apps > Installed apps > Microsoft Teams.
2. Select Advanced options > Repair. Test launch.
3. If the app still stalls, choose Reset. You will sign in again on next launch.

macOS

1. Drag Microsoft Teams from Applications to the Trash.
2. Empty Trash.
3. Download the current installer from Microsoft and reinstall, then sign in.

Try The Browser Client

The web client is reliable on Edge, Chrome, Firefox, and Safari. If the desktop app fails right before a meeting, open a tab and sign in at teams.microsoft.com. You can join calls, chat, and share screens while you finish repairs on the desktop build. Keep that tab handy during fixes. It works for urgent meetings.

Microsoft Teams Not Opening? Common Causes And Fixes

What Usually Works

1. Check service health to rule out a broad outage.
2. Kill lingering processes, then try again.
3. Clear cache folders and sign in fresh.
4. Repair, then reset the app if needed.
5. Reinstall as a last resort.
6. Use the browser client to keep work moving.

Fix Account And Credential Problems

Stuck tokens or bad saves in the OS keychain can block the sign in loop and keep the app from opening a window.

Windows

1. Open Credential Manager and remove cached entries that mention Teams or Microsoft Office.
2. Sign out of Office apps, then sign in again in one app, and launch Teams.

macOS

1. Open Keychain Access. Search for entries that include “Microsoft” or “Teams”. Delete stale items for your work account.
2. Sign in again in Teams and Outlook to refresh tokens.

Network, Proxy, And Firewall Checks

Launch can stop when traffic to sign in endpoints is blocked. A quick test is to switch to a mobile hotspot and try again. If the app opens on a hotspot but not on office Wi-Fi, the network is filtering the traffic.

• Disable VPN for a minute and retry.
• If you manage the device, add Microsoft sign in and Teams domains to the allow list.
• Ask your admin if TLS inspection is breaking the flow.

On corporate devices, device compliance or Conditional Access rules can also gate launch. Open a browser and sign in to Office on the same device. If that fails with a policy message, address the device posture first.

OS And App Updates

Old desktop builds and dated OS patches trigger odd launch loops. Update the OS, then install the current Teams build. If the app is managed by your org, let the admin channel push the update.

Graphics, Add-Ins, And Startup Conflicts

Launch crashes can link to old GPU drivers, screen capture tools, or meeting add-ins. A short isolation run helps you spot the culprit.

• Update the display driver from your device vendor.
• Turn off third-party overlays, screen recorders, or virtual cameras, then try again.
• On Windows, run a clean boot and enable startup items one by one until the crash returns.

Profile, Storage, And Permissions

A damaged user profile or a full disk can stop launch. Check free space on the system drive. Create a new local profile and test. If launch works there, migrate your data to the new profile or repair the old one. On macOS, confirm the app has access to the Documents folder if your org uses privacy controls.

Reinstall Cleanly

If nothing helps, perform a clean reinstall. Remove the app, delete its remaining data folder, restart, and install the current build. This removes corrupted files and gives you fresh defaults.

Reference Paths And Commands

Keep this table handy when you need exact locations or menu paths during fixes.

When It Is A Known Change

Classic desktop builds have been retired. If the older app was pinned and never updated, launch can fail. Install the current desktop build or use the browser client.

Browser Troubleshooting

If the web client will not load, clear site data for teams.microsoft.com in your browser settings, then sign in again. Turn off privacy extensions for a minute. Try a second browser to confirm the issue is local to a profile. On macOS with Safari, enable the setting that allows pop-ups for the site when you need device prompts during calls.

Admin And Tenant Policies

Some orgs lock features with Conditional Access, device compliance checks, or app protection rules. If the desktop app closes right after sign in, the device may not meet a rule. Open Outlook on the same device and sign in. If Outlook shows a prompt about device compliance or app protection, finish that flow, then try Teams again. If you use a personal Windows copy on a work account, your admin might require a device join before the client can open.

Time, Region, And TLS Handshakes

Wrong system time breaks secure sign in. Open your OS date and time panel, turn on automatic time and time zone, and sync time. Restart and try again. This small fix clears odd token loops where the window never appears.

Clean Sign Out And Fresh App Profile

A partial sign out can leave stale tokens that stop launch. In the app, if you can reach the tray menu, choose Sign out. Then quit all processes, clear cache folders, and start the app. If your user profile on the device is damaged, create a new local account, install the app there, and test launch. Success in the new profile points to a profile-level issue, not the service.

Notes On The Website App

The Website app inside the desktop client no longer loads external sites inside a tab. Links now open in a browser. This change can confuse users who expect a site to appear inside Teams. Launch still works; the behavior of embedded web views changed. If a tab appears blank, use the link button to open that page in the system browser.

When To Escalate

If the app still will not open after cache clears, repair, reset, and reinstall, collect logs and raise a ticket with your admin. Note the time, your version, and any error text. Attach logs from the default folder and include steps tried so the admin can compare with service health posts.

Helpful Official References

For deeper steps on clearing cached data on both platforms, see Microsoft’s guide on clearing the Teams client cache. To check for a broad outage, open the Microsoft 365 service health page. Both links open in a new tab.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback