VMTN

It works, No more mouse issues while RDPing into windows 1903 and using linux kde vm inside vmware. Thank you very very much for this tip.

Thanks for adding this info. Unfortunately, it does not affect the problem in my environment. Is it possible that you modified some other configuration setting at the same time you disabled WDDM for remote desktop connections?

I'm glad someone is having some luck with this.

That was the same setting described by @jfred90 , I'm disabled too some weeks ago.

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v fEnableWddmDriver /t reg_dword /d 0 /f

GPEDIT.msc

Local Computer Policy

Computer Configuration

  Administrative Templates

   Windows Components

    Remote Desktop Service

     Remote Desktop Session Host

       Remote Session Environment

        Use WDDM graphics display driver for Remote Desktop Connections  to DISABLED

Worked for me.  Gee it's nice to get back to having full control of the cursor.  Thanks!
The above needs to be done on the v1903 controlled (e.g., remote) system, by the way.

But no reboot is needed.  Just disconnect and reconnect RDP.

-Noel

>Use WDDM graphics display driver for Remote Desktop Connections  to DISABLED

This step is done on host or guest?

Host side

Just press win+r keys, type gpedit.msc and follow previous posts, no need for a restart..

Uh, no.  It's the CONTROLLED system that has to use the XDDM driver model for the fix to be effective.

-Noel

THIS FIXED IT THANK YOU SO MUCH

Can I kiss you?

I didn't even need to reboot. Just to re-connect

I just went through the same pain, and this tip seems to have saved the day.

I was running a Win-10 1809 system as a Host for a Centos 7.7 Guest. I would RDP in to this system from a remote 1903 system, and things worked as expected.

After updating the 'target' system to 1903, I had a horribly unusable 'jumpy' mouse in the remote controlling systems RDP session (when contolling the vmware Workstation Guest).

After making the change with gpedit.msc on the target system (hosting the Workstation 14.1.8 guest), the mouse is once again usable in the Workstation Guest (when RDPing in).

I changed from Workstation 14.1.7 to 14.1.8, from Windows 10 1809 to 1903, and updated the Nvidia Video drivers to 441.21 (studio) all around the same time. So, which one (or combination) was responsible is not clear to me. But, it seems like there is some issue with 1903 and Workstation Guest.

Thanks.

I would like to make a public service announcement regarding this issue and the proposed workaround:

Many people have found that disabling WDDM will effectively make Windows use XDDM. Doing this fixes the mouse problem. This is only going to be a short term fix. In Windows 10 1903, Microsoft replaced XDDM with WDDM and is no longer developing XDDM [1]. In an upcoming version of Windows 10, the option to not use WDDM will no longer be available. I would highly recommend either complaining to Microsoft, complaining to VMware, or finding another solution since this workaround is soon to no longer be available in a future version of Windows 10.

References:

[1] Windows 10 features we’re no longer developing | Microsoft Docs

Great... In my case the mouse problem is not just annoying, it makes the session unusable...