Hello, since a short while, (maybe creators update?), when using RDP in mRemoteNG, my mouse cursor disappears in text boxes, eg:
|||
|--:|---|
|Operating system | Windows 10 x64 Creators update |
|mRemoteNG version| 1.75.7005.28249 (hotfix 5) |
((I cannot label this as a bug as requested in this project's guideline; is it a permission issue?))
Thanks for the report @jupsoleil
Hmm - yes it might be a permissions issue. If so, we should remove the line about tagging your own issue tickets with bug/request. Thanks for bringing that up as well
Interesting: the bug is only visible on an external monitor. I have an HDMI display (connector on motherboard of my laptop) and a DVI via my USB3 dock. On both external displays the mouse cursor disappears as described. Only when using mRemoteNG. I had the problem with the normal release; I installed two alphas thinking it might be fixed but till now not fixed.
I have the exact same problem:
Windows 10 Pro, mRemoteNG version: 1.75.7000.19194
I have this issue when working on my laptop screen and not on a external monitor. This makes it really hard when connecting to developing machines with Visual Studio on it.
Same thing here (1.75.7008.17907).
It is really hard to work when your cursor(Text Select) is gone.
Btw. the Text Select is not completely gone its is just 3 or 4 pixels big, so it is really hard to see on a high resolution.
I have the same problem. Anyone found a fix?
Exactly the same issue, is there a fix or workaround?
I may have found a workaround (works for me). I'm connecting to windows server 2012 machines, but I expect this is the same as on Windows 10.
Go to Ease of Access -> Mouse, and set Pointer Color option to Black (the middle of the three options). After doing so the I-Beam appears as it should.
@jupsoleil @MaikvanderGaag @sunnyjayjay @difa1012 @sparerd
Thanks for sharing your workaround @Spankachu!
@Spankachu thanks, indeed, it works, but this doesn't fix the bug causing this, and many of the rdp sessions I use are on systems where I shouldn't change mouse cursors permanently or the users will not be happy...
@sparerd you have no idea on what the root cause is of this problem?
Work around is not working for me. I experience the same problem when using the Microsoft Remote Desktop Connection Manager. Is there any solution for this?
I believe this is not an mRemoteNG issue, but instead (another) Windows scaling issue. This only happens when I'm using an external monitor attached to a higher resolution laptop. If you try RDP outside of mRemoteNG the issue is also there.
Examples:
I do not have the issue when using the build-in RDP tooling. Besides that I have the problem on external monitor en laptop monitor.
We are going to be updating the .net framework version targeted by the project in v1.76. .Net framework 4.6 has some improvements to high dpi scaling that we are hoping to use. You can follow #321 for more general info about this
@Spankachu - I'm having this issue with my 4k laptop + external monitor + RDP session to Server2012R2 and your comment has saved me a huge nightmare. I've tried everything and at this point I don't care about the root cause as long as it works. One thing to note is I had to change the cursor color on the remote computer, not my local laptop.
I have the same issue with Remote Desktop Connection Manager (works on 4K laptop monitor but not standard external monitor). I also confirm this works fine when connecting directly using Remote Desktop Connection instead.
Exactly the same issue. Worked fine and now after ~ 2 months of using NGRemote mouse cursor is disappearing in text boxes.
Changing colour of a pointer is not a solution as RDP is working fine, so clearly mRemoteNG needs a fix ASAP
Still happening here, Surface Pro (200% scaling) on an external monitor (100% scaling)
Hello,
I am using Mremote 1.76 and since I have a new Dell with DPI my Mremote does not work well.
My laptop is windows 10, I RDP a windows 2012 SR as jumpbox and from there the mouse is tiny.
I am using an external screen.
Also if from the RDP I SSH a linux with Putty, the mouse inside the putty disappear so I cant use anymore MremoteNg ...
I used the trick to change the color of the mouse in black but then I need to change all my putty session as the background is black and the mouse is black so useless.
One more thing if I use the Mremote from the screen of the my laptotp it does work but from from external screen
Do we know when we gonna release and fix that in Mremote ?
I heard 1.77 ?
Thanks
Paul
Yes, this will very likely be resolved with the HiDPI support we have added in v1.77
Hi David,
Thanks, do you know when you gonna release MremoteNG as for now I cant use it anymore.
I got a super good new laptop but cant use my main useful sotfware anymore ;-(
Paul
Unfortunately no, we don't know when the next version will be released.
I had the same problem. Perhaps you are using the same connection using mremoteNG and Windows Remote Connection ?
or you have used windows remote connection after that mremoteNG ? in this case, you should restart you computer and use only mremoteNG
It's like that that I resolved the problem _in my case._
Is this still happening with the latest Windows update and the latest mRemoteNG prerelease?
Also, this just might be something we will have to live with:
https://support.microsoft.com/en-us/help/3025083/windows-scaling-issues-for-high-dpi-devices
Most helpful comment
I may have found a workaround (works for me). I'm connecting to windows server 2012 machines, but I expect this is the same as on Windows 10.
Go to Ease of Access -> Mouse, and set Pointer Color option to Black (the middle of the three options). After doing so the I-Beam appears as it should.
@jupsoleil @MaikvanderGaag @sunnyjayjay @difa1012 @sparerd