Regarding the two-row toolbar - your window chrome (frame) looks quite unusual. Do you have any theme pack or something else that modifies default Windows window layout, controls etc.?
I do not have any theme packs or other customizations. I do have the latest Windows 10 Anniversary Update, which has caused other users issues, according to the Internet. The only setting that sometimes causes issues in apps for me is the custom scale factor I have set (175%). I have bad vision and I need icons and text to be scaled up in Windows. This frequently causes windows and dialog boxes to have shifted or cut off text or buttons in apps that do not account for the scaling. I know I'm a unique case in this regard.
I know you have to ask the basic questions, but as you can see in my original post I have already answered this question ahead of time, because I knew it would be the first thing you'd ask. I have already enabled Remote Desktop on the Target machine. AND I am able to connect via RDP manually using the Windows built-in RDP app. The problem is with the Viewer app. It does nothing when I initiate an RDP connection to a Host on my local LAN.
RDP function using the Viewer does not work for me at all. The Viewer is a Win10 Pro machine, and the Host is a Win7 Pro machine, both running latest beta, 18.104.22.168. RDP did not work either before the beta upgrade, on version 22.214.171.124, by the way.
I can connect just fine using Windows RDP app from the Viewer machine to the Host machine. I checked and made sure that RDP was allowed on the Host machine. When I click on RDP in the Viewer, nothing happens. I verified that the RDP port setting in the Viewer is correct, I tried with Direct Connection checked and unchecked.
Also, in the Properties, the Configure box is cut off - see screenshot link below.
I'm using my own self-hosted Server. In the Server interface, I see all my Hosts listed, with their external IP's correctly listed. In my Viewer, however, the Last IP column displays the IP address of the self-hosted Server instead of the actual WAN IP of the Host. The exception being the Hosts that are on the same LAN and are being connected to directly.
One other related observation. One Host that has been upgraded to latest beta, 126.96.36.199, and is the same Host that the Viewer is running on, is displaying 169.254.13.154 as the Last IP.
I have also noticed this bug, with the Viewer version 188.8.131.52, and the new beta Viewer. I mostly noticed it after trying to copy and paste between my local machine and the remote machine, with ctrl-c and ctrl-v. The copy-paste operation does not work and then the ctrl key is stuck when I minimize the Viewer and try to do anything else on my local machine. A couple of taps on the control keys on my local keyboard clears out the stuck issue.
I haven't reported this before because I thought I was just me.
Bart, another important question - from which version you tried to upgrade to the beta one?
We've tested upgrade from 184.108.40.206 (the latest stable) to the beta and it worked without an issue. The password was there and we were able to connect back.
I upgraded from the same version - 220.127.116.11. I have another Host that I can test upgrading with, a Windows 10 laptop that is right next to me. Do you recommend trying to upgrade just by running the .msi directly on the laptop, or try upgrading using the Tools > Upgrade outdated Hosts tool in the Viewer?
Thanks for your reply. The Viewer is a Win10 Pro machine, and the Host is a Windows 7 Pro machine. I've emailed the logs and the screenshot to the support address. I'm a little hesitant about upgrading the Server module. With my luck, something will go wrong and all my Hosts will become inaccessible.