dbeck

Ok, under advanced options I didn't have the RDP scale factor disabled, so I checked that.

That seems to have done the trick. I have tested out a couple of servers and am no longer having the cursor jump when I right click the start menu.

Thank you SOOO much for the help. That was driving me crazy and now I can get back to just enjoying remote desktop manager as my RDP app.

When using the ActiveX (that is the default, correct?) the right click on the start menu jumps. I hadn't changed any settings, everything was the default.

As for the templates you mention, File->Templates, there is no such menu item.

Wait, I think you mean saving that info in server entry? I don't create entries for every server as they change quite a bit, but I launch the quick connect all the time. I would like any new connection to default to my username and my domain without me having to create entries for every server.

I mean it isn't saving domain and user name like it was before. I've searched through the options and haven't figure out how to make FreeRDP 7.0 save the domain and username. If I can get that to work the same as the default, where all I have to do is input my password, then I'm ok with switching it over to FreeRDP 7.0 and using that.

If I switch the engine to FreeRDP 7.0 then it works fine. However, that changes how the login works and I have to get used to it again :) I just have to figure out how to make it save the domain name and user name and then I can deal with the differences and get used to them.

So what is the difference between the default (not sure which version it uses) and FreeRDP 7.0?

Ok, I downloaded the Microsoft Remote Desktop Connection Manager version 2.7, used it to log into the exact same server and I do not experience the same problem. The same server opened through Remote Desktop Manager has the problem where a right click on the Start button, but only on the start button, causes the cursor to jump to the bottom middle of the screen.

If I use the built in Remote Desktop Connection and log into the server again it is fine.

The problem only occurs if I log into Server 2016, 2012 R2 and 2012. 2008 and 2003 work fine. I haven't tested desktop OS's as I only deal with servers.

So was anything ever discovered as to the source of this problem? I never had an issue until I upgraded to 3.0.1.18 and then I ran into it. I've just been putting up with it as I love the product, and today I upgraded to 4.0.1 hoping that the issue would be resolved. No luck, it still happens.