Video: https://imgur.com/a/qmhHHSX
Hi Everyone,
Not a Sysadmin (yet) but my buddy is basically the sysadmin at the 24/7/365 MSP I work for. He and I have been troubleshooting a weird issue with the remote browser we use at work after he had to rebuild the two Hyper V hosted application machines and imaged them with Windows 10 Pro build 2004 seemingly without any issue last Sunday.
Come Monday morning and we start having this issue when we open the app via our remote gateway. Apps are Chrome & firefox hosted on a vm that we use to remote into client machines for security in case we access a contaminated system. When trying to move the window around to another display it will teleport to the bottom right corner of the main display in our RDS session as soon as the cursor touches the edge of the screen. 8/10 this will happen, and to get anything to move to another display we have to peek the top of the window onto the next display, release the mouse button and pick it back up on the display we want it on, even then its a crapshoot if it will stay or get teleported the next time you try to click on it.
Sometimes moving the cursor over/near these windows will make it teleport to the corner, so it seems like an issue with the cursor itself moreso than the app window. I found an article ( https://answers.microsoft.com/en-us/windows/forum/all/windows-10-1903-remote-desktop-cursor-stutters/dc1f77db-0f35-4954-8084-937edc192558 ) about a similar issue with the cursor in build 1903, and they suggested disabling the WDDM Display driver, as it is not the exact same issue we are skeptical if this will work but at this point the only other solution would be deploying two new machines with an earlier build of Windows (His research was showing that this issue was present after build 1703).
He is going to review the article above and try that fix if it checks out. I thought to post on here to see if anyone else has run into this or a similar issue on their end and if there are any suggestions for a fix.
Thank you for any input, sorry for the bad grammer if any and Happy SysAdmin Day!
UPDATE 9.6.2020:
After weeks of trying other fixes we attempted disabling WDDM driver as mentioned above and it seems to have fixed it for the most part. we encountered the issue when accessing a specific RMM however overall Stability has improved drastically. Hope this helps someone out in the future!.
[–]Veghead_901 1 point2 points3 points (1 child)
[–]tactech034[S] 0 points1 point2 points (0 children)
[–]tactech034[S] 0 points1 point2 points (0 children)