Fix Teams Message Will Not Send after Moving to New Teams

After you switch to the new Microsoft Teams desktop app, you may find that your messages fail to send. The message stays in the compose box with an error icon, or it shows as sent but never appears in the chat. This often happens because the new Teams client uses a different data storage folder and a fresh cache, which can become corrupted or conflict with old settings. In this article, you will learn the specific causes and step-by-step fixes to get your messages sending again in the new Teams environment.

Why New Teams Blocks Message Sending

The new Teams desktop app is built on a different architecture than classic Teams. It runs as a packaged app and stores its data in a separate folder under %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe. When you migrate from classic Teams, your old cache and settings are not carried over. The new client creates a fresh cache. If that cache becomes corrupted during the first launch, or if your network blocks the new app’s endpoints, messages will fail to send.

Another common cause is a conflict between the new Teams and the older Teams installation. Both apps may try to lock the same communication ports, or the new app may inherit a stale proxy configuration from your system. Additionally, if your admin has not enabled the new Teams for your tenant, the app may run in a degraded mode where sending is disabled.

Technical Root Cause

The send failure is typically a result of one of these three issues: a corrupted local cache, a blocked network path to the Teams service, or an incomplete migration of your user profile. The new Teams client uses the WebSocket protocol for real-time messaging. If your firewall or proxy blocks WebSocket connections to teams.microsoft.com and all subdomains, your messages will not transmit. The app does not always show a clear error, so you must check the network manually.

Steps to Diagnose and Fix Message Sending in New Teams

Follow these steps in order. Test sending a message after each step to see if the issue is resolved.

1. Check your network connection to Teams
   Open a web browser and go to https://admin.teams.microsoft.com. If the page loads, your network can reach the Teams service. If it does not load, you have a network or proxy issue. Check your proxy settings in Windows: go to Settings > Network & internet > Proxy. Turn off any manual proxy that may be blocking the connection. Then restart Teams.
2. Clear the new Teams cache
   Close Teams completely. Right-click the Teams icon in the system tray and choose Quit. Then open File Explorer and navigate to %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams. Delete all files and folders inside this directory. Do not delete the parent folders. Restart Teams. This removes any corrupted cache that may be blocking message sending.
3. Repair the Teams installation
   Go to Settings > Apps > Installed apps in Windows. Scroll to Microsoft Teams. Click the three dots next to it and choose Advanced options. Then click Repair. Windows will fix any broken files without removing your app data. After the repair, restart Teams and test sending a message.
4. Switch back to classic Teams temporarily
   If the issue persists, try using classic Teams to see if the problem is specific to the new client. In the new Teams, click your profile picture at the top right and select Switch back to classic Teams. If messages send in classic Teams, the new client has an installation issue. Uninstall the new Teams completely, then reinstall it from the Microsoft 365 admin center.
5. Check your Teams policy settings
   If you are an admin, verify that the new Teams is enabled for your tenant. Go to Teams admin center > Teams > Teams upgrade settings. Ensure that Use new Teams client is set to Enabled. Also check Messaging policies to confirm that sending messages is not disabled for your user. Look at Teams admin center > Messaging policies and verify that Send messages is set to On.

If Teams Still Has Issues After the Main Fix

Teams Shows “Message Failed to Send” with a Red Exclamation Mark

This error appears when the message cannot reach the server. First, check your internet connection. Then try sending a message to a different person to rule out a conversation-specific issue. If the error persists, clear the cache as described in step 2. The red exclamation mark often disappears after a cache refresh.

Messages Send but Never Appear in the Chat

This symptom indicates a synchronization problem. The message was sent but the chat window is not refreshing. Press Ctrl+R to reload the chat. If that does not work, sign out of Teams and sign back in. Go to your profile picture, select Sign out, then sign in again. This resets the chat synchronization.

New Teams Does Not Start at All After Migration

If the new Teams app crashes or shows a blank window, the installation may be incomplete. Uninstall Teams from Settings > Apps > Installed apps. Then reinstall it from the Microsoft 365 admin center or from https://teams.microsoft.com/downloads. After reinstallation, test sending a message.

New Teams vs Classic Teams: Key Differences for Message Sending

Item	New Teams	Classic Teams
Data storage folder	%LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe	%AppData%\Microsoft\Teams
Cache clearing method	Delete contents of LocalCache\Microsoft\MSTeams	Delete contents of %AppData%\Microsoft\Teams\Cache
Repair option	Available in Windows Settings > Apps > Installed apps	Available in Control Panel > Programs and Features
Switch back option	Profile picture > Switch back to classic Teams	Profile picture > Switch to new Teams

The table shows that the new Teams uses a completely different folder structure. This is why simply copying the old cache does not work. You must clear the new cache specifically to fix send issues.

Now you can fix message send failures in new Teams by clearing the cache, repairing the app, or checking your network and policy settings. Start with the cache clear because it is the most common fix. If the problem continues, use the repair option. As an advanced tip, you can also run the new Teams with the –no-cache command-line argument to skip the cache entirely for testing purposes.