Laptop showing Microsoft Teams loading screen with hands on keyboard
Teams Loading FailureMicrosoft TeamsMicrosoft Teams

Fix Microsoft Teams Not Loading Error – Windows 10, Windows 11 2026

Microsoft Teams fails to load or gets stuck on startup screen due to cache corruption, network issues, or outdated client. Clear Teams cache, reset network settings, and reinstall the application to resolve loading problems.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
11 Mar 202612 min read12 views
Error CodeTeams Loading Failure
ProductMicrosoft Teams
KB ArticleKB5034128
Solutions5 methods
Sources3 official
Affected SystemsWindows 10, Windows 11, macOS
Quick Fix

The fastest solution is to clear Microsoft Teams cache. Close Teams completely, navigate to %appdata%\Microsoft\Teams, delete all folders except 'Logs', and restart Teams. This resolves 80% of loading issues caused by corrupted cache files.

Symptoms

  • Microsoft Teams shows loading screen indefinitely
  • Teams application starts but remains on white or blank screen
  • Teams crashes immediately after launch
  • Error message: "We're sorry - we've run into an issue"
  • Teams icon appears in system tray but interface doesn't load
  • Application freezes during sign-in process
  • Teams loads partially with missing features or channels

Possible Causes

  • Corrupted Teams cache and temporary files
  • Outdated Microsoft Teams client version
  • Network connectivity issues or proxy configuration problems
  • Windows user profile corruption
  • Conflicting third-party antivirus or firewall settings
  • Insufficient system resources or memory
  • Registry corruption affecting Teams startup
  • Microsoft 365 authentication token expiration
1

Clear Microsoft Teams Cache

Corrupted cache files are the most common cause of Teams loading issues. Follow these steps to clear the cache completely:

  1. Close Microsoft Teams completely by right-clicking the Teams icon in the system tray and selecting Quit
  2. Press Windows + R to open Run dialog
  3. Type %appdata%\Microsoft\Teams and press Enter
  4. Delete all folders except the Logs folder. Key folders to delete include:
    • Application Cache
    • blob_storage
    • Cache
    • databases
    • GPUcache
    • IndexedDB
    • Local Storage
    • tmp
  5. Navigate to %appdata%\Microsoft\Teams\Application Cache\Cache and delete all files
  6. Go to %localappdata%\Microsoft\Teams and delete the Current folder
  7. Restart your computer
  8. Launch Microsoft Teams and sign in
Pro tip: Create a batch file to automate cache clearing. Save the following commands as clear_teams_cache.bat and run as administrator when needed.
@echo off
taskkill /f /im Teams.exe
timeout /t 3
rd "%appdata%\Microsoft\Teams\Application Cache" /s /q
rd "%appdata%\Microsoft\Teams\blob_storage" /s /q
rd "%appdata%\Microsoft\Teams\Cache" /s /q
rd "%appdata%\Microsoft\Teams\databases" /s /q
rd "%appdata%\Microsoft\Teams\GPUcache" /s /q
rd "%appdata%\Microsoft\Teams\IndexedDB" /s /q
rd "%appdata%\Microsoft\Teams\Local Storage" /s /q
rd "%appdata%\Microsoft\Teams\tmp" /s /q
echo Teams cache cleared successfully
pause

Verification: Teams should load normally within 30 seconds. Check that all your teams and channels appear correctly.

2

Reset Network Configuration and Proxy Settings

Network configuration issues can prevent Teams from loading properly. Reset your network settings using these commands:

  1. Press Windows + X and select Windows PowerShell (Admin)
  2. Run the following commands one by one:
# Reset Winsock catalog
netsh winsock reset

# Reset TCP/IP stack
netsh int ip reset

# Flush DNS cache
ipconfig /flushdns

# Release and renew IP configuration
ipconfig /release
ipconfig /renew

# Reset Windows firewall
netsh advfirewall reset
  1. Check proxy settings in Teams:
    • Open SettingsNetwork & InternetProxy
    • Ensure Automatically detect settings is enabled
    • Disable Use a proxy server unless required by your organization
  2. Configure Teams proxy settings:
    • Open Teams and go to SettingsGeneral
    • Under Application, check proxy configuration
    • Select Auto-detect proxy or configure manually if needed
  3. Add Teams to Windows Defender exclusions:
    • Open Windows SecurityVirus & threat protection
    • Click Manage settings under Virus & threat protection settings
    • Add exclusions for:
      • %localappdata%\Microsoft\Teams
      • %appdata%\Microsoft\Teams
  4. Restart your computer and test Teams
Warning: Resetting network configuration will remove custom network settings. Document any custom configurations before proceeding.

Verification: Run ping teams.microsoft.com to confirm connectivity. Teams should connect and sync properly.

3

Repair or Reinstall Microsoft Teams

If cache clearing doesn't resolve the issue, repair or reinstall Teams completely:

Option A: Repair Teams Installation

  1. Press Windows + I to open Settings
  2. Navigate to AppsApps & features
  3. Search for Microsoft Teams
  4. Click the three dots menu and select Advanced options
  5. Click Repair and wait for the process to complete
  6. If repair fails, click Reset to restore default settings

Option B: Complete Reinstallation

  1. Uninstall Teams using PowerShell (removes all user data):
# Uninstall Teams for current user
Get-AppxPackage *Teams* | Remove-AppxPackage

# Uninstall Teams machine-wide installation
$TeamsPath = [System.IO.Path]::Combine($env:LOCALAPPDATA, 'Microsoft', 'Teams', 'Update.exe')
if (Test-Path $TeamsPath) {
    Start-Process -FilePath $TeamsPath -ArgumentList '--uninstall -s' -Wait
}
  1. Remove remaining Teams folders:
# Remove Teams folders
Remove-Item -Path "$env:APPDATA\Microsoft\Teams" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item -Path "$env:LOCALAPPDATA\Microsoft\Teams" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item -Path "$env:LOCALAPPDATA\Microsoft\TeamsMeetingAddin" -Recurse -Force -ErrorAction SilentlyContinue
  1. Clean Teams registry entries:
# Remove Teams registry keys
Remove-Item -Path "HKCU:\SOFTWARE\Microsoft\Office\Teams" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item -Path "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Teams" -Recurse -Force -ErrorAction SilentlyContinue
  1. Download latest Teams client from Microsoft's official website
  2. Install Teams with administrator privileges
  3. Sign in with your Microsoft 365 credentials
Pro tip: For enterprise environments, use the Teams Machine-Wide Installer (MSI) for better deployment control and management.

Verification: Teams should start cleanly with default settings. All features including chat, calls, and file sharing should work normally.

4

Fix Windows User Profile and Authentication Issues

Corrupted user profiles or authentication tokens can prevent Teams from loading. Address these issues systematically:

Clear Microsoft 365 Authentication Tokens

  1. Open Credential Manager by typing it in Start menu
  2. Click Windows Credentials
  3. Remove all entries containing:
    • Microsoft Office
    • Microsoft Teams
    • login.microsoftonline.com
    • *.sharepoint.com
  4. Click Web Credentials and remove similar entries

Reset Windows Store Cache

wsreset.exe

Repair Windows User Profile

  1. Create a new local administrator account for testing:
# Create test user account
net user TeamsTest P@ssw0rd123! /add
net localgroup administrators TeamsTest /add
  1. Sign in with the new account and test Teams installation
  2. If Teams works, the issue is profile-specific. Fix the original profile:
# Reset user profile registry
$UserSID = (Get-WmiObject -Class Win32_UserAccount -Filter "Name='$env:USERNAME'").SID
Remove-Item -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\$UserSID.bak" -Force -ErrorAction SilentlyContinue

Fix Office Activation Issues

  1. Reset Office activation state:
# Navigate to Office installation directory
cd "C:\Program Files\Microsoft Office\Office16"
# or for Office 365: cd "C:\Program Files\Microsoft Office\root\Office16"

# Reset Office activation
cscript ospp.vbs /dstatus
cscript ospp.vbs /unpkey:XXXXX  # Replace XXXXX with last 5 digits of product key
cscript ospp.vbs /act
  1. Clear Office credentials:
# Clear Office credential cache
Remove-Item -Path "$env:LOCALAPPDATA\Microsoft\Office\16.0\Wef" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item -Path "$env:APPDATA\Microsoft\Office\Recent" -Recurse -Force -ErrorAction SilentlyContinue
Warning: Modifying user profiles can affect other applications. Create a system restore point before making changes.

Verification: Sign out and back in to Windows. Teams should authenticate properly and load all organizational data.

5

Advanced System Repair and Performance Optimization

For persistent issues, perform comprehensive system repairs and optimize performance for Teams:

Run System File Checker and DISM

# Check system file integrity
sfc /scannow

# Repair Windows image
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# Reset Windows Update components
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Optimize System Performance for Teams

  1. Increase virtual memory:
# Set virtual memory to system managed
$cs = Get-WmiObject -Class Win32_ComputerSystem
$cs.AutomaticManagedPagefile = $true
$cs.Put()
  1. Disable unnecessary startup programs:
# Disable non-essential startup programs
Get-CimInstance -Class Win32_StartupCommand | Where-Object {$_.Command -notlike "*Teams*" -and $_.Command -notlike "*Office*"} | ForEach-Object {
    Write-Host "Consider disabling: $($_.Name) - $($_.Command)"
}

Configure Teams Performance Settings

  1. Modify Teams desktop configuration:
# Create or modify %appdata%\Microsoft\Teams\desktop-config.json
{
  "appPreferenceSettings": {
    "disableGpu": false,
    "enableLogging": false,
    "logLevel": "info"
  },
  "currentWebLanguage": "en-us",
  "homeTenant": "",
  "theme": "default"
}
  1. Set Teams process priority:
# Create scheduled task to set Teams priority
$Action = New-ScheduledTaskAction -Execute 'powershell.exe' -Argument '-Command "Get-Process Teams -ErrorAction SilentlyContinue | ForEach-Object { $_.PriorityClass = \"High\" }"'
$Trigger = New-ScheduledTaskTrigger -AtLogOn
$Settings = New-ScheduledTaskSettingsSet -AllowStartIfOnBatteries -DontStopIfGoingOnBatteries
Register-ScheduledTask -TaskName "TeamsHighPriority" -Action $Action -Trigger $Trigger -Settings $Settings -User $env:USERNAME

Registry Optimization for Teams

Warning: Back up your registry before making changes. Incorrect modifications can cause system instability.
# Backup registry
reg export HKLM\SOFTWARE\Microsoft\Teams TeamsRegistry_Backup.reg

# Optimize Teams registry settings
New-ItemProperty -Path "HKCU:\SOFTWARE\Microsoft\Office\16.0\Teams" -Name "PreventFirstLaunchAfterInstall" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKCU:\SOFTWARE\Microsoft\Office\Teams" -Name "DisableAutoStart" -Value 0 -PropertyType DWORD -Force

Verification: Monitor Teams performance using Task Manager. CPU usage should be under 10% during normal operation, and memory usage should stabilize under 500MB.

Verification

After applying any of the above methods, verify the fix by performing these checks:

  1. Launch Microsoft Teams and confirm it loads within 30 seconds
  2. Sign in successfully and verify all teams and channels appear
  3. Test core functionality: send a chat message, join a test meeting, and share a file
  4. Check Teams performance in Task Manager - CPU usage should be reasonable (under 15%)
  5. Verify Teams starts automatically on system boot if configured
  6. Run this PowerShell command to check Teams process health:
Get-Process Teams -ErrorAction SilentlyContinue | Select-Object Name, CPU, WorkingSet, StartTime | Format-Table -AutoSize

Teams should show normal resource usage and a recent start time. If issues persist, proceed to the troubleshooting section.

Still Having Issues?

If the above methods didn't resolve the Teams loading issue, try these advanced troubleshooting steps:

Check Windows Event Logs

Open Event Viewer and check Windows LogsApplication for Teams-related errors. Look for error codes like 0x80070005 (Access Denied) or 0x80004005 (Unspecified Error).

Test with Different Network

Connect to a different network or use mobile hotspot to isolate network-specific issues. If Teams works on different network, contact your network administrator about firewall or proxy configurations.

Safe Mode Testing

Boot Windows in Safe Mode with Networking and test Teams installation. If Teams works in Safe Mode, a third-party application is likely causing conflicts.

Contact Microsoft Support

If all methods fail, collect diagnostic information using the Teams diagnostic tool and contact Microsoft Support. Include system specifications, error logs, and steps already attempted.

Alternative Access Methods

Use Teams web version at teams.microsoft.com as a temporary workaround while resolving desktop application issues. The web version provides most functionality without requiring local installation.

Frequently Asked Questions

Why does Microsoft Teams get stuck on the loading screen?
Teams typically gets stuck loading due to corrupted cache files, network connectivity issues, or authentication problems. The most common cause is corrupted temporary files in the %appdata%\Microsoft\Teams folder. Clearing the cache by deleting all folders except 'Logs' resolves this issue in most cases. Other causes include outdated Teams client, proxy configuration problems, or Windows user profile corruption.
How do I completely uninstall and reinstall Microsoft Teams?
To completely remove Teams, first uninstall it through Windows Settings > Apps > Apps & features. Then use PowerShell to remove remaining files: delete folders in %appdata%\Microsoft\Teams and %localappdata%\Microsoft\Teams. Clean registry entries under HKCU\SOFTWARE\Microsoft\Office\Teams. Download the latest Teams installer from Microsoft's website and install with administrator privileges. This ensures a clean installation without leftover configuration files.
What network ports does Microsoft Teams require to function properly?
Microsoft Teams requires several network ports: TCP 443 and 80 for HTTPS traffic, UDP 3478-3481 for media traffic, and TCP 50000-59999 for Teams meetings. Ensure your firewall allows these ports and that Teams.exe is added to Windows Defender exclusions. Corporate networks may require additional proxy configuration. If Teams works on mobile data but not corporate network, contact your IT administrator about firewall rules.
Can I use Microsoft Teams web version if the desktop app won't load?
Yes, the Teams web version at teams.microsoft.com provides most functionality when the desktop app fails. You can access chat, participate in meetings, share files, and collaborate on documents. However, some features like background blur in meetings, local recording, and desktop notifications may be limited. The web version works in Chrome, Edge, Firefox, and Safari browsers and serves as an excellent temporary workaround while troubleshooting desktop app issues.
How do I fix Teams authentication and sign-in problems?
Teams authentication issues often stem from expired tokens or corrupted credentials. Open Credential Manager and remove all entries containing Microsoft Office, Teams, or login.microsoftonline.com. Clear Office credentials by deleting the %localappdata%\Microsoft\Office\16.0\Wef folder. Reset Office activation using cscript ospp.vbs commands if you have Office 365. Sign out of all Microsoft services in your browser, clear browser cache, then sign back in to Teams. For persistent issues, create a new Windows user account to test if the problem is profile-specific.

Which method worked?

Vote to help others

Official Resources

About the Author

Emanuel DE ALMEIDA

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...