Microsoft Teams Not Working: Fixes for the Five Common Failures

Microsoft Teams not working covers about five different failures that people report with the same sentence. The fixes are not interchangeable, so the useful move is to name the symptom first.

Before anything else, open teams.microsoft.com in a browser. If Teams works there, the service is fine and the problem is the desktop app on that machine. That single check decides everything that follows.

Symptom 1: Teams will not open at all

The icon bounces or the window flashes and disappears.

The first thing to rule out is a Teams process still running invisibly. Open Task Manager with Ctrl + Shift + Esc, find any Microsoft Teams entries, and end them. Then start Teams again. A hung background process blocking a new instance is common enough that it is worth doing before anything else.

If that does not work, the app needs to be reset, which is covered below.

Symptom 2: Teams loads but sits on the splash screen

Teams opens, shows the logo, and stops. Or it loads a blank window.

This is nearly always the local cache. Teams keeps a working copy of your data on disk, and when it corrupts, Teams cannot get past startup.

There are two ways to clear it on the current Teams client for Windows.

The reset, which is easier and does the same job:

1. Open Settings, then Apps, then Installed apps.
2. Search for Microsoft Teams and find the new Microsoft Teams entry.
3. Click the three dots on the right, then Advanced options.
4. Under Reset, click Reset.
5. Start Teams again.

The manual cache clear, if you want the targeted version:

1. Quit Teams properly. Right-click the taskbar icon and select Quit rather than closing the window.
2. Press Windows + R and enter:

%userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams

3. Delete everything in that folder.
4. Start Teams again.

Two things to expect. Resetting the app deletes local app data, which includes personalization settings people may have configured. And the first launch after a cache clear is slow, because everything has to be rebuilt. Tell the user that, or they will report it as a new problem.

Note that this path is for the current Teams client. If you find guidance pointing at %appdata%\Microsoft\Teams, that is for the old client and it will not help you.

Symptom 3: messages will not send

A message sits with a red exclamation mark and a retry option.

This is almost always the network, not Teams. Teams is unusually sensitive to poor connections because it holds a persistent connection rather than making one request at a time. A link that is fine for email and web browsing can be bad enough to break Teams messaging.

Check whether calls also drop or sound rough on the same machine. If they do, you have a network problem, and it is worth reading why the office Wi-Fi is slow before touching the Teams client at all. Signal strength in the corner of the office, a saturated uplink, and an access point serving too many devices all produce exactly this.

If it is one user in one seat, move them somewhere else in the building and try again. That test takes two minutes and answers the question.

Symptom 4: notifications stopped

This one wastes a lot of time because there are four independent switches and all of them have to be on.

Check in this order:

1. Windows Focus Assist or Do Not Disturb. Turns itself on during presentations and stays on.
2. Windows notification settings. Settings, System, Notifications. Teams needs to be allowed there.
3. Teams status. If someone is set to Do Not Disturb inside Teams, notifications are suppressed by design.
4. Teams notification settings. Inside Teams, under Settings and Notifications, per-channel settings can be muted individually. A muted channel is the usual culprit when notifications work everywhere else.

Only after all four are correct is a cache clear worth trying.

Symptom 5: Teams is slow and eats the machine

Teams is a heavy application. On a machine with 8 GB of RAM that is also running Outlook, a browser with twenty tabs, and a line-of-business app, it will struggle, and no amount of cache clearing changes that.

If Teams is slow on one person’s five-year-old laptop and fine on everyone else’s, you have found a hardware problem wearing a software costume. That belongs in the hardware lifecycle line of your IT budget, not in a support queue.

When it is not the app

Some patterns mean you should stop troubleshooting the client:

• Several people break at the same time, which points at the tenant, a policy, or the network
• Teams works on Wi-Fi and fails on the wired network, or the reverse, which points at firewall or VLAN rules
• Guest and external users cannot join meetings, which is a tenant configuration question
• Calls are consistently rough for everyone in a specific room, which is usually the room, and belongs with the rest of the conference room setup

Teams problems that repeat across an office are worth diagnosing once rather than clearing caches every week. That kind of pattern is the point of having a managed IT relationship, and it is often a network fix rather than a Microsoft one.

If Teams is unreliable in your office and nobody has looked at why, tell us what breaks and when and we will tell you whether it is the app, the network, or the room.