Microsoft Teams Won't Install or Update? Fix MSIX and Update Errors

Microsoft Teams fails to install or keeps offering an update that never finishes. This guide covers the current Windows MSIX client. Classic Teams stopped functioning on July 1, 2025; restoring its old switcher or updater is not a current recovery option.

Why: MSIX prerequisites, organization policies, an unsupported OS or runtime, and blocked update downloads can prevent installation or updates. Check the exact error and use the supported installer for your environment.

Fix 1: Check Windows and WebView2 prerequisites

Confirm your device meets the current Teams system requirements. Install available Windows updates for a supported OS, and keep the WebView2 runtime current. For the documented Windows 10 “We’ve run into an issue” installation error:

1. Download and install the Microsoft Edge WebView2 Runtime from Microsoft’s developer site (developer.microsoft.com/microsoft-edge/webview2).
2. Restart the Teams desktop app and try the install again.
3. Before retrying, also install any pending Windows updates (Settings → Windows Update) — missing updates are a common blocker.

Fix 2: Install the supported client

Use Microsoft’s current Teams download, or your organization’s approved deployment. Administrators can use the latest TeamsBootstrapper to provision the MSIX package for all users; follow Microsoft’s bulk deployment procedure. Check the result and installation logs if provisioning fails. For Citrix or another VDI environment, have IT follow that provider’s current Teams deployment requirements.

The old Try the new Teams toggle was part of the classic-to-new transition. Do not clear the classic cache to try to bring it back.

Fix 3: “Due to org policy, you can’t install the new Teams”

This message means a policy or registry key is blocking the MSIX install:

1. This is usually controlled by your organization — contact your IT admin.
2. If it’s your own machine, check Group Policy: press Windows key + R, run gpedit.msc, and go to Computer Configuration → Administrative Templates → Windows Components → App package Deployment.
3. Set Prevent non-admin users from installing packaged Windows apps and Allow all trusted apps to install to Not configured.
4. Make sure Windows is fully updated — the October 2023 cumulative update (KB5031455 for Windows 11, KB5031445 for Windows 10) fixed an MSIX install failure tied to these settings.

Fix 4: Teams keeps offering an update

1. When Teams shows Restart or Update and restart, select it to apply the downloaded update. Save meeting work first.
2. On Windows, have IT check Delivery Optimization and access to Microsoft’s update endpoints. Disabling that service or using download mode 100 (Bypass) blocks the current updater.
3. Current Teams MSIX files normally live under Program Files\WindowsApps. Do not move them or change their permissions; the old classic-client rule about an AppData-only updater does not apply.
4. If the update still fails, collect the error and have IT repair/redeploy the current supported package. A cache reset cannot fix a blocked update download or restrictive deployment policy.

FAQ

Do I need to be an administrator to install Teams? It depends on the installation method and device policy. A managed bulk deployment uses administrative provisioning; ask IT if a non-admin install is blocked.

I see “Update and restart” in the title bar. Select it when you can restart to finish applying the downloaded update.

Where did classic Teams go? Classic Teams reached end of availability and stopped functioning on July 1, 2025. Use the current client or Teams on the web while resolving a desktop installation problem.

Sources: Microsoft Learn — Resolve Teams installation issues · Microsoft Learn — Bulk deploy Teams · Microsoft Learn — Teams updates · Microsoft Learn — End of availability for classic Teams