version 6.10.9 ever since upgrading when I make an initial connection the screen remains black for about 5 seconds, then I need to move the mouse over start menu/other areas. when I do this the screen will begin to redraw itself slowly until it looks normal. I upgraded all my systems (4 hosts, all using windows 10 x64 latest version) and this happens to all of them. setting legacy capture mode resolves but it seems in legacy capture mode the screen view is not as clear as the normal mode... these host are direct (connecting via local IP)
also besides the screen issue the connection itself seems slower, it used to be very fast but in general it seems RU is getting worse... not better, very disappointing.
If you use direct connection the performance and speed should be near instant (real time). If upgrading to the new version caused such decrease in performance - especially when direct connection is used - we would have been reported that immediately including here on the forum.
Please, send us your Host logs for examination. Also, make sure that you upgraded the Viewer as well and restarted your remote Host PCs after the installation . If you cannot restart the entire Host PCs try restarting the Hosts only.
yes the viewer and all my hosts have been updated. this happened right after the last upgrade. all systems have been rebooted multiple times, I even reinstalled the host on one of my systems to see if it would help. it did not. the only other option I can try would be to uninstall the viewer from my main system and reinstall it. perhaps something went wrong with the viewer upgrade. as I mentioned this worked perfectly fine prior to the upgrade,on all my systems then after the upgrade this issue occurs on all my systems not just 1 but all my network is GB network (managed switches) and my hosts do not have any 3rd party firewall/av installed they all use built in windows defender and windows firewall.
I will see if uninstalling viewer helps since reinstalling host does not. I will also send host logs when I can.
just curious does remote utilities use an XDDM-based remote display driver? I'm only asking since I just read one of the features Microsoft has removed in windows 10 May 2019 update is XDDM-based remote display driver. the article states: Independent Software Vendors that use XDDM-based remote display driver should plan a migration to the WDDM driver model. here is the link to the article I just read. https://betanews.com/2019/05/23/removed-or-deprecated-in-windows-10-may-2019-update/ here is what the article states regarding XDDM remote display driver: REMOVED FEATURES: XDDM-based remote display driver -- Starting with this release the Remote Desktop Services uses a Windows Display Driver Model (WDDM) based Indirect Display Driver (IDD) for a single session remote desktop. The support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent Software Vendors that use XDDM-based remote display driver should plan a migration to the WDDM driver model.
Edited:Michael Taylor - May 23, 2019 8:45:13 pm EDT
I can confirm I have the same issue on initial redraw. I don't think it came with 6.10.9, I faintly recall being annoyed by this behavior even with older versions (but I am not sure and I certainly don't remember which version started that). I also use direct connections, but I didn't try legacy capture yet.
1) I suspect this may be (partially) caused by the active screen saver. It might be a good idea to "move the mouse" on connection so that the screen saver is turned off.
2) The initial redraw is slow, even if the initial screens (blanking screen saver, fixed-color login screen) are very simple. Once the initial redraw is done, the succeeding redraws are much faster - in fact, redrawing a desktop with complex and diffult-to-compress background is maybe twice as fast as the initial redraw of a one-color lock screen...
I already did, but did not observe any change. Note, though, that I did it remotely and wasn't able to restart RU, so I expect the change did not take effect yet. I will restart the computer tomorrow and then test how it behaves.