RDM no longer functional after W10 Anniversary Update

Hello,


We are trying to reproduce locally, we have another case in the support pipeline with those symptoms.

We'll keep you posted

Could you try to execute RDM with Run As Administrator?

Regards

Hello David,

Just tested that, same result unfortunately.

Only difference I see is a slightly reduced CPU usage, it is now below 25% instead of around 30%.

Beste regards,
Erik

Have you tried RDM 64bit or 32bit?

Hello,

We will wait for a response from you on previous questions before going further.


Best regards,

Hello David,

You may slap me (gently please) but I simply downloaded the MSI from your website, I am not aware of a 64bit download link. So yes, I am using the 32bit version, which could of course explain my issues.

Best regards,
Erik

It's included with the same msi. You can execute RemoteDesktopManager64.exe from the installation folder

Regards

Hello David,

I guess I am the exception that confirms the rule or something, but I cannot find an x64 executable. I've downloaded both the ZIP and the MSI, unpacked both and I cannot find the 64 bit executable.

When I run the MSI, it installs into Program Files(x86) and doesn't give anything like an option to do otherwise.

Just to make sure, I am talking about the RDM Free version.

Regards,
Erik

Hello,


The Free Edition is only offered in 32bit edition.

Best regards,

Was starting to suspect that already.

Since I have migrated from Terminals to RDM Free quite some time ago already, you are now forcing me to buy it or switch to another product and rebuild my entire server connection database, to say the least, that's a bit of a bummer.

What I also find 'remarkable' is that it ran fine on a 64bit Windows installation, until this Anniversary Update and please,don't blame Microsoft, that would be a very unprofessional and cheap way out of this discussion.

Maybe I have overlooked something on your website, but it is NOT clearly stated there that the Free edition only comes in 32bit.

Should I decide to buy the product, will all my data at least seamlessly migrate over? In other words, if I copy/pasty my connections cfg file, will all my connections still be usable?

Regards,
Erik

Hello,


This is still a diagnostics process, we have not hinted to upgrade nor purchase, we just need to identify why it does not work on your machine at this time. The steps above were to try and isolate the issue. On our test machine, it works in the 32 bit edition.

Hi,
We are not even sure if the 64bit version works. We are able to run both (32bit and 64bit) on our virtual machine. We just try to find why it does not work. Could you try to download the trial version of RDM just to check if the application starts.

Regards

Hello,


Another suggestion we'd like you to try, right click on the shortcut and use the "Troubleshoot compatibility" tool, just with the recommended settings initially.

Hello

I have also an issue after applying W10 anniversary update. But for me, the problem exists only for connections which have to be done over a remote desktop gateway. The RDP connection using mstsc with the same setting works as expected.

Thanks for having a look into this

I am experiencing an issue as well after the W10 anniversary update. External RDP sessions do not open, but internal (tabbed) works as expected.

This is really strange for the external mode. All we do is invoke mstsc.exe. Could you try to create a Command Line session and invoke mstsc.exe to see if it opens?

Regards

I can launch mstsc.exe from the command line and open a session manually. I can launch from my taskbar shortcut and open a session. I noticed that I cannot open from the taskbar jumplist directly to a recent or pinned session though. Trying it that way pretty much the same behavior as from within Remote Desktop Manager. Just no response at all.

Could you try to launch it from a Command Line session created in RDM:

http://help.remotedesktopmanager.com/sessions_commandline.htm

Regards

Yes, that worked fine.

Could you try to export your session to a .rdp and invoke mstsc with this rdp file as a parameter to the command line?

Hello David,

I just ran a clean install of the Enterprise version and ran the x64 exe. No problems though startup seems a bit sluggish. I've created an RDP connection and was able to use it without problems so far.

Can I just copy over the data directory from the old 32-bit install so I have my connections back? That way I can also test some ssh / https etc connections.

Regards,
Erik

Hello,

The default data source is a SQLite data source and the file is saved in %localappdata%\Devolutions\RemoteDesktopManager. The name of the file is Connections.db

You can copy this file from the old configuration to get your sessions back. Make sure to configure the appropriate path to reach this file in File -> Data Sources.

You can also recup your configuration. The configuration file is called RemoteDesktopManager.cfg and this file is also located in %localappdata%\Devolutions\RemoteDesktopManager. If you copy this file as well, you will recup your configuration like the license key, your options in File -> Options, etc...

Best regards,

Hello Jean-Francois,

I can confirm it works, all my connections are back.

Regards,
Erik

I am still finding it strange that the 32bits edition has problems after running the Anniversary Update. Up till now I've had zero issues with it on my W10 box.

Could this be because of the new anti-malware gadgetry M$ has put into the update?

Regards,
Erik

@Leslie,

One of our customers has encountered the same issue as you (that he was not able to open session in external mode) and he sent us the following information this morning:

An update on my problem. It seems to fixed. A new image of 1607 (07160) has been released in our mpn portal, and after reinstalling the new image the problem no longer exists.

I don't know if this Microsoft build is available to you, but it could help with your issue.

Best regards,

Hello Jean-Francois,

My issue is not so much not being able to open sessions, it is RDM Free not starting at all, or rather, starting, but hogging CPU at 25+ % and nothing else happening.

I am running W10 1607 14393.10

Regards,
Erik

@Erik, the previous was aimed at @Leslie


Please launch the app at the command line by using

RemoteDesktopManagerFree.exe /profiler
Please use the Send trace to support button when content stops scrolling in the profiler window.


Best regards,

Hello Maurice,

I will do that as soon as I have reinstalled the Free version, I am now running the trial version of Enterprise ;-).

Regards,
Erik

Hello,


They are two independent products that can be installed side-by-side.

Best regards,

Hi,

I also just installed the W10 Anniversary Update, and am using RDM Enterprise 11.6.2.0, and cannot connect via embedded RDP when a remote desktop gateway is used. Connects fine when using external (but prompts for password).

Embedded works fine as long as no RD gateway is used.

Debug logs shows:


Opening in Console / Admin mode
Your computer can't connect to the Remote Desktop Gateway server. Contact your network administrator for assistance.
RDP - Disconnect:50331656 / exDiscReasonNoInfo


Also tested on a new machine, and the same issue occurs. If it makes a difference, data source is Azure SQL.

Jake

Hello Jake,

Does the session credential and the RD Gateway credential are the same?

Best regards,

Hi,

Yes, the credentials for gateway and host are the same. It is set to 'use the same rd gateway credentials on remote computer'.

I tested with inherited (which work for another host in the same folder that does not use the RD gateway), and Default. Also tried without any credentials, which prompts for a password (not the rdm password prompt, but the windows password prompt), but still fails after entering the correct password. Same results with NLA off and on.

It might be something with the remote desktop gateway server itself. Possibly the new version of mstsc (v10.2 by the looks of it) changed an authentication method. When testing with a host with a 2012/2012R2 RD Gateway it worked, but 2008/2008R2 gateways didn't.

Jake

Could you export your .rdp session from mstsc? I want to verify if they added a new parameter. You can remove any sensitive info

Regards

Could you also try with RDCMan? We use the same ActiveX to open the RDP connection.

Regards

Hi,

RDCMan comes up with a password prompt (saying login attempt failed). After entering the same password it logged in ok.

I exported the connection from RDM as an RDP file, then edited in mstsc and resaved as a new file. (I removed servername details via notepad)

Looks like it added these lines:


screen mode id:i:2
desktopwidth:i:800
desktopheight:i:600
connection type:i:7
enableworkspacereconnect:i:0
gatewaybrokeringtype:i:0
use redirection server name:i:0
rdgiskdcproxy:i:0
kdcproxyname:s:


Files are also attached.

Jake

I also tested again with an external connection of my remote desktop session and it looks like the same issue as Jake has. My connection also uses a remote desktop gateway and if I want to start the session embedded the connection fails immediately. If I open the connection external, everything works. I also exported the connection to an RDP file and it is working when mstsc is invoked with that file. Looks like the embedded mode is doing something different.

Could someone try to set the RDP to RDP 7 in File->Options | Types - RDP

Regards

Hi David,

I changed it to RDP 7, but it made no difference. Also tried RDP 6.1 and 8.1, but were also the same.

Jake

David, I can confirm the same experience as Jake.

@Unlimited Networks
Just to be sure when you use mstsc.exe with the gateway. Do you get the prompt if you save your credentials?

Could you try to use the exported file and remove the gatewaybrokeringtype:i:0?

Hi,
Could someone try to overwrite those files?

Regards

I do not wish to reinstall Windows, if that is your suggestion. This is an inconvenience, not an emergency ;)
Thanks for taking our reports and working with us on the issue. Let me know if there is any more information I can provide or any other steps you would like me to take in order to help troubleshoot.

By the way, it seems that there is a lot of bugs with RDP:

http://www.tenforums.com/network-sharing/58427-rdp-files-wont-open-remote-desktop-after-win10-anniversary-update.html

@Leslie,

Thank you for your reply, no need to reinstall Windows.



Could you try to overwrite the AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll like David proposed. I also include the attachment here

Best regards,

I found a fix related to custom scale factors. Going to "Display" and turning off custom scale factors and signing out-in again resolved my issue. Here is the link to the thread where I found this suggestion: http://www.tenforums.com/network-sharing/58427-rdp-files-wont-open-remote-desktop-after-win10-anniversary-update-2.html?s=3b79f6d1d8c508681fc0906db0e7f2b0

The custom scaling factor fixed it for me. Thanks for that link!

Hi,
We have the confirmation that the bug with RDP Gateway was introduced by Microsoft in the Anniversary update and it seems to be only when you use the 32bit version of the ActiveX which is the case with RDM Free. It seems that there is a workaround.


You can replace the mstscax.dll library located in %windir%\SysWOW64\ with the "backup" file in "Windows.old\WINDOWS\SysWOW64".
You will need to take ownership of the file and give Administrators Full control access to be able to replace it. Please backup the file you are replacing.


The other solution is to use RDM Enterprise and execute RemoteDesktopManager64.exe. I know that some of you will think that we did it on purpose to force you toward the Enterprise edition but it's not the case. We will add a 64bit version for RDM Free 3.0 but we need time. Don't forget that the Free edition offers a lot of features and it does not have limitation like the number of connection you can create or open. So please don't be to hard on us.

We all hope that Microsoft fixes their bugs.

Sorry about that.

Hi David & Jean-François,

Looks like the 64bit version works fine. Thanks for your help. Hopefully Microsoft releases an update shortly.

Jake

I seem to have this problem only when connecting to an RDGW which is Windows Server 2008 R2. When I connect to a RDGW on 2012 R2 it works just like before.

Replacing the .dll workaround fixed it for now however

I've got the same problem today after upgrading W10 Anniversary Update. ' Open session' closes and can be openend only with embedded tab.

Hello,

i have the same problem. It doesn´t matter whether 32 Bit or 64 Bit exe. Execute as Admin.

No external RDP posible.

Greetings from Germany

Alex

Hi Maurice,

Just installed the Free edition again and started it using the /profiler switch. Same happens as before, it loads, eats up to 25% cpu and nothing happens, I am not getting the profiler window either.

Where does it create it's logfile? Maybe it did create that so I can send that to you......

Best Regards,
Erik

@Erik,
Could you try to go in the command line with the Run As Administrator and execute the OptimizeRDMFree.bat?

Hi Maurice

I ran the optimize and got sevral errors. Unfortunately, I haven't pied the output to a TXT file. But some of the errors are listed below:

Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Compiling assembly SMDiagnostics, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 (CLR v2.0.50727) ...
Warning: Failed to load method token 690000d9 from profile data.
Warning: Failed to load method token 690000da from profile data.
Warning: Failed to load method token 690000d9 from profile data.
Warning: Failed to load method token 690000da from profile data.
Warning: Failed to load method token 690000d9 from profile data.
Warning: Failed to load method token 690000da from profile data.
SMDiagnostics, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

Also, the same situation as before, RDM starts and grabs 25% cpu and nothing happens.

Best regards,
Erik

I had this same issue - I installed the anniversary update, and I could not RDP to servers via an RD Gateway. I could remote to other servers over the web just fine. All this time I had been using the 32bit flavor. When I started the 64bit version, I was able to connect to those servers that use an RD Gateway.

I am using a licensed enterprise version. When you install the enterprise version, it installs both the 32 and 64 bit versions. You do not pick which one you install, more so which one you open.
Hope this helps anybody else having this issue.

I can confirm this, I use the 64-bit Enterprise version and am able to connect via RD Gateway perfectly, no issues. Haven't tested it with 32-bit version however.

I have a sneaky suspicion that under the hood, MS has tinkered with the anti-malware engine in Windows Defender and this is making it harder for 32-bit apps to use certain system functions, which in itself is not a bad thing. Until the Anniversary Update, I was able to use Greenshot (to capture screenshots) without problems. After the Anniversary Update, no go, it even completely locked up my system to such an extend that I had to hard boot it.

Best regards,
Erik

Hi,
has this issue been solved?
I've recently installed the Win10 Anniversary Update, and also upgraded to RDM Free 2.6.4.0, prior to noticing this issue. I found this thread, and have tried some of the suggestions.

My symptoms:
From RDM Free, RDP connection to Win2008R2 with gateway defined fails with message "Your computer can't connect to the Remote Desktop Gateway server. Contact your network administrator for assistance."
I've tried various options:
- Downloaded RDM Enterprise Trial. RDM Enterprise x64 Trial connects fine, RDM Enterprise x32 Trial has the same issue as RDM Free.
- Remote Desktop Connection Manager and MSTSC.exe both connect fine.
- The version of Windows the RDGateway runs on (or the version of RDGateway?) also matters. SBS2008 (Windows 2008SP2), Windows 2008R2 have the same issue (from both RDM x32 versions). RDGateway (TSGateway) on Windows 2012 and Windows 2012R2 connect fine from the RDM x32 clients.
- I've changed various options within the RDP properties (RDM Free). The only one that seems to change things is changing the Display field to "External". Display options "Embedded (tabbed)" and "Undocked" both have the issue.
- it is also definitely related to the TSGateway, as when accessing the server from INSIDE the network (ie TSGateway is not required), when "Bypass RD Gateway server for local adderesses" is ticked then connection works, and when unticked the connection fails as before.


Thanks
Rick.

For now the workaround is to replace one dll with the older version like explained in another thread:

===
You can replace the mstscax.dll library located in %windir%\SysWOW64\ with the "backup" file in "Windows.old\WINDOWS\SysWOW64".
You will need to take ownership of the file and give Administrators Full control access to be able to replace it. Please backup the file you are replacing
===


It's really a bug in Windows and we wait for a fix from them.


Regards

Thanks David.

I just want to confirm both the bug and the fix. This was driving me crazy all day today. Took me a while just to figure out that it was RDM and not RDP in general. Then I was sad that I would have to temporarily give up RDM while a solution was figured out. And then I found the solution right here in this forum. I'm using RDM Enterprise, and simply switching to the 64-bit version took care of things. Thanks for the work-around.


Matt

Hello,

As per the Windows Insider Hub and these popular links for Microsoft News;
http://www.windowscentral.com/windows-10-build-14393103-release-preview
http://www.winbeta.org/news/microsoft-publishes-changelog-windows-10-build-14393-103-heres-whats-changed
https://www.neowin.net/news/heres-what-got-fixed-and-improved-in-windows-10-build-14393103-for-pcs-and-phones

The upcoming update that should be released August 30th, 2016 will bring the Anniversary build to 14393.103.

This update includes repairs to Microsoft Remote Desktop (RDP).

Hopefully, this will address the issues we have all been experiencing.

Please don't hesitate to provide feedback once this update for Windows is released.

Thank you all!


Regards,

My ocmputer patched and rebootet yesterday and todauy RDP through a WS 2008 R2 RDGW is broken again

@Per-Torben Sorensen

What version of RDM are you running? Are you using RDM 32 or 64bit?

Best regards,

I agree with @Per-Torben Sorensen.

Over night my laptop applied an update "Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3193494)", and once again RDM 32bit (actually RDM Free 2.7.1.0) is not working when RDPing to W2008 servers.

Investigating shows C:\Windows\SysWOW64\mstscax.dll has been updated to file version 10.0.14393.187. I re-"fixed" this by overwriting this file (after taking ownership of it) with a copy restored from prior to the W10 Anniversary Update, in my case file version 10.0.10586.545