Download and Update on Close doesn't seem t work

Hello,
Could you try to disable in File->Options | Use Devolutions Updater?



Regards

No, I haven't. So I unchecked this option, but I'll have to wait for the next update to try it 😉

Hello,
Could you try to disable in File->Options | Use Devolutions Updater?



Regards

OK, I just tested this today, and it works. But why wouldn't this work with the Devolutions Updater?

Hello,
This is not the expected behavior and it should work with Devolutions Updater. Could you verify if you find anything in the RDM logs (Help->View Application Logs)?

Regards

Hello,
This is not the expected behavior and it should work with Devolutions Updater. Could you verify if you find anything in the RDM logs (Help->View Application Logs)?

Not really. The logs contain only a couple of lines (literally only 10 lines) all about the upgrade to version 2022.3.15.0. For the latest update to 2022.3.18.0 I didn't use the Devolutions Updater (as you suggested), but anyway there aren't any log entries either.

So I suppose I wait for the next update, try the Devolutions Updater first and then inspect the logfiles.

This is not the expected behavior and it should work with Devolutions Updater. Could you verify if you find anything in the RDM logs (Help->View Application Logs)?

So I checked today and found a new update. So I re-enabled the "Devolutions Updater" (closed the app and restarted the app, to make sure the setting will be honored). Then choose "download and install on close" in the update window. So far nothing happend right away. Looking at the log doesn't show any entry.

So I closed the app - still nothing happening. Restarted the app to check the log, but still no entry.

What would be the expected behavior?

Hello,
Do you mean that the updater does not open at all?

Regards

Do you mean that the updater does not open at all?

Right, nothing at all is happening. Complete silence after clicking to "download and update" (with Devolutions Update enabled) as well as when closing the application.

Hello,
I will add some debug information for the next update. Could you try to open the Windows-Profiler and verify if anything is added to it when you click Download and Update?

Regards

I will add some debug information for the next update. Could you try to open the Windows-Profiler and verify if anything is added to it when you click Download and Update?

In what version will this be available? And: could you give my a hint what excatly you mean with "Windows-Profiler"?

Hello,
The updated version is planned to be released tomorrow. Here the Profiler window I was talking about:



Regards

Hello,
The updated version is planned to be released tomorrow. Here the Profiler window I was talking about:



Regards

So I assume I first need to update to the latest (greater than 2022.3.23) version and the run the profile for the next update?

Hello,
You can try with the current version but retry it also with the next one. We have few debug logs already.

Regards

Hi,

so I tried checking everything before I hit the update button ...



and this is what I got in the profiler:

Installing update with Devolutions Updater:C:\Program Files\Devolutions\Remote Desktop Manager\Devolutions.Updater.exe
ImageFileName:C:\Users\eiben\AppData\Local\Devolutions\RemoteDesktopManager\Images\Themes\DataEntryWebSmall.png
ImageFileName:C:\Users\eiben\AppData\Local\Devolutions\RemoteDesktopManager\Images\Themes\DataEntryWebSmall.png

When I close the app - still nothing happens trying to update from 2022.3.24.0 to 2022.3.26.0. When I the restart the app and look at the profile, it's empty.

However, this is what I found in the application logs:

Date	Version	Type	Message
07.12.2022 01:01	2022.3.24.0 - 64-bit	2	"System.ComponentModel.Win32Exception (0x80004005): Das System kann die angegebene Datei nicht finden
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Devolutions.RemoteDesktopManager.Managers.UpdateManager.InstallWithUpdater()"
07.12.2022 01:01	2022.3.24.0 - 64-bit	2	"System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\eiben\AppData\Local\Temp\RDM\Devolutions.Updater.exe'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
   at Devolutions.RemoteDesktopManager.Managers.UpdateManager.InstallWithUpdater()"

I suppose that's explaining why ... it seems that the updater.exe is not found, probably because it's looking at the wrong location.


Cheers,
Henning

Could you try to force the update with the profiler open?

Ctrl+Click on the ribbon button Check For Update to simulate the new version found (this is an hidden key to force the update). Execute the installer and check if the Updater is copied into:

C:\Users\eiben\AppData\Local\Temp\RDM\

Regards

Hi,

when I click on "Download this version and install when application is closed" nothing gets copied to the temp-folder. But the profiler says

Installing update with Devolutions Updater:C:\Program Files\Devolutions\Remote Desktop Manager\Devolutions.Updater.exe

when I click "Download this version and install now" the installer is copied to the temp folder and the profiler shows

Installing update with Devolutions Updater:C:\Program Files\Devolutions\Remote Desktop Manager\Devolutions.Updater.exe
Copying Devolutions Updater in temp folder:C:\Users\eiben\AppData\Local\Temp\RDM\Devolutions.Updater.exe

When I now click "cancel" the updater exe exists in the temp-folder. So I tried selecting "install when application is closed" and closed the application. But upon closing the application the temp-folder is being removed (and mabye because of that the updater cannot be started?)

All this i tried with 2022.3.24.0 ... so now I updated to 2022.3.26.0

After updating to 2022.3.26.0 the behavior is slightly different. So I started RDM and used the CTRL+Check-for-update trick. Looking at the temp-folder I see immediatly the updater.exe in the folder as well as an install.log. This is new - previously this file wasn't present.

But closing RDM again removes the C:\Users\eiben\AppData\Local\Temp\RDM\ folder. However I noticed a folder c:\Users\eiben\AppData\Local\Temp\RDMUpdate\, which was still present after closing RDM. There is a file called Setup.RemoteDesktopManager.2022.3.26.0.msi, But I'm not sure this is after or before updating to 2022.3.26.0.

I hope this helps ...

Cheers
Henning

Hello,
Your logs were useful. I have some clue to investigate.

Regards

With 2022.3.29.0 this still doesn't seem to work 🙁

Hello,
You've tried to update RDM 2022.3.29 to 2022.3.30?

Regards

So now I'm on version 2022.3.30 - let's see how the next update goes 😉

Nope, no change in behavior (just tried to install the update to 2022.3.31 this way)

That's sad. It still does not update on Close? Do you get anything in the logs?

Regards

[23.01.2023 18:30:20 - 2022.3.30.0 - 64-bit] Error Silent: System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Runtime.InteropServices.SafeHandle.InternalDispose()
   at System.Threading.WaitHandle.Dispose(Boolean explicitDisposing)
   at System.Threading.WaitHandle.Close()
   at Devolutions.RemoteDesktopManager.Business.HttpBrowserLinker.Run()
[23.01.2023 18:30:20 - 2022.3.30.0 - 64-bit] Error Silent: System.Threading.ThreadAbortException: Thread was being aborted.
   at Devolutions.RemoteDesktopManager.Business.HttpBrowserLinker.Run()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
[23.01.2023 18:30:20 - 2022.3.30.0 - 64-bit] Error Silent: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\eiben\AppData\Local\Temp\RDMUpdate\Devolutions.Updater.exe'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
   at Devolutions.RemoteDesktopManager.Managers.UpdateManager.InstallWithUpdater()
[23.01.2023 18:30:20 - 2022.3.30.0 - 64-bit] Error Silent: System.ComponentModel.Win32Exception (0x80004005): Das System kann die angegebene Datei nicht finden
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Devolutions.RemoteDesktopManager.Managers.UpdateManager.InstallWithUpdater()

Hello,
Sorry for the delay. Were you updating on application close or clicking Update Now? From the log I see that RDM is unable to find the updater copied in ...\AppData\Local\Temp\RDMUpdate\

Regards

I wanted to "update on close". "update now" works just fine as expected.

Hello,
I asked our QA (3 of them) to try to reproduce it and unfortunately they were unsuccessful. We will add an option to configure a custom Download/Update path and try to use it. I see that RDM is unable to find the updater in the temp folder and I suspect that for an unknown reason it's get deleted.

Regards

Hello,

An option to set a custom download path has been implemented internally. It will be available with the 2023.1 release.

The setting can be found in the updater directly, or in RDM via File -> Options -> Paths -> "Custom download path"

Regards

OK, I will test this as soon as this will be available.

Today I installed the update from 2022.3.33 to 2022.3.35 ... and it worked to "download & install on close" ... I'll keep an eye open to the next update