Fix Teams Update Will Not Install When Switching Between Tenants

When you switch between work or school tenants in Microsoft Teams, the update process can stall or fail completely. You see the update icon, but clicking it does nothing, or the update downloads and then rolls back. This happens because Teams stores tenant-specific data and update state in separate profiles on your computer. This article explains why switching tenants breaks the update mechanism and gives you a step-by-step fix to get Teams updating again.

The root cause is a corrupted or locked update cache in the Teams app data folder. When you switch tenants, Teams creates a new profile but reuses the same update cache. If the cache contains files from the previous tenant, the update installer cannot verify them and aborts. You will learn how to clear the cache, reset the update service, and reinstall Teams cleanly.

Why Switching Tenants Blocks the Teams Update

Teams stores its application files, update cache, and per-tenant profile data in the folder %appdata%\Microsoft\Teams. When you sign in to a different tenant, Teams creates a new subfolder for that tenant’s profile but keeps the same update cache folder. The update installer checks the cache for integrity before applying a new version. If the cache contains files from a previous tenant, the verification fails and the update stops.

Another common cause is a locked file. The Teams update process runs as a background service called TeamsUpdater. If that service is still running when you click the update button, it holds a lock on the update executable. The installer cannot overwrite the locked file, so it shows an error or silently fails.

In rare cases, the tenant switch changes the update channel. For example, your first tenant might use the Current channel, while the second uses the Monthly Enterprise channel. Teams does not handle channel switches well and may refuse to install an update that does not match the expected channel.

Steps to Clear the Update Cache and Reinstall Teams

1. Exit Teams completely
   Right-click the Teams icon in the system tray and choose Exit. Then open Task Manager with Ctrl+Shift+Escape. In the Processes tab, look for any process named Teams or TeamsUpdater. Select each one and click End Task. This releases the lock on the update files.
2. Back up your chat and files if needed
   Your chat history is stored in the cloud, so you do not need a backup for messages. But if you have local files saved in the Teams folder, copy them to another location. The next step deletes the entire folder.
3. Delete the Teams app data folder
   Press Win+R, type %appdata%\Microsoft\Teams, and press Enter. Select all items inside that folder and press Delete. If any files are in use, go back to Task Manager and end the Teams processes again, then retry the deletion.
4. Clear the Teams update cache
   The update cache is stored in %localappdata%\Microsoft\Teams\Update. Open that path and delete everything inside it. This forces Teams to download a fresh update package.
5. Reinstall Teams using the official installer
   Go to the Teams download page at teams.microsoft.com/downloads and download the installer for your operating system. Right-click the downloaded file and choose Run as administrator. Follow the prompts. The installer will place Teams in the correct folder and create a fresh update cache.
6. Sign in to your primary tenant first
   After installation, launch Teams and sign in to the tenant you use most often. Let Teams fully load and check for updates. Once the update is applied, you can switch to the other tenant. This prevents the cache from being created with mixed tenant data.

If Teams Still Has Issues After the Main Fix

Teams Shows a Blank Window After Reinstall

A blank window usually means the Teams cache is still corrupted. Close Teams, delete the %appdata%\Microsoft\Teams folder again, and restart Teams. If the problem persists, clear the Windows credential manager entries for Teams. Open Control Panel > Credential Manager > Windows Credentials and remove any entries that contain Teams or Skype.

Teams Keeps Asking Me to Switch Tenants

This happens when Teams stores the tenant ID in the registry. Open Registry Editor with Win+R and type regedit. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\Teams. Delete the TenantId value. Restart Teams and sign in again. This resets the tenant association without affecting your profile.

The Update Fails With Error Code 0x80070005

Error 0x80070005 means access denied. The update installer cannot write to the Program Files folder. Run the installer as administrator, or temporarily disable your antivirus software during the update. After the update completes, re-enable your antivirus.

New Teams vs Classic Teams: Update Behavior Differences

Item	New Teams	Classic Teams
Update cache location	%localappdata%\Microsoft\Teams\Update	%appdata%\Microsoft\Teams\Update
Tenant profile storage	Separate per-tenant folders in app data	Single profile with tenant switch
Update channel switching	Supported, but requires cache reset	Not supported, may block updates
Recommended fix for stuck update	Delete cache and reinstall	Delete entire app data folder

The new Teams app, released in 2023, stores update files separately from user data. This makes it more resilient to tenant switches, but it still has the same cache-locking problem. The fix is identical: clear the cache and reinstall. The classic Teams app, which is being retired, has the update cache inside the app data folder, so deleting that folder is the only reliable fix.

After following the steps above, Teams will update normally even when you switch between tenants. Start by clearing the update cache and reinstalling Teams with administrator rights. Then sign in to your primary tenant first to establish a clean update baseline. For persistent errors, check the Windows Event Viewer for the Teams update service logs to identify the exact file that is failing. This targeted approach saves time compared to a full system reset.