none
Win-1903 RemoteApp: Cursor teleporting when changing between multiple displays RRS feed

  • Question

  • Hiya!

    I am seeing some very strange behaviour since upgrading from 1803 to 1903 on my Windows 10 Enterprise environment.

    RemoteApp host:  Windows 10 Enterprise 1903
    Client: Windows 10 Enterprise 1903
    Displays: More than one

    Reproduce:

    Create a Remote app session capable of multiple windows (like a browser).  Place window (1) of the session on the left monitor (A), and another window (2) on the right monitor (B).  Preferably maximise both windows.  Once the mouse is moved across the monitor boundary, it jumps / teleports to the right a considerable distance.  In this situation, it is actually impossible to move the cursor / pointer back to the left hand monitor again, as it will repeatedly jump back to the right every time the monitor boundary is reached.  This makes 1903 pretty much unusable for me unfortunately, and I expect the same for most people using RemoteApp.

    Other interesting notes:  If there is only one window which spans multiple monitors, the issue also exists.  This makes moving a RemoteApp window from a monitor on the right to a monitor on the left almost impossible.  In this case the user must drag the window on the right monitor from the very right hand side of the window.  Whilst dragging over to the left window, the user must make sure the mouse cursor does not cross the window boundary whilst dragging or else the entire window will teleport back to the right along with the mouse cursor.  A gap of desktop space must exist along the window boundary.  The mouse pointer can then be bought back to the window on the left hand monitor, at which the pointer will teleport back into the right monitor.  Then the user must now avoid touching any part of the window still remaining on the right by nagivating through the monitor boundary over a gap where there is no part of the window displayed.  The mouse can then be bought back inside the window perimeter on the left side (this time it should not teleport) and the window dragged fully over to the left.

    Really need a fix on this one before we can deploy.  I can't roll back so will have to go back to my Mac until this can be fixed...

    Monday, July 22, 2019 6:52 AM

All replies

  • Hi,

    What is your RDS OS version? 

    Please check detail OS build number on both client and RDS systems, and provide me the information:
    Open Run, type winver and end with enter.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 23, 2019 7:58 AM
  • Both are build 18362.239
    Tuesday, July 23, 2019 11:31 PM
  • Hi,

    In general, within Microsoft solution, RemoteApp deployment needs Windows Server system with RDS deployment. As you had mentioned, both local and remote systems are windows 10 1903, please provide more information about your RemoteApp configuration, and I want to confirm with you if RDC is used to establish remote session? 

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Wednesday, July 24, 2019 8:26 AM
  • Hi Eve,

    I was fairly sure that when we got our SA on Windows 7 Enterprise, it was supported as a RemoteApp session host.  Has something changed there?  I haven't really noticed any deprecation of support for the method.

    To follow up with your question, RDC is indeed what is being used to establish the remote session, via customised RDP files.  They connect to another Enterprise VM hosted on the same PC using Hyper-V which is tasked only with hosting the remote application.  The VM has had a registry change to enable the remoteapp session host.

    It has worked pretty well for a long time, until this latest update.

    Thursday, July 25, 2019 8:51 AM
  • Another update, I also have a Windows Server 2019 RemoteApp session host.  It is not affected int the same way when connected to from the same Windows 10 Enterprise client.

    It is Windows Server 2019, 1809 build 17763.253

    I have also tested a fresh install of Windows 10 Enterprise as the RemoteApp session hosts, and it also exhibits the issue before making any changes.

    I was going to attempt testing with Windows Server 1903, but that is Core only.

    Monday, July 29, 2019 3:28 AM
  • Hi,

    In order to have further identification, tracing and process monitoring log should be collected. However, detail log collection and analyzing is beyond the support scope on the forum. 

    I would suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. 

    Global Customer Service phone numbers:
    https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

    Thank you for your understanding.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 2, 2019 8:15 AM
  • I have submitted it as a support issue, and will see how I go there.
    Wednesday, August 7, 2019 3:04 AM
  • Hi,

    Thank you for updating the status, if there is anything else we can do for you, please feel free to let us know. 

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 7, 2019 8:02 AM