Hi, We experience the following: Person "Alice" starts a Teams-Screensharing with "Bob" via the Chat->Screensharing The mouse of "Alice" is now reacting slow and less usable. It is shaking / flickering. When Alice moves the mouse, the cursor lags behind or shakes. When "Alice" gives "Bob" control, Alice cannot move her own Mouse-pointer anymore. Bob, who has control, can move the mouse and work on Alice' desktop. Alice cannot move her mouse, so she can't revoke screensharing and also not take away control from Bob. Only if Bob gives up control, Alice can use her desktop again. When the presenter tries to move her mouse pointer, it is shaking, flickering, slow, dragging. When in addition "giving control" to someone, the mouse is unusable and the remote controller has all control, whereas the presenter loses all mouse control. (adding synonyms here for people who also search for this problem) Circumstances under which this happens: Microsoft Teams runs on two PCs "PC-A" and "PC-B" in the same local company network. The PCs are close to each other, no network latency. PC-A (Alice) shares the desktop with PC-B (Bob). Alice sits physically in front of an Acer Laptop and uses VPN, a home internet connection, and Microsoft Remote-Desktop (mstsc.exe) to connect to her "PC-A", which is at the company. Between the Acer Laptop and PC-A there is network latency and limited bandwith as her internet at home is consumer-grade. Bob sits physically in front of his "PC-B". Bob could also be logged in via VPN&remote-desktop like Alice if he works from home-office. The problem is the same. All are Windows 10 with recent patch-level. The two screens of her Laptop and PC-A have different resolutions. Teams is a fresh install a week ago. If Alice and Bob sit physically in front of PC-A and PC-B, the problem does not occur. Then, there are mutliple mouse-pointers shown and screen sharing with Microsoft Teams works fine. I suspect it is related to remote desktop (mstsc.exe) and the way that the mouse is moved when being remotely connected. Screen resolutions differ, too. Did anybody experience this, too? Any idea how to resolve it? We could start Teams on the Acer Laptop, but that would open other problems. kind regards Leo

This is the exactly solution for this issue. It works!

My work around for this issue was to have the user start the team meeting on the local machine and once the meeting started he could then remote to the other machine. Ty...

Same issue: when presenting a screen on Zoom or Teams in an RDP session the mouse is slow/lagging/jittery and jumpy. Impossible to use. Rebooting the remote computer (office computer) temporarily fixes the problem. I didn't need to reboot my local (home) computer. This does not happen when sharing a screen through Zoom or Teams logged in from my local (home) computer (i.e., not through RDP). If anyone has figured out a permanent solution, please post. In case it matters, there are no issues when sharing a screen through Zoom or Teams logged in from my local computer even if I still have an RDP session opened and minimized (so that I'm working from my home desktop).

I have seen that issue in both Skype for Business and Teams. SfB just recently and Teams off and on for the last 2 years. There seems to be a memory or resource leak. Closing the app completely and restarting it generally seems to fix it though.

Hi @Marvin, Thanks for the clarification. As both Remote Desktop and Teams are from Microsoft, maybe testing Teams when logged in via Remote Desktop is something you could do. Update from today with another piece of information that may help: The bad mouse-flicker still happened today between Alice and Bob as described above. We noticed that "Alice" had on her computer not authorized Windows Defender Firewall yet to allow connections outgoing from "Teams.exe". This can happen because the Defender Firewall only asks once, when first sharing a screen, if Teams should be allowed to do outgoing connections. When the user clicks "cancel" on the Firewall dialog, it never pops up again - but screensharing and audio connections still work, but more badly. After logging in as Admin on Alice' computer and configuring Windows Defender Firewall to allow teams.exe, her experience improved a lot. So the cause may be related to how Teams and Firewall do work together. I will track this further and keep adding information if I get them for any other person out there experiencing this issue. best Leo

Mouse of presenter slow/unusable/flickering when sharing screen in Microsoft Teams. Unusable when giving control. Via Remote desktop

Anonymous

Hi,

We experience the following:

Person "Alice" starts a Teams-Screensharing with "Bob" via the Chat->Screensharing
The mouse of "Alice" is now reacting slow and less usable. It is shaking / flickering. When Alice moves the mouse, the cursor lags behind or shakes.
When "Alice" gives "Bob" control, Alice cannot move her own Mouse-pointer anymore. Bob, who has control, can move the mouse and work on Alice' desktop. Alice cannot move her mouse, so she can't revoke screensharing and also not take away control from Bob. Only if Bob gives up control, Alice can use her desktop again.

When the presenter tries to move her mouse pointer, it is shaking, flickering, slow, dragging. When in addition "giving control" to someone, the mouse is unusable and the remote controller has all control, whereas the presenter loses all mouse control.

(adding synonyms here for people who also search for this problem)

Circumstances under which this happens:

Microsoft Teams runs on two PCs "PC-A" and "PC-B" in the same local company network. The PCs are close to each other, no network latency. PC-A (Alice) shares the desktop with PC-B (Bob).
Alice sits physically in front of an Acer Laptop and uses VPN, a home internet connection, and Microsoft Remote-Desktop (mstsc.exe) to connect to her "PC-A", which is at the company. Between the Acer Laptop and PC-A there is network latency and limited bandwith as her internet at home is consumer-grade.
Bob sits physically in front of his "PC-B".
Bob could also be logged in via VPN&remote-desktop like Alice if he works from home-office. The problem is the same.
All are Windows 10 with recent patch-level.
The two screens of her Laptop and PC-A have different resolutions.
Teams is a fresh install a week ago.

If Alice and Bob sit physically in front of PC-A and PC-B, the problem does not occur. Then, there are mutliple mouse-pointers shown and screen sharing with Microsoft Teams works fine.

I suspect it is related to remote desktop (mstsc.exe) and the way that the mouse is moved when being remotely connected. Screen resolutions differ, too.

Did anybody experience this, too?

Any idea how to resolve it?

We could start Teams on the Acer Laptop, but that would open other problems.

kind regards

Leo

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

50 answers

Anonymous

2020-07-24T18:01:12+00:00

This is the exactly solution for this issue. It works!
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2020-05-28T14:25:50+00:00

My work around for this issue was to have the user start the team meeting on the local machine and once the meeting started he could then remote to the other machine.

Ty...
Was this answer helpful?

0 comments No comments
Anonymous

2020-05-21T18:54:11+00:00

Same issue: when presenting a screen on Zoom or Teams in an RDP session the mouse is slow/lagging/jittery and jumpy. Impossible to use. Rebooting the remote computer (office computer) temporarily fixes the problem. I didn't need to reboot my local (home) computer. This does not happen when sharing a screen through Zoom or Teams logged in from my local (home) computer (i.e., not through RDP). If anyone has figured out a permanent solution, please post. In case it matters, there are no issues when sharing a screen through Zoom or Teams logged in from my local computer even if I still have an RDP session opened and minimized (so that I'm working from my home desktop).
Was this answer helpful?

0 comments No comments
Anonymous

2020-04-22T15:25:55+00:00

I have seen that issue in both Skype for Business and Teams. SfB just recently and Teams off and on for the last 2 years. There seems to be a memory or resource leak. Closing the app completely and restarting it generally seems to fix it though.
Was this answer helpful?

0 comments No comments
Anonymous

2020-03-27T16:51:33+00:00
Hi @Marvin,

Thanks for the clarification. As both Remote Desktop and Teams are from Microsoft, maybe testing Teams when logged in via Remote Desktop is something you could do.

Update from today with another piece of information that may help:
1. The bad mouse-flicker still happened today between Alice and Bob as described above.
2. We noticed that "Alice" had on her computer not authorized Windows Defender Firewall yet to allow connections outgoing from "Teams.exe". This can happen because the Defender Firewall only asks once, when first sharing a screen, if Teams should be allowed to do outgoing connections. When the user clicks "cancel" on the Firewall dialog, it never pops up again - but screensharing and audio connections still work, but more badly.
3. After logging in as Admin on Alice' computer and configuring Windows Defender Firewall to allow teams.exe, her experience improved a lot.
So the cause may be related to how Teams and Firewall do work together.

I will track this further and keep adding information if I get them for any other person out there experiencing this issue.

best

Leo
Was this answer helpful?

0 comments No comments