The honest first response for most Microsoft Teams problems is clearing the Teams cache, because a substantial fraction of Teams issues — sign-in failures, missing meetings, channels not loading, notifications inconsistencies, app crashes, mysterious errors — are resolved by cache cleanup. Teams is notoriously cache-heavy, accumulating substantial local data that can become corrupted, stale, or inconsistent in ways that produce confusing problems. Most “Teams not working” articles bury cache clearing in the middle of long troubleshooting lists, leading users to try elaborate fixes before reaching the step that actually resolves their issue.
This matters because the time investment for cache clearing is small (under five minutes), the success rate for common Teams issues is high, and the alternative troubleshooting steps for the issues that cache clearing addresses are dramatically more time-consuming. Leading with cache clearing produces better outcomes than treating it as a later step.
This guide is structured around cache-first troubleshooting and then targeted fixes for issues that cache clearing does not resolve. For broader context on the troubleshooting and fixes catalog, our complete guide to fixing errors covers the approach across many tool categories.
Step 0: Determine Which Teams Client You Are Using
Before any troubleshooting, identify which version of Teams you are using because procedures differ. Microsoft has been migrating users from “Classic Teams” to the “New Teams” client over recent years, and both clients may exist on the same computer with different troubleshooting requirements.
The New Teams client (introduced in 2023) is the current default. The application icon and interface have been redesigned, and the underlying technology is genuinely different from classic Teams. Cache locations and troubleshooting commands differ from classic Teams.
Classic Teams (deprecated but still present on some systems) is the older version. Microsoft has been forcing migration to New Teams, but some users still have classic Teams installed and may be inadvertently using it.
To verify which version you have: click the Teams app icon and look at the application’s appearance. New Teams has a cleaner interface with redesigned navigation. Classic Teams has the older interface with the heavier feature density. The application title or About menu confirms which version is running.
For most users in 2026, New Teams is the version that matters. The troubleshooting below covers New Teams primarily, with notes where classic Teams procedures differ. Microsoft’s Teams support documentation also clarifies version-specific procedures for cases where this matters.
Step 1: Clear Teams Cache (Resolves Most Issues)
Clear the Teams cache before trying anything else. This is the single most effective Teams troubleshooting step.
For New Teams on Windows: completely exit Teams (right-click the system tray icon → Quit, then verify no Teams processes remain in Task Manager). Open File Explorer and navigate to %localappdata%PackagesMSTeams_8wekyb3d8bbweLocalCache. Delete the contents of this folder (not the folder itself). Restart Teams.
For New Teams on Mac: completely quit Teams (Teams menu → Quit Teams, or Cmd+Q). Open Finder → Go → Go to Folder → enter ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams. Delete the cache subfolders within. Restart Teams.
For Classic Teams on Windows: completely exit Teams, then navigate to %appdata%MicrosoftTeams. Delete the contents of subfolders including Cache, blob_storage, databases, GPUCache, IndexedDB, Local Storage, and tmp. Do not delete the parent Teams folder itself. Restart Teams.
For Classic Teams on Mac: completely quit Teams, navigate to ~/Library/Application Support/Microsoft/Teams. Delete the contents of cache-related subfolders, similar to the Windows process. Restart Teams.
After cache clearing, Teams must rebuild its local state on first launch. The first launch after cache clearing is slower than normal as Teams downloads channel structures, recent messages, and other state from the cloud. Allow this initial rebuild to complete before declaring the cache clearing successful or unsuccessful.
If cache clearing resolves your issue, no further troubleshooting is needed. This addresses most common Teams problems in our experience and is worth always trying first.
For users who specifically want the more aggressive version of this — completely resetting Teams while preserving the install — uninstalling and reinstalling Teams produces a guaranteed clean state at the cost of a few additional minutes of setup time. For persistent issues that simple cache clearing does not resolve, uninstall-reinstall is the appropriate next escalation.
Step 2: Check Teams Service Status
If cache clearing did not help, verify whether Teams itself is having service issues before continuing user-side troubleshooting.
Visit Microsoft 365 Service Health status pages (admin.microsoft.com for organisational admins, status.office.com for general status). Active Teams incidents are clearly indicated with affected features.
Cross-reference with downdetector.com for user-reported issues. Spikes in user reports indicate service problems even when Microsoft’s status page has not yet acknowledged them.
Check with colleagues directly. If others in your organisation are using Teams normally while you are not, the issue is on your side. If multiple colleagues are simultaneously experiencing the same problem, the issue is more likely on Microsoft’s side or specific to your organisation’s configuration.
If service status confirms a Teams-side issue, waiting for resolution is the appropriate response rather than continued troubleshooting. Microsoft typically resolves Teams incidents within hours.
Step 3: Audio and Microphone Issues After Cache Clearing
For audio-specific issues that persist after cache clearing, the troubleshooting parallels the audio stack approach.
Operating system permissions for Teams must be granted. Windows Settings → Privacy & Security → Microphone → verify Microsoft Teams has permission. Mac System Settings → Privacy & Security → Microphone → verify Teams has permission. Without OS-level permission, Teams cannot access the microphone regardless of in-app settings.
Within Teams, audio device selection matters. Click the three-dot menu in a meeting → Device Settings. Verify the correct microphone and speaker are selected. Test microphone with the test button to confirm Teams can capture audio.
Audio enhancements within Teams (noise suppression, echo cancellation) can sometimes produce unexpected effects. The default settings work for most cases, but adjusting them helps for specific situations — disabling enhancements for users with high-quality external microphones, enabling more aggressive noise suppression for users in noisy environments.
Hardware-level audio issues (Bluetooth headset mode confusion, USB device problems, driver issues) affect Teams the same way they affect other applications. Verifying microphone functionality outside Teams (Windows Voice Recorder, browser-based microphone tests) isolates whether the issue is Teams-specific or system-level. Our Zoom audio troubleshooting guide covers the audio stack approach in detail for the related video conferencing category.
Step 4: Camera Not Working in Meetings
Camera issues parallel audio issues with similar layered diagnosis.
Operating system camera permissions for Teams must be granted (Privacy & Security → Camera settings on both Windows and Mac).
Camera device selection in Teams meeting Device Settings should show available cameras. Choose the correct one if multiple are present.
Hardware-level camera issues often relate to other applications using the camera simultaneously. Cameras can only be used by one application at a time on most operating systems. If another application (Skype, browser, recording software) is using the camera, Teams cannot access it. Closing other applications resolves this conflict.
Driver issues for cameras follow the same pattern as audio drivers. Windows Update typically handles drivers; manual driver updates through Device Manager address persistent issues. For specific external cameras, the manufacturer’s driver may need to be installed manually rather than relying on Windows generic drivers.
Camera privacy switches on some laptops physically disable the camera. Check for sliding shutters, mechanical switches, or function keys that disable the camera at the hardware level.
Step 5: Sign-In and Authentication Problems
Authentication failures prevent Teams from working regardless of network or application state. These typically require account-level rather than application-level fixes.
Verify your work or school credentials. Sign in through office.com or portal.microsoft.com through a browser. Successful web sign-in confirms credentials are correct. If web sign-in also fails, the issue is at the account level rather than application level.
Multi-factor authentication issues affect Teams sign-in. If your MFA method is unavailable (authenticator app on a device you no longer have, SMS to a phone you have replaced), MFA recovery through your IT department is the appropriate response. Microsoft’s own account recovery handles personal accounts; work accounts require organisational IT involvement.
Conditional Access policies in enterprise environments can prevent sign-in from specific devices, locations, or under specific conditions. Affected sign-ins typically show specific error codes that point to conditional access. IT support is the appropriate response for conditional access blocks.
Account licensing affects Teams availability. If your organisation has changed licensing in ways that removed Teams from your account, Teams will not work for you. The user account page in admin centres shows current licensing.
Cached credentials sometimes cause persistent sign-in issues even when credentials are correct. The Windows Credential Manager (Control Panel → User Accounts → Credential Manager) holds stored credentials that may be outdated. Removing Teams-related entries from Credential Manager and signing in fresh sometimes resolves persistent authentication issues that cache clearing alone does not address.
For New Teams specifically, some sign-in issues relate to the migration from classic to new Teams. The new client may have authentication state that conflicts with classic Teams remnants. Removing both versions, restarting, and reinstalling only New Teams produces a clean state. Our Slack troubleshooting guide covers a parallel pattern in the alternative team chat category.
Step 6: Meeting Joining Failures
When other Teams features work but meetings specifically fail to join, the issue is usually network or meeting-specific.
Network configuration affects meeting connections. Teams meetings use specific UDP ports for audio and video that some networks block. Corporate firewalls, restrictive networks, or aggressive security software can prevent meeting connections while allowing chat and other Teams features.
The “Use the web app instead” option appears in some failure scenarios. The web app uses different code paths than the desktop client and sometimes works when the desktop fails. This is a viable workaround for specific meetings.
Browser-based join through the meeting link in your calendar invitation bypasses the desktop app entirely. Even users with desktop Teams problems can typically join meetings through the browser as a workaround.
For meetings hosted by external organisations (guest meetings), additional considerations apply. Your organisation may restrict guest meeting access, the meeting host may have restricted external participants, or specific configuration may be required. The error messages typically indicate what is preventing the join.
Specific meeting types (large town halls, webinars, broadcast events) have different connection requirements than regular meetings. If you can join regular meetings but not these specific types, the issue may be related to the meeting type’s specific requirements rather than your general Teams setup.
Step 7: Performance and Slowness Issues
Teams is notably resource-intensive, and performance issues are common even on adequate hardware. Several specific causes have specific fixes.
Hardware acceleration in Teams sometimes produces problems with specific graphics drivers. Toggling hardware acceleration (Teams Settings → General → Disable GPU hardware acceleration) and restarting Teams resolves some performance issues. The setting can also be re-enabled if disabling does not help.
Resource competition affects Teams performance. Teams genuinely uses substantial RAM and CPU, and on computers running close to resource limits, Teams performance degrades. Closing other applications when using Teams improves performance noticeably. Adding more RAM is the durable fix for users whose computers are genuinely resource-limited.
Teams updates sometimes introduce performance regressions. The current Teams version may be slower than the previous version under specific conditions. Microsoft typically addresses these in subsequent updates. Verifying you have the most recent Teams version (Help → Check for Updates) ensures you are not running an older version with known performance issues.
Specific Teams features impact performance differently. Many concurrent channels with active conversations, large numbers of teams with substantial content, and integrations from many third-party apps all contribute to Teams’ resource consumption. Hiding inactive teams (right-click → Hide) and removing unused integrations reduces overhead.
Background sync activity uses resources even when you are not actively using Teams. Teams syncs channels, downloads files for offline access (on supported plans), and performs other background work. For users specifically wanting minimum resource use, settings to reduce background activity exist in some areas but Microsoft has been moving toward less user control over these.
Step 8: Update and Installation Issues
When Teams fails to update properly or has installation issues, several specific fixes apply.
Teams typically updates automatically without user intervention, but sometimes updates stall or fail. Manual update attempts through Help → Check for Updates may work when automatic updates do not.
For New Teams specifically, the installation is managed through the Microsoft Store on Windows. Microsoft Store update issues affect Teams updates. Updating Microsoft Store first (Microsoft Store → Library → Get Updates) often resolves Teams update issues.
Classic Teams uses a different update mechanism that has its own issues. Manually downloading the latest Teams installer from teams.microsoft.com and installing over the existing version often resolves classic Teams update problems.
Installation failures for Teams sometimes relate to disk space, permission issues, or conflicting software. Verifying adequate disk space (at least several GB free), running the installer with administrator privileges, and checking for antivirus interference all address common installation failures.
For users in environments managed by IT (work or school computers with managed deployment), Teams updates and installation may be controlled centrally. Manual update attempts may be prevented by the management software. The appropriate response is contacting IT rather than attempting workarounds.
The dual-installation problem (both classic and new Teams present) sometimes causes confusion. Microsoft has been working on managing this transition, but specifically for users where both versions exist, choosing one and uninstalling the other reduces the chance of switching between them inadvertently. Our video conferencing software comparison covers the broader category and alternatives users sometimes evaluate during recurring Teams issues.
The Practical Recommendation
For most users in 2026 experiencing Microsoft Teams issues, the answer follows a specific sequence. Step 0: Verify which Teams client (New Teams or classic Teams) you are using because procedures differ. Step 1: Clear the Teams cache as the first response — this resolves the majority of common Teams issues and takes under five minutes. Step 2: Check Microsoft 365 service status if cache clearing did not help — actual service issues require waiting rather than user-side fixes. Step 3-4: Address audio and camera issues through the OS permissions → in-app selection → hardware verification sequence. Step 5: For authentication issues, verify credentials through web sign-in, address MFA recovery, contact IT for enterprise issues, remove cached credentials if persistent. Step 6: For meeting-specific failures, try web app as workaround, check network configuration, address meeting-type-specific issues. Step 7: For performance issues, disable hardware acceleration, address resource competition, verify update status, hide unused teams and integrations. Step 8: For update or installation issues, manual updates, Microsoft Store updates, manual installer downloads as appropriate. The wrong move is trying elaborate fixes before clearing the cache, because cache problems are the most common cause of Teams issues and the easiest to address. Lead with cache clearing, work through the targeted fixes for specific remaining issues, and the troubleshooting becomes efficient rather than extensive. Our Discord troubleshooting guide covers a related troubleshooting pattern for the alternative communication platform category.
