Teams has started using 100% CPU

Nick Perza 0 Reputation points
2023-06-20T18:01:01.87+00:00

Teams has just recently started consuming all of the available CPU on my Windows 11 PC. Total CPU is at 100% with Teams consuming anywhere from 60-98%. This is resulting in a very sluggish user experience making my PC nearly unusable. When I kill the Teams process via Task Manager, CPU utilization drops to <20%. I've been using Teams on this PC for years without any prior issues.

Windows 11 Pro 22H2 (OS build 23481.1000)

Teams Version 1.6.00.12455 (64-bit)

User's image

I've performed the recommended troubleshooting steps below:

  1. Checked for Windows & Teams updates
  2. Disabled GPU hardware acceleration
  3. Disabled animations
  4. Disabled read receipts
  5. Disabled "Register Teams as the chat app for Office"
  6. Cleared the Teams cache (%appdata%\Microsoft\teams)
  7. Repaired & Reset Microsoft Teams
  8. Uninstalled/Reinstalled Teams (along with manually deleting all Teams files)
  9. Rebooted the PC

CPU utilization immediately jumps to 100% upon launching Teams, even just sitting at the login screen before signing into my Teams account. As a workaround, I'm using the browser-based version without any issues.Another user recently reported a similar issue:

Another user recently reported a similar issue:

https://answers.microsoft.com/en-us/msteams/forum/all/why-has-teams-just-started-using-100-cpu-and/2ddbaef6-da5c-4c02-927f-3143fedfbf71

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,261 questions
{count} votes

5 answers

Sort by: Most helpful
  1. Nick Perza 0 Reputation points
    2023-06-21T14:57:06.7533333+00:00

    Thanks @JimmyYang-MSFT . I appreciate your response. Unfortunately, I've already tried your suggestions without any improvement.

    No one in our organization has reported the issue, but only a few of us in IT are running Windows 11. Most users are still on Windows 10. I'm probably the only one running the latest version of Windows 11 (Insider Preview). I did test on another machine running an older version of Windows 11 (same/latest version of Teams) and was unable to reproduce the issue. For now, the issue is isolated to my main device. I'll try updating another machine to the same version of Windows 11 to see if it triggers the issue.

    I'll proceed with opening a ticket with Microsoft Support.


  2. Nick Perza 0 Reputation points
    2023-06-21T15:00:06.1433333+00:00

    Update:

    I manually checked for another Teams update and one became available this morning. I installed the update and the CPU spiked to 100% for the first minute or so and has since normalized. Hopefully this update has permanently resolved the issue. The bizarre thing is that Teams prompted that it was installing an update and then restarted the application, but the version number didn't rollover.


  3. Michael Daw 0 Reputation points
    2023-06-22T14:16:46.1333333+00:00

    If anyone finds a solution, please share! Hopefully the problem is fixed in a new update soon.

    0 comments No comments

  4. Brad Campbell 0 Reputation points
    2023-11-29T20:28:36.5766667+00:00

    Having Same Issue, was using the "New Teams web version" up until October when I switched back to the Desktop version and I constantly have to exit Teams because it takes over my CPU at 100%. Haven't tried any of the recommended steps yet, but I think I will just go back to Web App. Windows 11 Ent 23H2

    0 comments No comments

  5. JK 0 Reputation points
    2023-12-19T16:46:26.0233333+00:00

    My instance of Teams (currently version 1.6.00.33567) seems to start using very high CPU after a meeting ends. It remains high (~ 25%) which is ridiculous on a 32 GB high-end i7 microprocessor. That is equivalent to video editing. The temporary "fix" is to log off Teams and then log back in. There is NO reason for Teams to consume this much CPU when NOTHING is active. Microsoft, I think the clue should be that a meeting does this (again still very high after the meeting ends and I exit). PLEASE fix. Thank you.