New Microsoft Teams Won't Install or Update? How to Fix the Switch and the Update Loop

You try to switch to the new Microsoft Teams and it fails to install, the Try the new Teams toggle isn’t there, or Teams keeps telling you to update but never actually finishes updating.

Why: New Teams installs as an MSIX package, which depends on a couple of Windows components and isn’t blocked by organization or Group Policy rules. Update problems are usually because Teams was installed to a non-default location, or it can only update when idle and signed in. Different symptoms have different verified fixes below.

Fix 1: Windows 10 install error (“We’ve run into an issue”)

On Windows 10, the new Teams needs the WebView2 runtime:

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: The “Try the new Teams” toggle is missing

If you can’t even see the switch:

1. Restart the current Teams client first to make sure you have the latest changes, and install pending Windows updates (including security updates).
2. Confirm your PC meets the minimum Windows and Teams versions; the toggle won’t appear on unsupported builds.
3. Sign out of Teams and back in.
4. If it’s still missing, clear the classic Teams folder: quit Teams, press Windows key + R, enter %appdata%\Microsoft\Teams, delete the folder contents (your account data is safe), then restart Teams twice — the toggle should appear.

Note: the toggle is intentionally hidden on VDI machines (Citrix/VMware), for Teams for Life (personal) accounts signed into work Teams, and where an admin has set sign-in restrictions.

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 saying it needs an update but won’t update

For the endless “update available” nag:

1. Force a check: select your avatar in the top-right corner of Teams → Check for updates. Teams updates only when it’s idle and you’re signed in, so leave it open afterward.
2. If updates never stick, it may be installed to the wrong place. Teams auto-updates only from the default per-user location (user\Appdata); a copy in Program Files (often from a deployment script) won’t auto-update.
3. If the banner persists after updating, clear the cache to drop the stale prompt — see our guide on clearing the Teams cache.

FAQ

Do I need to be an administrator to install new Teams? Not normally — it’s a per-user MSIX install. But certain Group Policy/registry settings can block non-admin installs, which is what Fix 3 addresses.

I see “Update and restart” in the title bar after switching. That’s expected — just select the link to restart and finish applying the update.

Where did classic Teams go? After switching, you can still launch either version from the Start menu or taskbar, unless your admin has retired classic Teams.

Sources: Microsoft Learn — Resolve the new Teams installation issues · Microsoft Learn — Automatic update not working in Teams