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

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

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

Sometimes, yes. I have learned to use the CTRL key to locate my mouse sometimes. In Control Panel > Mouse Properties > Pointer Options - at the bottom there is a checkbox for Show location of pointer when I press the CTRL key.

After you've changed it to XDDM, do other people still see your mouse pointer when you do that? I did a test by recording the session but the mouse pointer disappeared.

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!

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-08-18T07:44:23+00:00

I confirm, this solution solved my issues. Big thanks!
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
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-07-23T21:09:39+00:00

Sometimes, yes. I have learned to use the CTRL key to locate my mouse sometimes. In Control Panel > Mouse Properties > Pointer Options - at the bottom there is a checkbox for Show location of pointer when I press the CTRL key.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2020-07-23T20:51:37+00:00

After you've changed it to XDDM, do other people still see your mouse pointer when you do that? I did a test by recording the session but the mouse pointer disappeared.
Was this answer helpful?

0 comments No comments
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 No comments