RDM incorrectly detecting that it is the current version

RDM incorrectly detecting that it is the current version

avatar
STGdb

Good morning. I have RDM 10.5.4.0 installed on my work system. I have the option enabled to check for updates (including BETA) and it has worked fine up until recently (I just realized that it isn’t working). When I select to “Check version” from within RDM (tested with both x86 and x64 flavors), a popup message informs me that “Your current version is up to date”. However, Devolutions currently offers RDM 10.5.6.0 (BETA) for download. The update check last worked when updating to 10.5.4.0. I’ve disabled the update check completely and then enabled it again and I’ve also tried changing the option to check for BETA’s and reverting back, but I end up with the same results. This happened once before (sort of) and the issue at that time was that the new version needed to be updated on the Devolutions site so that the RDM client recognized that the update was available. However, I don’t think that this is the same issue as before because my RDM client at home recognized that the update was available earlier this morning and I was able to install it successfully via RDM (clicking the UPDATE button). For some reason, my RDM client at home updated but an hour later my RDM client at work didn’t detect the update.




Thanks much
edited by STGdb on 5/1/2015

All Comments (3)

avatar
David Hervieux

This is strange. I will look into it right now.

David Hervieux

avatar
Hubert Mireault

Hello,

This will be fixed in the next beta version of RDM, ironically. :)

For a quick fix, you can edit your RDM configuration file which can be normally found in C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager.cfg . You need to add this line to the file: <CheckForUpdateIncludeBeta>true</CheckForUpdateIncludeBeta>
This needs to be added under the "<option>" line and it should prompt you for the latest beta version when checking for updates. This fix is only temporary though and our next beta build will have the true fix.

Regards,

Hubert Mireault

avatar
STGdb

Thanks. I made the change and when I ran the update check, it worked as expected and saw the latest BETA release. The only thing was that the file (RemoteDesktopManager.cfg) was actually in the following directory tree:

%AppData%\Local\Devolutions\RemoteDesktopManager

But we’re all good. Look for the fix in the next BETA. Thanks again