RDP under Build 1607 killing running program on client, upon exit

Yes, it is RDP when you type in remote (i.e., mstsc.exe in System32 directory).

I'll give it some testing today and will post back on results. Worse case is I do have TeamViewer working but no where as good as RDP works.

I will not call this issue Solved until Microsoft fixes the native RDP program without the help of RDP Wrapper. I'm not a fan of band-aide, third party fixes when it comes to the operating system; Microsoft needs to resolve this one and I am holding my breath :).

Again -- THANKS for the feedback and your time!

Stop using RDP because it is ancient and has not kept up with the times. Use Teamviewer or VNC.

Sorry, but I have to disagree on using TeamViewer or VNC as better solutions for what "I" need -- RDP is (WAS) a solid, remote desktop tool when the user is strictly the only one needing "full" control of remote (host) systems. I've been using it well over 20 years now and it works on all other hosts I have to access/maintain for my business, except the one I need here in this discussion.

A little status feedback: I reinstalled RDP Wrapper and tried RDP again -- got to the login screen, entered the password and it crashed the upload stream. Still got access to the host just fine and can do whatever i need except it crashed the stream. Exit the radio software, restart it, and stream stays on (while I'm in the RDP session). As soon as I close the RDP session, stream crashes. Again -- never did this after 11+ years or running my hobby radio.

SO -- will stick with TeamViewer for now. Don't have time to check out VNC but will consider it. What I'm reading is TV is the best one of the options out there.

bro67 said:

Teamviewer is multi-platform and no having to run a DNS proxy. VNC is great if you are on the same LAN as that machine and need a lighter weight interface than Teamviewer is.

THANKS for the insight. Teamviewer seems to work very well so far. I did miss someone's comment about whether I was running RDP with "run as adminstrator" (or changing properties to select "Run as administrator" -- but my gut is telling me it's still going to stop the stream.

bro67 said:

Running as Admin when you do not want to, can cause you issues if someone you allow to access and they go in and start deleting stuff.

I set Teamviewer up with my user account password when I was on the LAN or wanting to get into the desktop. Otherwise it was just the regular Random Password at the strongest setting.

It is not that everyone is hating on RDP. It is just outdated from Microsoft never catching up with the newer more secure methods like TV and VNC. Also when you do Cross-Platform remote connections, every OS has its own way of doing RDP and it is not always going to be bulletproof or work 100%. Plus RDP is so slow when compared to TV and how it handles Remote Connections.

True, true. Funny how it has helped for so long and BAM - broken. FYI -- running RDP as administrator made absolutely no difference; stream (audio) still crashed. As long as no one hacks my TV account, I'll probably stick with it. Would be nice if a licensed version didn't cost so much for a single individual!