If you’ve been following this thread, you’ve already seen my solution below to uninstall KB2592687 in order to remove the security error from RDP’ing into a Windows Server.
The real issue I was having was that my mRemote client wasn’t passing the “new” control that MSTSC is looking for.
The new updated solution (for me at least) was to stop using mRemote and start using mRemoteNG that can be downloaded at this hyperlink.
Please note the instructions on how to copy and paste the XML files needed to migrate your old mRemote connections to mRemoteNG.
This has stopped the error and you no longer have to uninstall KB2592687 to remove the error.
Recently I updated my workstation using Microsoft Update. The next day , a curious thing started to happen. When I was using mRemote to RDP into some servers, I started getting popups that said “a website is trying to start a remote connection”:
I would allow the process and connect normally. However, this was beginning to get QUITE ANNOYING. I found this blog on CodePlex that summarizes it nicely although it took me a while to find it.
Here’s the jist (from Microsoft):
This article discusses the Remote Desktop Protocol (RDP) 8.0 update that enables you to use the new Remote Desktop Services features. These features were introduced in Windows 8 and Windows Server 2012 R2. These features are now available for computers that are running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1).
So there you have it. “NEW FEATURE”. I’ve since uninstalled and rebooted and am back to enjoying NOT having that feature.