TeamViewer high cpu usage(10-20%) when IDLE
Comments
-
This issue has re-appeared again on the latest V15.40.8 update. 😫
My Surface Pro 8 and another Family PC both now have/had this high CPU usage issue (~25%). All are Windows 11 22H2.
The "Disable hardware acceleration" setting does seem to have fixed it, but I am unsure if that has a detrimental effect when I connect to the hosts.
0 -
Yes, the issue reappeared with 15.40.8 , same thing on Ryzen 7 4750G desktop, using 10% CPU doing nothing. I am going to disable automatic updates... The solution for me was to disable hw acceleration, all logging and restarting the service. Please fix it.
0 -
Not solved, it started using CPU again, 8 - 9% while doing nothing. I wish there was an option to reverse to previous version... I'm just going to stop using it for now.
0 -
Registered my account to the community here just to say this is happening to me too. Very noticeable high cpu usage. I close teamviewer and/or teamviewer service, it is fine for up to 10 minutes, then it is high cpu again. Only started happening in the last update -- I can remember because the icon suddenly is different right when the high cpu usage started happening.
I'm unsure if this relates or not, but this is on a Lenovo Thinkpad T580
0 -
I am having the exact same problem. My Asus laptop goes crazy with fans on max. 25-30% CPU usage.
0 -
I also have this problem daily, I use my PC to access my laptop that's in another room.
(Team viewer not running, just.. in bottom right icons)
Then I hear my fans going at 100% CPU at 100%.. (but laptop is not hot) Open task manager and team-viewer is using 30-40% of the CPU but shown twice.
I think this did happen before but since the last update it is now a constant thing. I guess I will try reinstalling the program.
0 -
I am also experiencing CPU usage of 25-30% when Teamviewer is idle - Windows 11 22H2 on a ThinkPad T580.
0 -
I am also experiencing CPU usage of 25-30% when Teamviewer is idle - Windows 10 22H2 on a Dell Inspiron 7559. 😕
0 -
It would be really nice if Teamviewer could solve this problem....
Teamviewer always between 20 & 30%
0 -
I use Windows 10 and 11. TeamWiever consumes 20-25% CPU power when idle alone. This ensures permanent loud fan noise. Can anything be done there?
0 -
Uninstall 15.40.8, install 15.39.6 and disable auto-update will "fix" it.
Version 15.41 should fix this permanently. Planned release: 25th April 2023.
Patrick
1 -
Thanks Patrick, looking for ward to the update.
0 -
where can I download 15.39.6? I couldn't find it, just version 14.
0 -
You've got PM.
0 -
The new version was released and, oh boy, is the new FullClient bad...
The Host however seems to be fine.
For the moment I'd either stay with version 15.39.6 on the FullClient or change the design to the old one. However that's prevented by the "Disable Teamviewer shutdown" policy - so either disable that policy, or force close using TaskManager :)
I'm extremely disappointed, to say the least.
1 -
Hi all,
Thank you all for your trust and patience.
The high CPU usage has been improved with version 15.41.7.
Could you please update your clients to version 15.41.7 and let us know if you see the improvements on your devices, too?
Thanks a lot in advance for your feedback.
/JeanK
Community Manager
0 -
This problem is persisting with version 15.42.7 wiht hardware acceleration disabled on both the source and target computers. Any update on when the high CPU problem will really be resolved?
0 -
The issue was resolved and seems to have come back.
Thats ridiculous imho. I was so excited when we moved to TeamViewer by the end of last year. But it’s absolutely disgusting how many issues we’ve been facing in that timespan. And now a crucial issue coming back again, (battery drain, performance issues, fans ramping up) really makes me angry!
If this is not getting fixed MUCH FASTER than the last time, we really need to think about taking actions. It’s unacceptable to manage 5500 devices and constantly having issues and enabling/disabling updates every second update…
Hiddious.
0 -
15.42.8 has been released. Unfortunately there's no changelog published yet, so I wonder if this issue has been adressed?
Have you updated already? I'm quite hesitant on reenabling our automatic updates, because rolling back all our clients has been a pain in the **bleep**:) And I can't check it on my end because me personally wasn't effected by the bug.
0
