We've managed to reproduce the issue this time, with the remote laptop's lid being closed. I'll forward this to our developers to see if there's anything that could be done to fix the issue in our future updates.
Just wanted to add my .02 here, I've defaulted my host settings to Use Legacy Capture Mode, especially if the host computer is a laptop. I've noticed that many laptops when the lid is shut and the Use Legacy Capture Mode is not checked, the Viewer gets a blank black screen. Opening the lid restores the image on the viewer screen. Turning on Use Legacy Capture Mode enables the viewer to operate a laptop with a closed lid.
Correct. Am aware of that legacy setting. The troubles started when Microsoft released they're April 2020 patch (MS calls it 2004). While legacy capture stopped the black screen effect, a new effect surface where A) the start menu size shrunk to very small text, and scroll boxes do not work (like the text image is frozen even though you can move the scroll bar down).
Hopefully, the developers can determine what changed in all of this to cause this new issue.
I checked on the issue with our developers - even though we have managed to reproduce it, unfortunately, it's caused by something in the Windows OS's update itself, rather than something in the program. Like I've mentioned earlier in the thread, Remote Utilities only works in a console session and displays exactly what is shown on a remote machine. Unfortunately, in this situation, we can only recommend referring to the Microsoft support service as the issue occurred after the 2004 OS update. Sorry for the inconvenience.
Nijel, thank you for your input. Indeed, enabling the Use legacy capture mode feature usually helps in resolving similar issues. However, in this case, the issue is caused by some changes that were applied to the way the Start menu is displayed after updating to the Windows' 2004 patch.
So understanding that this may not be resolved, I did try the Classic Shell add-on/modification. A few things of note for others that attempt this and some general info if others need to take this path to get this to once-work again.
1) Classic Shell is no longer supported by the above-mentioned web link (the website does still work). The Developer decided to hang up his hat on this and make it Open-Source where others can still develop on it. The developer did state he would be taking down forums, etc. within 6 months of the announcement (now almost three years ago), so never know how long it will remain. Main page does have links to the Github location.
2) It is on Github and the name of the program has been changed to "OpenShell": OpenShell on Github
For those wondering, yes, the current version on Github (4.4.152) does install successfully on WIndows 10, and does get around that annoying screen shrink issue that came with the latest/last patch from Microsoft, 2004 when using Remote Utilities on a Laptop, with the lid closed.
"Use legacy Capture mode" is still required in order to get around the black-screen issue also reported when lid-is-closed and Windows 10 has been patched to version 2004. OpenShell does not resolve that neither.
Finally, Microsoft's next update is expected around November, we'll see if there are any improvements that help out Remote Utilities.
Unfortunately, this did not resolve the video issues documented here in this posting. Can we assume that the RemoteUtilities developers are unable to come up with a workaround?
Unfortunately, in this case we cannot provide a fix for this issue, as our assistance in resolving issues caused by third-party software is limited (please see our Support Policy). In this case we can only recommend to contact Microsoft support service and ask for their input on the issue.