Forum Discussion
FcoManigrasso
Jan 20, 2023Iron Contributor
MS Teams crashes, slow performance and high CPU/Memory use - Troubleshooting
It's already known that the MS Teams client causes sometimes performance issues. That's something that happens less often after any MS update. But, still, it happens and there are certain things that...
FcoManigrasso
May 10, 2023Iron Contributor
Have you tried to disable the GPU hardware acceleration?
On the other hand, you say that your machine is a Company controlled one. Do you know if you're permanently connected to a VPN? Did you test the performance connected to another network?
If your Company allows that, ( it depends of the Teams update policy and Office update channel ), you could try also the New Teams Preview client... It works a lot better.
On the other hand, you say that your machine is a Company controlled one. Do you know if you're permanently connected to a VPN? Did you test the performance connected to another network?
If your Company allows that, ( it depends of the Teams update policy and Office update channel ), you could try also the New Teams Preview client... It works a lot better.
Anonymous
May 11, 2023Updates get pushed to us, but we are still able to control a lot because I'm on the engineering org. I have tried most things like disabling GPU acceleration, the issue is ongoing for so long all my team members just wait for me to leave and rejoin the meeting. Sometimes the lag will go away for a few moments, so it feels like something is queuing up. Turning off VPN appears to make a small difference to how quickly it manifests, but does not really change things. Also does it when plugging into the fibre network while in our labs or in the office in the city.
I am running through the intel driver updates once more - (this has been a problem for about a year) but I think you are onto something. I may be able to install the preview client, that's the best bet I think.
I am running through the intel driver updates once more - (this has been a problem for about a year) but I think you are onto something. I may be able to install the preview client, that's the best bet I think.
- FcoManigrassoMay 11, 2023Iron ContributorYeah, probably it's the best bet in your case.
It could be also a network blocker, ( proxy, firewall... ), and that could be traced with Fiddler. But taking in mind that you're the only one affected by this issue, I don't think that there will be the root cause. Or even a local anitvirus... But again, I guess all the users will have the same configuration.
Just thinking loud... And if some GP was missconfigured/propagated in your device? Have you tried a "gpupdate /force" ? ( From cmd as admin ).
There're so many things to check in this kind of scenarios, but you already did most of them as per your description.
Hope that you find the fix! And if there's something unusual that could help to the community, we'll appreciate if you post it 🙂- AnonymousMay 22, 2023Solved for me.
I was going to try the beta client, but not wanting to mess with logins again after re-installing clean (my memory and passwords is terrible.) I instead solved it by updating the graphics drivers.
1. I installed the intel driver updater utility from the intel website - it requires a reboot to install and is a unusual app that uses your browser as a user interface. And that told me that the graphics driver did need an update.
2. After letting that intel graphics driver update I rebooted again anyway before resuming my day.
And now I have in the last week had zero issues, even noticing that other people are lagging out in their meetings, when mine is rock solid. I even had a 3 hour long pair programming session, which was impossible before. Previously my machine would hang after between 40 minutes and an hour in almost any meeting. I can only guess that MS Teams was sending too much workload to the graphics card for it to handle and the updated driver addresses the workload better.- Scott_JiangMay 22, 2023Copper Contributor
Deleted
Thank you very much for your sharing!
I just upgraded the graphic driver as you instructed and completed an 1-hour meeting. It seems like it works perfectly
-Scott