![]() In the Display Settings, set the primary screen to a monitor which runs with 100% scaling. Possible Workaround: Set primary monitor to 100% display On newer Windows 10 versions you may need to click the "Change high DPI settings", check the option "Override high DPI scaling behavior." and set "Scaling performed by" to "System" or "System (Enhanced)": On the guest machine (that you are remoting into) simply edit the current Windows theme and change the mouse cursor. Launch the application and the cursor appears normal. Thankfully the fix is a pretty simple one.In the Compatibility tab select the “Override high DPI scaling behavior” checkbox.Right click -> Properties on the RoyalTS.exe.Navigate to the install directory where RoyalTS.exe is located (default is C:\Program Files (x86)\\Royal TS V4).One of our users provided a possible workaround for the issue above: Possible Workaround: Set DPI scaling behavior for RoyalTS.exe In case you find other DPI and RDP related feedback items in the feedback hub application, make sure you vote for them too! It may also be useful to comment and provide some context/more information about your setup for Microsoft to repro and fix the issue. Mouse pointer will not be visible or loss of control of mouse pointer occurs. On the work computer, open skype, teams or any conferencing program and share screen with someone. In case the above link does not work, search for "RDP Mouse Text Cursor to small (pointer is OK) (DPI issue)" (without the quotes). Connect to work computer through remote desktop. We checked with the Feedback Hub application in Windows 10 and noticed that this bug has already been reported to Microsoft but not yet fixed.Ĭlick the following link on your Windows 10 desktop to open the issue in the feedback hub application: This seems to be a bug in the Microsoft RDP ActiveX control which ships with Windows and is used by Royal TS and similar applications. We weren't able to repro the issue on our side but several users reported that this issue is more and more showing up in Windows 10, especially after the "Creators Update". We got user reports of an issue where the mouse cursor rendering in the remote desktop session is too small or missing. Please provide feedback to Microsoft (as stated below) and help them to fix the issue. The information below may be helpful in some situations but it is important to understand that these issues cannot be fixed on our side. Unfortunately we cannot fix those issues as they are caused by Microsoft's RDP ActiveX which ships with Windows. Note: There are some reports about DPI issues within Remote Desktop connections. ![]() I was able to create a work around by setting the local computer user profile to match the Windows Black - extra large cursor size so when it does flip between the two cursor settings (remote and local) it will behave as we would like to the user to see.Solution home Royal TS (for Windows) Knowledge Base Mouse Cursor issue with high DPI in Remote Desktop Sessions ![]() Is this a known bug or issue and if so can someone let me know what Windows CU update will correct this behavior. ![]() So basically i can confirm that the remote session does know that the Xlarge black cursors pointer settings is correct, however moving between displays/ applications the cursor will change to the local computer cursor settings. We are noticing that when logged into a RDP session, mouse cursor pointers that are set in the remote server windows user profile (set to Windows Black - extra large) are changing back and forth to the cursor pointers on the local Windows 10 machine (default small grey pointers) where the RDP was initiated from. The other day I switched to Windows 11, the virtual desktop which I use in my clients network is Windows 10. We have work computers (Windows 10 Ent LTSC 2019 / Windows 10 build 1809) that have multiple displays connected that primarily RDP into RDS servers (Windows 2019 STD LTSC).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |