Free version of RDM locks up with new Spring Update for Windows 10, build 1803

Free version of RDM locks up with new Spring Update for Windows 10, build 1803

avatar

While we wait to submit the Enterprise version to our application review board to purchase site licenses, some of us are using the Free version of RDM, build 4.5.3.0. We noticed after the upgrade to Windows 10, build 1803 that was released earlier this week, RDM freezes if you double-click on a server to RDP into and put in your password. As soon as you do, the program locks up and you have to close out via task manager or wait for Windows to tell you to close out. A few of us have reproduced the issue. However, if you attach the username/password to each server in the properties so you don't have to manually type it in, it works fine.

2018-05-02 11_19_54-Remote Desktop Manager Free [PxM Console].png

All Comments (15)

avatar

Hello,

We received a similar report from a user last week.

We discovered that Windows itself was causing the crash.

But just to be sure, could you please look for a log about the crash in Windows Event Viewer and show us the details?


Best regards,

Mark Beausejour

avatar

I see it. Attaching a screenshot of it. I did send a report off to MS when it prompted me to. Not sure if they actually do anything with them ;)

2018-05-02 11_51_49-Event Viewer.png

avatar

Hello,

If you do the same through MSTSC.exe, does it work as expected?


Best regards,

Mark Beausejour

avatar

Yep, it works fine there.

avatar

Hello,

In embedded mode, we use the Microsoft ActiveX to establish the RDP connection. In fact, it’s the same ActiveX that is used in RDC Manager from Microsoft.

In external mode, we use the native Microsoft RDP (mstsc.exe).

That being said, could you please try RDC Manager from Microsoft to see if you experience the same issue with that software?

https://www.microsoft.com/en-ca/download/details.aspx?id=44989

Best regards,

Mark Beausejour

avatar

Actually, RDCMan worked. I was thinking like you were since the ActiveX control would be the same due to the credentials box that appeared. But I'm able to remote into servers here entering my creds.

Is there anyone upgraded to 1803 over there that can test? I guess another comparison would be to find someone that is working and compare the settings within the RDP properties.

avatar

Hello,

Could you please try the solutions here?
https://help.remotedesktopmanager.com/troubleshooting_csf.htm

This is what i suggested to the user who had a similar issue and it seems to have done the trick for him.


Best regards,

Mark Beausejour

avatar

Hi Mark,

Neither worked for me. SFC said I had no issues and .NET repair tool didn't find any issues. Remember, there are multiple people here in my Dept. experiencing this as well. Are there any logs in the program I can send to you?

avatar

Hello,

Could you please show us a screenshot of the Properties of your RDP session? We would like to see the settings you have.

You may hide any sensitive information.


Best regards,

Mark Beausejour

avatar

Not sure how many you want but these were all of the sub tabs on the first Property screen. Other than the first screen, they should all be the default and I did not change any of the settings of the tabs on the left side.

RDM - Properties7.png

RDM - Properties6.png

RDM - Properties5.png

RDM - Properties4.png

RDM - Properties3.png

RDM - Properties2.png

RDM - Properties1.png

avatar

Hello,

Could you please check/uncheck the NLA option in the Connection tab of your RDP session?


If that doesn't work, could you please try RDM Enterprise instead to see if you have the same issue?
https://remotedesktopmanager.com/home/download

You can request a trial license here;
https://remotedesktopmanager.com/trial


Best regards,

Mark Beausejour

avatar

So that worked for me (unchecking the box) but did not work for my co-worker. However, we are in the process of purchasing a global license so he said he would just wait and check it out then.

Thanks for all of your help!!!

avatar

Hello,

Thank you for your reply!

We're pleased to see the solution has worked for you.

Please do not hesitate to provide feedback if the issue remains for your colleague going forward.


Best regards,

Mark Beausejour

avatar

I can confirm that the Enterprise version doesn't have this issue. We received our Enterprise key today so all is definitely good! :cool:

avatar

This should be fixed soon in the Free edition as well.

Regards

David Hervieux