Microsoft Teams, Outlook, Browsers, or Office Apps Consuming Excessive CPU/Memory Resources

Indicators

• Task Manager shows Teams.exe, Outlook.exe, or browser process consuming >50% CPU sustained for several minutes
• System RAM utilisation consistently at or near 90–100% with paging file activity increasing
• Application UI becomes unresponsive, slow to render, or freezes intermittently
• Fan noise and thermal throttling on laptop hardware coinciding with app launch or video calls
• Other applications stutter or become unresponsive while the offending app is running
• High GPU usage reported in Task Manager Performance tab when hardware acceleration is active
• Teams GPU process (Teams.exe *32 or msedgewebview2.exe) appearing as separate high-resource entry in Task Manager

Likely causes

• Corrupted or oversized application cache — Teams cache can exceed several GB, causing repeated I/O and memory pressure
• GPU hardware acceleration enabled on incompatible or under-resourced GPU drivers, forcing excessive GPU/CPU context switching
• Outdated application version with known memory leak or CPU regression bugs
• Multiple simultaneous background sync operations (Outlook OST synchronisation, Teams background downloads, OneDrive sync) contending for resources
• Browser extensions or add-ins consuming excessive resources within renderer processes
• Corrupted Outlook profile or oversized OST/PST file causing repeated indexing and search failures
• Teams running in Classic (Electron) mode rather than the optimised New Teams client
• COM add-ins in Office applications failing and retrying in a tight loop

Diagnostic steps

1. Open Task Manager (Ctrl+Shift+Esc), navigate to 'Processes' tab, click 'More details' if in compact view, sort by CPU or Memory column descending. Record the exact process name, PID, CPU %, and Memory (MB) values for the top offending process(es).
   Confirms which application and which specific process (main process vs GPU process vs renderer) is consuming excessive resources, avoiding guesswork and targeting remediation correctly.
2. Open Resource Monitor (resmon.exe), navigate to CPU tab and expand 'Associated Handles' and 'Associated Modules' for the offending process. On the Disk tab, check for sustained high disk I/O from the same process — particularly reads/writes to AppData cache folders.
   Determines whether resource consumption is CPU-bound, memory-bound, or I/O-bound (e.g. cache corruption causing repeated disk reads), which directs the correct resolution path.
3. For Teams: open Settings > General and check whether 'New Teams' or 'Classic Teams' is active; note version from Help > About. For Outlook: File > Office Account > About Outlook — record full version string. For browsers: navigate to About page (edge://settings/help or chrome://settings/help) and record version.
   Confirms whether the application is on a known-buggy version with a published fix, and whether the New Teams client (which has better resource efficiency) is available to switch to.
4. Check GPU hardware acceleration status: Teams — Settings > General > 'Disable GPU hardware acceleration'; Outlook — File > Options > Advanced > Display > 'Disable hardware graphics acceleration'; Chrome/Edge — Settings > System > 'Use hardware acceleration when available'. Document current state.
   Hardware acceleration is a common cause of excessive GPU and CPU usage on systems with incompatible drivers; confirms whether it is active and a likely contributor.
5. For Office/Outlook: File > Options > Add-ins, change 'Manage' dropdown to 'COM Add-ins', click Go, review enabled add-ins. Temporarily disable all third-party add-ins, restart application, re-measure resource consumption via Task Manager.
   Isolates whether a faulty COM add-in is responsible for CPU or memory regression, as add-ins run in-process and a looping failure can peg a CPU core.
6. Use Process Explorer (Sysinternals) to capture CPU sample: right-click offending process > Properties > Threads tab to see which thread(s) are consuming CPU, view call stack to identify the module responsible.
   Provides deep diagnostic evidence of the exact code path or third-party DLL driving CPU consumption, useful for escalation to Microsoft support or vendor.

Resolution path

• 1. DISABLE HARDWARE ACCELERATION: Teams — Settings > General > check 'Disable GPU hardware acceleration', restart Teams. Outlook — File > Options > Advanced > Display > check 'Disable hardware graphics acceleration', restart Outlook. Chrome — Settings > System > toggle off 'Use hardware acceleration when available', relaunch. Edge — edge://settings/system > toggle off 'Use hardware acceleration when available', relaunch.
• 2. CLEAR TEAMS CACHE: Fully quit Teams (right-click system tray icon > Quit). Open Run (Win+R), navigate to %appdata%\Microsoft\Teams. Delete contents of: Cache, blob_storage, databases, GPUCache, IndexedDB, Local Storage, tmp (do not delete the folders themselves). Restart Teams and sign in.
• 3. UPDATE ALL AFFECTED APPLICATIONS: Microsoft 365 apps — File > Account > Update Options > Update Now. Teams — Help > Check for updates. Edge — edge://settings/help. Chrome — chrome://settings/help. Install all available updates and restart applications.
• 4. DISABLE PROBLEMATIC ADD-INS/EXTENSIONS: Outlook — File > Options > Add-ins > COM Add-ins > Go > uncheck all non-Microsoft add-ins. Browsers — navigate to Extensions page and disable all non-essential extensions. Restart and re-test resource usage.
• 5. REPAIR OUTLOOK PROFILE (if Outlook remains offender): Control Panel > Mail > Show Profiles > select profile > Properties > Email Accounts > Repair. If repair fails, create new Outlook profile via Control Panel > Mail > Add, configure account fresh, set as default.
• 6. SWITCH TO NEW TEAMS CLIENT: In Classic Teams title bar, click toggle 'Try the new Teams' or deploy via Microsoft Teams admin center update policy. New Teams uses significantly less memory and CPU than Classic Electron-based client.
• 7. APPLY OS-LEVEL RESOURCE GOVERNANCE (for persistent issues on shared systems): In Task Manager, right-click offending process > Set Priority > Below Normal as temporary measure. For VDI environments, review session host resource limits in hypervisor or AVD/WVD host pool settings.

Prevention

• Enforce automatic updates for all Microsoft 365 apps, Teams, and browsers via Group Policy or Microsoft Endpoint Manager (Intune) to ensure known performance regressions are patched promptly
• Deploy New Teams client organisation-wide via Teams Admin Center update policy, replacing Classic Teams, to benefit from substantially reduced memory and CPU footprint
• Set monthly maintenance task to clear Teams cache on endpoints via scheduled PowerShell script targeting %appdata%\Microsoft\Teams subdirectories
• Establish add-in governance policy: audit and whitelist permitted Outlook COM add-ins via Group Policy (HKCU\Software\Microsoft\Office\Outlook\Addins), blocking unlisted add-ins from loading
• Monitor endpoint performance via Microsoft Endpoint Analytics or third-party UEM tool to detect sustained high CPU/memory trends per device before users report impact
• For VDI/AVD environments, configure per-session CPU and memory limits at hypervisor layer and right-size host pool VMs based on actual concurrent user resource telemetry

Tools

• Task Manager (taskmgr.exe) — real-time CPU, memory, disk, GPU per-process monitoring
• Resource Monitor (resmon.exe) — granular I/O, handle, and network activity per process
• Process Explorer (Sysinternals) — thread-level CPU analysis and DLL/handle inspection
• Windows Performance Recorder / WPR — ETW-based CPU sampling for deep profiling
• Credential Manager (credmgr.msc) — clearing cached authentication tokens for Microsoft apps
• Office Repair (Control Panel > Programs > Microsoft 365 > Change) — repairs corrupted Office installation files
• Microsoft Support and Recovery Assistant (SaRA) — automated diagnostics and repair for Teams, Outlook, Microsoft 365

References

• Troubleshoot Microsoft Teams performance issues
• How to clear the Teams client cache
• Disable hardware graphics acceleration in Office programs
• Outlook performance troubleshooting guide
• Microsoft Support and Recovery Assistant (SaRA)
• New Microsoft Teams client overview