MS Teams Helper using up >100% of CPU MacBook

Anonymous
2020-05-22T10:17:30+00:00

Since the latest update of MS Teams (current version 1.3.00.9271 updated on 07/05/20) on a MacBook (early 2015), every time I now join a Teams call, the Microsoft Teams Helper is using >100% of CPU and causing the laptop to overheat. I have disabled the GPU acceleration as seen on some other message boards but this has no impact, and could do with a fix for this ASAP.

Many thanks in advance.

Microsoft Teams | Microsoft Teams for business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

218 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-09-20T09:26:46+00:00

    Hi !

    Unfortunatly, I don't have a Roccat mouse pluged to unplug to make Teams works better T_T

    Years of Slack without an issue, 2 months of Teams and countless of bugs... (not mentioning dozens of bugs in outlook, sharepoint, ...)

    I remember a time when Microsoft was great, it was with Windows XP, make Windows great again... plz...

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-10-25T11:53:03+00:00

    just an update for the people encountering the problem on Mac (apparently M1/M2):

    In the classic teams, you could rename the node_module to make it work (previous posting of me).

    In the "New Teams" this trick doesn't work anymore, but it has exactly the same problem.

    I solved it by going to Mac's "System Settings", "Privacy & Security", "Input Monitoring" and making sure, that it is disabled for Teams. So far I did not encounter any missing functionality because of it, but instead I can keep using my Roccat Kone mouse.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-11-21T16:59:23+00:00

    its not any better so far with my M2 MacBook Air/

    Was this answer helpful?

    0 comments