is your rdp client updated to 18362.356 too ?
mine shows this, and the problem is not solved as of 10.0.18362.356, It seems Microsoft is destroying RDP while trying to solve its vulnerabilities. I had to move to virtualbox indeed, and I am not really happy about that...
Tried it now with the latest windows updates installed on v1903 and the mouse problems are still present when using linux VMs inside vmware. Let's hope vmware will fix this bug in the upcoming 15.5 version.
VMware 15.5 is out, the problem is still there...
Hate to say it but this issue isn't limited to VMware guest machines into which you might RDP. It happens when the remote system is a v1903 hardware system too.
I regularly RDP from a multi-monitor hardware system running Win 8.1 into a remote multi-monitor hardware system running Win 10 and use it for hours,
- When the remote hardware system was running Win 10 v1809 it worked perfectly. "Like being there".
- When I moved the remote hardware system to (a fresh, clean install) Win 10 v1903 the problem showed up.
The problem gets MUCH WORSE if I try to use a VM on the remote hardware system. I don't mean RDPing directly into the VM, but use the VM on the desktop on the machine I'm RDPing into. The interaction is maddening, with the cursor jumping around all over the place.
The problem also gets much worse if I start a screen-grabbing tool (ffmpeg) on the remote system to capture a video of what I'm doing.
It used to be that only the originating system controlled where the mouse pointer would be. Now both both the originating system and the remote system try to control it.
I suggest, as one prior poster mentioned, that the problem is with Microsoft's current implementation of RDP, specifically the server component.
since v356 from my laptop to remote, my mouse issue doesn't occur.
tested with workstation 15.1 and vm guest win10 & Ubuntu.
before v356 on my laptop, the problem was here, then i was using xfreerdp client because it was not possible to work on VM runns from VmWare Workstation.
upgraded to 15.5 version, it continue to works as expected
but i don't remember if i was touched another setting. i'll try to install an old 1903 on my laptop just to test !
edit: correction some words , sorry my poor english
I can confirm, as crematory noted, the problem still exists in 15.5.
I've installed a fresh 18362.1 (1903, with no updates) on my laptop, then I rdp to my remote 1903 , no mouse problems on my Vmware Workstation's VM !
So the problem isn't of the client side.
Somewhat has changed on my remote system during last month, but I do not know yet.
It seems a microsoft issue with VMware rather a vmaware issue alone, unless vmware comes out and sheds light on this, since 1903 microsoft has been issuing patches for RDP trying to mitigate RDP vulnerabilities.
Edit: Today I discovered that CentOS 6 guest mouse works OK, while CentOS 7 and Windows 10 guests have the bad mouse in VMware WS 15.5 ..
I found that when I use the APP version of "Microsoft Remote Desktop", the mouse works OK.
Personally I suspect Microsoft changed the protocol slightly in a way it would make it irritating to use from an older system - as an incentive to get those of us using older OS versions to upgrade. They'll never admit it, they'll never document it, and there's nothing anyone can do about it.
man we are talking about Windows 10 1903 with latest updates connecting thru RDP to a similar machine that has VMWare workstation 15.5 insalled on it, which has both windows 10 and centos 7 guests. The mouse moves in a strange way inside the windows 10 and centos guests. The irritating thing is that this doesn't happen on freerdp, and also doesn't occur on virtualbox which makes you think what the hell is going on...
Just tested with a new VM CentOS 7, no mouse issue (Win1903 Last update on Remote Host and Client RDP)
perhaps a driver ? or software used in host ? or remote hardware config ?
I'll try an new install on spare host next days ...
I was having the same issues with jumpy mouse when RDP'ing to host and using VM's on Workstation 15.0 and 15.5 after upgrading to Windows 10 1903.
I was having other issues with the machine periodically crashing while on RDP and found posts mentioning a local policy change to address that issue. So far no crashes, but I just hit one of my VM's and no lag anymore either!
I haven't had time to flip it back to see if it returns, but I'll include the info here for anyone who wants to try it and let us know if it solves it for them!
Local Computer Policy
Remote Desktop Service
Remote Desktop Session Host
Remote Session Environment
Use WDDM graphics display driver for Remote Desktop Connections to DISABLED