Teams Constantly Reconnecting Windows 11 Fix [2026]

Quick Answer: Teams reconnects because of network jitter exceeding 100ms, GPU-accelerated rendering conflicts, or corrupted local cache files. Clear Teams cache at %appdata%\Microsoft\Teams\Cache, disable GPU hardware acceleration in Teams settings, and switch to 5GHz Wi-Fi to reduce jitter.

Symptoms

• Teams shows "Reconnecting..." every 2-5 minutes during calls
• Audio cuts out, then "We're having trouble connecting"
• Teams works fine on web but desktop app reconnects
• Other apps (Zoom, browser) work fine — only Teams has issues
• Reconnecting happens more during video calls than chat
• Teams crashes then auto-restarts repeatedly

Why This Happens (Root Cause)

Teams reconnecting is usually caused by three factors:

1. Network Jitter Timeout: Teams has a hardcoded 100ms jitter tolerance. If your Wi-Fi ping varies by more than 100ms (common on 2.4GHz with interference), Teams drops the media connection and tries to reconnect.

2. GPU Acceleration Conflicts: Teams uses Chromium's GPU acceleration for video rendering. On hybrid graphics laptops (Intel + NVIDIA), Teams sometimes switches GPUs mid-call, causing a 2-second freeze that Teams interprets as a disconnect.

3. Cache Corruption: Teams stores authentication tokens, call history, and media preferences in %appdata%\Microsoft\Teams. Corrupted cache files cause Teams to re-authenticate repeatedly, appearing as "reconnecting."

How to Diagnose (Manual)

Check 1: Test Network Jitter

$results = 1..20 | ForEach-Object { (Test-Connection -ComputerName 13.107.64.0 -Count 1).ResponseTime }; $avg = ($results | Measure-Object -Average).Average; $max = ($results | Measure-Object -Maximum).Maximum; $min = ($results | Measure-Object -Minimum).Minimum; "Avg: $avg ms, Max: $max ms, Min: $min ms, Jitter: $($max-$min) ms"

Expected output:

Avg: 45 ms, Max: 62 ms, Min: 38 ms, Jitter: 24 ms

If jitter > 100ms: Network is too unstable for Teams media.

Check 2: Check Teams GPU Usage

Get-Process teams | Select-Object Name, PagedMemorySize, WorkingSet

If WorkingSet > 1GB: Teams cache is bloated, causing memory pressure reconnections.

Check 3: Inspect Teams Cache Size

Get-ChildItem "$env:APPDATA\Microsoft\Teams" -Recurse | Measure-Object -Property Length -Sum | Select-Object Sum

If Sum > 500MB: Cache is oversized and likely corrupted.

Step-by-Step Fix

Method 1: Clear Teams Cache (Most Effective)

1. Fully close Teams — right-click Teams tray icon → Quit
2. Press Windows + R, type %appdata%\Microsoft\Teams, press Enter
3. Delete these folders (NOT the entire Teams folder):
   • application cache\cache
   • blob_storage
   • Cache
   • databases
   • GPUCache
   • IndexedDB
   • Local Storage
   • tmp
4. Restart Teams

This fixes: 70% of reconnecting issues by clearing corrupted auth and media cache.

Method 2: Disable GPU Hardware Acceleration

1. Open Teams → Click ... (three dots) → Settings
2. Go to General
3. Uncheck "Disable GPU hardware acceleration" (or check it, depending on version)
   • Look for: "Turn on new meeting experience" — keep this ON
4. Restart Teams

On hybrid GPU laptops, also:

1. NVIDIA Control Panel → Manage 3D settings
2. Find Teams → Set to Integrated graphics (not High-performance NVIDIA)

Method 3: Switch to 5GHz Wi-Fi

1. Settings → Network & internet → Wi-Fi
2. Click your network → Properties
3. Verify "Band" shows 5GHz

If connected to 2.4GHz:

• Log into router (192.168.1.1)
• Name 2.4GHz and 5GHz networks differently
• Connect Windows 11 to 5GHz network

Method 4: Use Teams Web App as Fallback

If desktop Teams continues reconnecting:

1. Open browser (Edge/Chrome)
2. Go to teams.microsoft.com
3. Sign in

The web app uses browser networking, which handles jitter better than Teams desktop's custom media stack.

Method 5: Update or Reinstall Teams

# Uninstall Teams (both versions)
Get-Process teams | Stop-Process -Force
Get-AppxPackage *teams* | Remove-AppxPackage
Start-Process "C:\Program Files\WindowsApps\MSTeams_*\Teams.exe" -ErrorAction SilentlyContinue

Then:

1. Download latest Teams from teams.microsoft.com/download
2. Install New Teams (the 2024+ version, not classic)
3. Sign in and test

Method 6: Registry Fix for Teams Media Timeout

Create a .reg file:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Lync]
"MediaTimeout"=dword:00007530

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Teams]
"MaxMediaTimeout"=dword:0000ea60

What this does: Increases media timeout from 10 seconds to 30 seconds, giving Teams more tolerance for network jitter before declaring a disconnect.

How Againly Diagnoses This Automatically

Againly runs check_teams_specific in 1.0 second and detects:

• Network jitter to Microsoft Teams media servers (13.107.64.0/18)
• Teams cache size and corruption indicators
• GPU acceleration conflicts with hybrid graphics
• Teams version (new vs classic) and update status
• Wi-Fi band (2.4GHz vs 5GHz) and interference

Instead of guessing, it shows: "Teams cache 890MB with jitter 180ms — clearing cache and recommending 5GHz switch."

[CTA: Try free diagnosis]

Prevention

• Clear Teams cache monthly — prevents accumulation of corrupted files
• Use 5GHz Wi-Fi — lower jitter, less interference than 2.4GHz
• Update Teams regularly — Microsoft fixes reconnecting bugs monthly
• Disable GPU switching for Teams — lock to integrated graphics on hybrid laptops

FAQ

Q: Why does Teams reconnect but Zoom works fine? A: Zoom tolerates up to 300ms jitter. Teams has a stricter 100ms threshold. Your network is between those values.

Q: Will clearing cache delete my chat history? A: No — chat history is stored in Microsoft's cloud. Cache only stores local files and temporary data.

Q: Why does reconnecting only happen on video calls? A: Video calls use much more bandwidth (2-5 Mbps) and are sensitive to packet loss. Chat uses minimal bandwidth.

Q: Is the New Teams better than Classic Teams? A: Yes — New Teams (2024+) has rewritten media stack with better jitter tolerance and lower memory usage.

Related: Teams High CPU Usage Fix | Teams Audio Not Working Fix