Fix Teams Update Will Not Install After a Windows Update

After a Windows update, Teams may fail to install its own updates, leaving you stuck on an old version. You might see errors like “Update failed” or “Something went wrong” when Teams tries to download a new build. This often happens because the Windows update changed file permissions or left behind temporary files that block Teams. This article explains the root cause and gives you clear steps to force the Teams update to install successfully.

You will learn how to clear the Teams cache, repair the installation, and reinstall Teams if needed. These methods work for both the classic Teams and the new Teams app on Windows 11 and Windows 10.

Why Teams Updates Fail After a Windows Update

Windows updates often change the permissions on system folders and user profile directories. Teams stores its update files in the AppData folder under your user profile. If the Windows update resets the security descriptors on that folder, Teams cannot write new update files. The result is a failed update attempt that repeats every time you launch the app.

Another common cause is leftover temporary files from a previous update. When a Windows update restarts your PC, Teams may not shut down cleanly. This leaves behind locked files in the Teams cache. On the next launch, Teams tries to overwrite those files but cannot, so the update stalls.

The new Teams app, which is a web-based wrapper, has a different update mechanism. It updates through the Microsoft Store or via the Teams bootstrapper. Windows updates can disrupt the Store’s app registration, causing the new Teams to fail to update silently. You may not see an error, but the version remains old.

Classic Teams vs New Teams Update Paths

Classic Teams updates itself automatically using a built-in updater that runs in the background. It checks for new versions and downloads them to the AppData folder. If that folder is locked or corrupted, the updater fails.

New Teams uses the same mechanism but also relies on the Windows App SDK and WebView2 runtime. If the Windows update replaced WebView2 or the App SDK, the new Teams may not start correctly, and updates fail silently. You can check the version by clicking your profile picture and selecting About.

Steps to Force the Teams Update to Install

Follow these steps in order. Stop after each method and check if Teams updates successfully. To check the version, click your profile picture in Teams and select About. Compare the version with the latest build listed on the Microsoft 365 message center.

1. Close Teams completely and end background processes
   Right-click the Teams icon in the system tray and select Quit. Then press Ctrl+Shift+Esc to open Task Manager. Look for any process named Teams or ms-teams. Select each one and click End Task. This releases all locked files.
2. Clear the Teams cache
   Press Win+R, type %appdata%\Microsoft\Teams, and press Enter. Delete all files and folders inside the Teams folder. Do not delete the Teams folder itself. Then press Win+R again, type %localappdata%\Microsoft\Teams, and delete the contents as well. This clears temporary update files.
3. Restart Teams and trigger a manual update check
   Launch Teams normally. It should start the update process automatically. If not, click your profile picture, select Check for updates. Wait for the download to finish and restart Teams when prompted.
4. Repair the Teams installation
   Open Settings > Apps > Installed apps. Find Microsoft Teams, click the three dots, and select Advanced options. Click Repair. This reinstalls the app files without removing your accounts or settings. After the repair, launch Teams and check for updates again.
5. Reinstall Teams completely
   If repair does not work, uninstall Teams from Settings > Apps. Then download the latest installer from the official Microsoft 365 page. Run the installer and sign in. This gives you a clean installation with the newest version.

If You Use the New Teams App

For the new Teams, the repair and reinstall steps are the same. Additionally, you can reset the Microsoft Store cache. Press Win+R, type wsreset.exe, and press Enter. A blank Command Prompt window opens, then closes. Restart the Store and check for updates for Teams.

If Teams Still Has Issues After the Main Fix

Teams Update Error 0x80070005

This error means access denied. The Windows update may have changed permissions on the AppData folder. Right-click the Teams folder in %appdata%, select Properties, go to Security, and ensure your user account has Full control. Click Edit, select your user, and check Allow for Full control.

Teams Update Stuck at 0%

A stuck update often indicates a network issue or a corrupted download cache. Close Teams, delete the contents of %localappdata%\Microsoft\Teams\Update, and restart Teams. If the problem persists, temporarily disable your VPN or proxy and try again.

Teams Says “Update Failed” with No Error Code

This usually means the update server is unreachable or the app is blocked by a firewall. Check your Windows Defender Firewall settings and allow Teams to communicate through private and public networks. You can also try using a different network, like a mobile hotspot.

Classic Teams vs New Teams Update Comparison

Item	Classic Teams	New Teams
Update path	Built-in updater in AppData	Built-in updater plus Windows App SDK
Cache location	%appdata%\Microsoft\Teams	%localappdata%\Microsoft\Teams
Repair option	Available in Settings > Apps	Available in Settings > Apps
Common failure cause	Corrupted cache or permission change	WebView2 or App SDK conflict
Reinstall method	Download installer from Microsoft site	Download installer or use Microsoft Store

Now you can clear the Teams cache, repair the app, or reinstall it to get the latest version. Start with the cache clear because it is the least invasive. If that does not work, use the repair option. For persistent issues, reinstall Teams completely. As an advanced tip, check the Teams admin center for the update ring settings if you manage multiple users in an organization.