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-07-23T11:27:36+00:00

    So I have found a solution that works for me (hallelujah!!).  There are a couple of references to this, but the best one I found is this one. But the essentials in case the link goes bad are:

    Microsoft has enabled (and made default) the use of a second driver model on the system being controlled:  The WDDM model.  Up to now RDP has run off the XDDM display driver model.  Microsoft provided a new policy for configuring the controlled system to use the older, tried and proven XDDM model. 

    If you have Windows 10 Pro, on the remote PC, run gpedit.msc and navigate to the following:

    Local Computer Policy

    Computer Configuration

    Administrative Templates

    Windows Components

    Remote Desktop Services

    Remote Desktop Session Host

    Remote Session Environment

    Set the Use WDDM graphics display driver for Remote Desktop Connections policy to Disabled.

    You'll need to stop and restart your RDP session. But Voila!

    Was this answer helpful?

    40+ people found this answer helpful.
    0 comments
  2. Anonymous
    2020-04-10T16:46:17+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

    Marvin, read the reports from multiple other users. This is definitly not only my problem and it stops multiple organizations from rolling out Teams, as you can read below.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-09-29T10:18:12+00:00

    Best answer! Thanks. The issue popped up today after everything worked up until yesterday. Maybe the domain operators changed some group policies. :D

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-07-13T21:30:12+00:00

    I'm 99% certain this issue is caused by the avatar that follows the mouse pointer.  It is shown as a black square when Teams is used with an RDP session.  I know this because if I share a single Application, the black square is gone and the mouse act normal.  The moment I share an entire desktop that's when the black square appears and the mouse acts erratic.

    It has got to the point I cannot possibly share my desktop because the erratic mouse movement causes all my windows to minimize when I drag a title bar (another stupid feature).  I think we're going to switch back to WebEx if Microsoft cannot solve this issue.  I don't need the stupid avatar following my pointer.  We should be able to turn that off.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-04-01T14:15:40+00:00

    We have the exact same problem - poor mouse reaction, rubberbanding as soon as the screen is shared.  Disabling the firewall did not help.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments