Hi,

I am having a following situation:
- app running as Windows Service
- Updater enabled and configured to support silent updates via Support service
- manually creating a scheduled task in Powershell custom action to periodially run the Updater

In case everything is fine then the update process works quite smooth. All good here.

BUT when the scheduled task is triggered and there is some kind of a problem during update process (e.g. invalid installer url in "updates.txt" so it cannot be downloaded) then Updater.exe hangs forever and scheduled task does not run next time as Updater cannot run in multiple instances. This is a showstopper for us as it is definitely not a reliable behavior.

What do you suggest, please?

Hi,

Please make sure you define proper settings for the scheduled task, as you can configure the task in case of a failure.


Check the New-ScheduledTaskSettingsSe options.

Another approach that you can use is withing your application, periodically check to see if any check for updates process was triggered, check its start date and if it takes longer than a specific time, you may consider that the task had failed and close the Updater's process.

Let me know if you need any help.

Best regards,
Dan

I have tried but Windows does not seem to care, the process keeps hanging. It is clearly a poor design of error handling within Updater app. I have found out that it manifests a faulty behavior when updates file contains invalid url of the installer to be downloaded. When can I expect it to be fixed please?

Regarding your second thought - nope, not going to happen. We cannot change the app with the installer stuff.

I have found out the root cause - I was missing the "-nogui" switch.

So I think this page should be adjusted as well
https://www.advancedinstaller.com/user- ... dates.html

Hello,

Thank you for your followup on this.

It's great to hear that everything is now working as expected.

We will try to improve our articles, thank you for your suggestions.

Best regards,
Liviu