Fix Teams Desktop App Uses the Wrong Tenant When Launched From the Taskbar

When you click the Teams icon in the Windows taskbar, the app may open with a work or school account from the wrong tenant, showing the wrong chats, channels, and files. This happens because Teams caches the last signed-in account and the taskbar shortcut points to a stale executable path. This article explains why the taskbar launch uses the wrong tenant and gives you four methods to force Teams to start with the correct account and tenant.

You will learn how to clear the cached account, reset the app, use a fresh shortcut, and adjust Windows settings that affect which account Teams loads. The fixes take less than ten minutes and do not require administrator rights unless you reinstall the app.

Why Teams Launches With the Wrong Tenant From the Taskbar

Teams stores the last signed-in account in a local cache file. When you launch Teams from the taskbar, the app reads that cache and tries to sign in silently. If you previously signed in with a different tenant, that tenant remains the default until you actively sign out and sign in with another account.

The taskbar shortcut itself can also be the culprit. Windows pins the shortcut to the Teams executable that was active when you pinned it. If you have multiple versions of Teams installed, such as the classic Teams and the new Teams, the pinned shortcut may point to the wrong file. That wrong executable loads a different cache, which belongs to another tenant.

Another cause is Windows credential storage. Teams may store tokens in Windows Credential Manager. Those tokens are tied to a specific tenant. When the app launches, it grabs the first token it finds, which may not match the tenant you want.

Steps to Force Teams to Launch With the Correct Tenant

Use these methods in order. Start with the simplest and move to the more thorough fixes only if the problem persists.

Method 1: Sign Out Completely and Clear Cached Credentials

1. Open Teams and go to your profile picture
   Click your avatar in the top-right corner of the Teams window. Select Sign out from the menu. This signs out the current account but does not delete the cached data.
2. Close Teams completely
   Right-click the Teams icon in the system tray and choose Quit. This ensures no background process keeps the cache files locked.
3. Delete the Teams cache folder
   Press Ctrl + R to open the Run dialog. Type %appdata%\Microsoft\Teams and press Enter. Delete the contents of this folder, but keep the folder itself. Do not delete the folder, only its contents.
4. Clear Windows Credential Manager entries
   Open Control Panel and go to User Accounts > Credential Manager > Windows Credentials. Look for entries that start with Teams or Microsoft Teams. Remove all of them. This deletes the stored tokens that point to the wrong tenant.
5. Relaunch Teams from the Start menu
   Click the Start button and search for Teams. Launch it from the search result, not from the taskbar. Teams will ask you to sign in. Enter the account for the tenant you want to use.

After signing in, pin the new window to the taskbar by right-clicking the Teams icon in the taskbar and choosing Pin to taskbar. This replaces the old pinned shortcut with the correct one.

Method 2: Reset Teams Using the Built-in Repair

1. Open Settings in Teams
   Launch Teams and click your profile picture. Select Settings from the menu.
2. Find the reset option
   Scroll down to the About section. Look for a button labeled Reset or Repair. The exact label depends on your Teams version. New Teams shows Reset under About.
3. Confirm the reset
   Click the reset button and confirm when prompted. Teams will close and reopen automatically. This clears the local cache and resets the app to its default state.
4. Sign in with the correct tenant
   After the reset, Teams opens a sign-in window. Enter the account for the tenant you need. Do not use the taskbar shortcut until you have signed in successfully.

The reset does not remove your files or chats, but it does clear all local settings, including the cached tenant.

Method 3: Create a Fresh Taskbar Shortcut

1. Unpin the current Teams shortcut
   Right-click the Teams icon in the taskbar and select Unpin from taskbar.
2. Locate the correct Teams executable
   Open File Explorer and go to %localappdata%\Microsoft\Teams\current. Look for Teams.exe. If you use the new Teams, the path is %localappdata%\Microsoft\Teams\current as well, but the executable may be named ms-teams.exe. Right-click the correct executable and choose Send to > Desktop (create shortcut).
3. Replace the desktop shortcut
   Delete the old desktop shortcut if one exists. Right-click the new shortcut and select Properties. In the Target field, verify that the path points to the correct executable. Click OK.
4. Pin the new shortcut to the taskbar
   Right-click the new desktop shortcut and choose Show more options > Pin to taskbar. Now the taskbar icon points to the correct Teams version.

This method solves the problem when the pinned shortcut pointed to an old or wrong Teams installation that used a different cache.

Method 4: Adjust Windows Settings to Prevent Automatic Sign-in

1. Open Windows Settings
   Press Windows + I to open Settings. Go to Accounts > Email & accounts.
2. Remove the unwanted work or school account
   Find the account that belongs to the wrong tenant. Click it and select Remove. This disconnects the account from Windows, so Teams will not use it for silent sign-in.
3. Check the default sign-in options
   Go to Settings > Accounts > Sign-in options. Disable any option that says Use my sign-in info to automatically finish setting up my device. This stops Windows from automatically signing you into apps with the last account.
4. Relaunch Teams
   Close Teams completely, then launch it from the Start menu. Sign in with the correct tenant account.

This method is useful when Teams keeps reverting to a tenant even after you sign out.

If Teams Still Launches With the Wrong Tenant

Teams Opens With the Wrong Tenant After Signing Out

The cached token may still be stored in the Teams local storage. Repeat Method 1, but also delete the folder %appdata%\Microsoft\Teams\Storage. This folder holds the local database that stores the last signed-in account. After deleting it, Teams will act like a fresh install.

Teams Shows the Tenant Selection Screen Every Time

If Teams opens the tenant picker on every launch, the app cannot find a valid token. This is normal after clearing the cache. Sign in once and the picker will stop appearing. If it keeps appearing, check that you have not disabled the Stay signed in option during sign-in.

The Taskbar Shortcut Points to the Classic Teams Instead of New Teams

The classic Teams and new Teams use separate caches. If your taskbar shortcut points to the classic Teams, it will use the classic cache, which may contain a different tenant. Follow Method 3 to create a shortcut to the new Teams executable. You can also unpin the classic shortcut and pin the new Teams from the Start menu.

Teams Taskbar Shortcut vs Start Menu vs Web: Key Differences

Item	Taskbar Shortcut	Start Menu Shortcut	Teams on the Web
Cache location	Uses the cache of the pinned executable	Uses the default Teams executable	Uses browser cookies and storage
Tenant selection	May be locked to a previous tenant	Prompts for account if cache is clear	Always asks for account unless saved
Silent sign-in	Uses Windows Credential Manager	Uses Windows Credential Manager	Uses browser session only
Best for	Quick access to a single tenant	First launch after cache reset	Testing multiple tenants without cache conflicts

The web version is the fastest way to verify that your account and tenant are correct before you fix the desktop app. Use it as a diagnostic tool.

After applying the fixes, you can now launch Teams from the taskbar and see the correct tenant. Start with Method 1 and confirm the tenant on the next launch. If the problem returns, use Method 2 to reset Teams completely. For a permanent solution, pin a fresh shortcut to the new Teams executable and disable automatic sign-in in Windows Settings.