Share via

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

Anonymous
2020-03-26T15:19:57+00:00

Hi,

We experience the following:

  1. Person "Alice" starts a Teams-Screensharing with "Bob" via the Chat->Screensharing
  2. 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.
  3. 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

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

50 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-08-18T07:44:23+00:00

    I confirm, this solution solved my issues. Big thanks!

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-07-21T20:30:19+00:00

    IT APPEARS IT'S FINALLY FIXED!!!

    Today a new version was released / installed and for the first time in months my mouse doesn't have the black box / laggy mouse issue!

    I checked the versioning and it states:

    "You have Microsoft Teams Version 1.3.00.19173 (32-bit). It was last updated on 7/21/20."

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-04-16T14:17:05+00:00

    In respond to COVID-19, Microsoft has temporarily adjusted some features and services in Teams to avoid server overload. For Calling & Meetings service, currently HD experience is not available. And bandwidth cap has been set to 1Mbps. As remote desktop connection will consume a lot of network and computer resource, for users worked with home PC, they may not have a good experience in Teams meeting. 

    As for the recovery of Teams services, it will be influenced by the epidemic. To learn more information, please refer to the following website.

    https://news.microsoft.com/covid-19-response/

    Hi Marvin, 

    thank your for replying even though many questions come in.

    the PCs where teams is running (in above example: PC-A and PC-B) are in the same local network (same TCP/IP subnet), about 5-20 meters apart.

    Will teams use the local LAN, if possible? Is the 1Mbps cap also configured for LAN connections?

    It would be quite a waste of bandwidth, if connections would always go via your Microsoft Servers, even if the team members are in the same subnet. Especially since Teams is rolled out in scenarios where all team members are in the same enterprise network.

    The connection from remote desktop (Acer-Laptop in above example) using remote desktop to the PC-A or PC-B is not capped by anone. Our LAN is connected via fiber and a close backbone to the internet. Both ping times and bandwidth are good/excellent between PC-A and Acer-Laptop. The remote desktop connection is generally smooth and should not be the problem. 

    That said: I still believe the problem is an error in the way Teams handles the mouse when doing remote sessions.

    My gut-feeling as a win32 programmer is that different screen resolutions and mouse-movements lead to an overload when moving the mouse or trying to show the fancy "personal avatar face" around the mouse and have nothing to do with bandwidth and/or ping times. Could it be that teams is constantly (like, every millisecond) trying to track the mouse on the presenter screen and even move the mouse on the presenter screen? Could it be that teams listens to mouse-events but a bit too often and too heavy? Could it be that this causes a thread going wild in the GUI thread and then blocks the user's mouse on the presenter screen? 

    My team describes it like "something heavy hanging on your mouse" or "I can't move the mouse anymore".

    The weirdest effect is: a viewer, having "mouse control right", can move the mouse of the presenter without any problem and does not "feel it heavy".

    That is quite unfair, the viewers enjoy it, the presenters hate it.

    Regards,

    Leo

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-03-31T16:22:59+00:00

    Update:

    It is also happening with users that have the Firewall unlocked.

    kind regards

    Leo

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-03-27T12:12:20+00:00

    Hi Leo,

    Based on your description, this issue doesn't occur when user doesn't use remote desktop connection. In this scenario, the issue should be related with remote desktop function instead of Teams request control function. Regarding the remote desktop feature, it's out of our knowledge base and support boundary since we focus on Teams services and issues. I'll try to consult our related team to check if they have any experience. But still, for users, it's suggested to control their own PCs to share the screen with each other.

    Regards,

    Marvin

    2 people found this answer helpful.
    0 comments