This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
This issue happens everytime the person who is sharing the screen switches. Whenever the switch happens, the screen will freeze on the last image before the screen was switched to another user. The sound works still but the screen will stay frozen on that last image of the users screen. The only fix is to end Teams via task manager and it restarts the app and adds back to the call. This happens everytime the screen share is switched to another user. Not sporadic at all. The old Teams works fine but Teams keeps forcing me to the "New" Teams. This issue needs fixed. I have seen many other people online noting the same issue. I have updated all drivers and unistalled Teams and re-installed. Nothing fixes it. What is going on with this "New" Teams.
Displaying your screen content to others during a Teams meeting or call for collaboration
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.
Having the same issue here with users on Remote Desktop
Teams Hangs
We resort to Ending the Task and re-launching Teams
Same here! I have a user that when he shares his RDP window or PowerBI, teams either freezes completely or just crashes outright. It seems the more memory consuming the application, the worse the freezing is.
Exactly the same issue here. It's repeatable and extremely frustrating.
Same issue for me, this is very troublesome
Same issue here. Very embarrassing and not very professional that I cannot share things effectively. It doesn't let me leave the call either. Everything freezes. Why force the change when the new version isn't ready. There's a notable silence here from MS too....