Updater causes reboot - Advanced Installer Community
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Updater causes reboot

Hi,
If my application has a modal message box showing when the auto updater installs it causes Window 7 to do a reboot when the installer completes. The user is not given an option, it just logs them off and reboots. Very unfriendly if they are in the middle of some other tasks. If my application does not have that same modal message box showing when the updater install completes then the reboot does not occur.

The updater installer uses the Updates > Update > Auto Close Applications settings as follows:

Main Executable Path: [APPDIR]<exeName>
Window Title Prefix: <application name>
Application Restart >
Disable Auto Restart (off)
Restart Always (on)
Command Line: <blank>

Has anyone else seen this occur? Has anyone come across a possible solution? The reboot should not be necessary just because their is a modal message box showing.

Another question: Why when minimized does the auto updater icon go into the "show hidden icons" group of the running programs by the system clock? If I do an updater install and minimize that window the updater EXE is not inactive, it's very much active, I think it should show all the time, not move the "show hidden icons" group.

Thanks.
PS: I have now confirmed this reboot behavior in 3 out of 3 attempts; so it is consistently bad.
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Updater causes reboot

Hello,
If my application has a modal message box showing when the auto updater installs it causes Window 7 to do a reboot when the installer completes. The user is not given an option, it just logs them off and reboots. Very unfriendly if they are in the middle of some other tasks. If my application does not have that same modal message box showing when the updater install completes then the reboot does not occur.
It seems that the modal message box causes this behavior. Can you please tell us why do you have a custom dialog when the updates are applied? The Updater already has an User Interface where the user is informed with the download and installation progress.
Another question: Why when minimized does the auto updater icon go into the "show hidden icons" group of the running programs by the system clock? If I do an updater install and minimize that window the updater EXE is not inactive, it's very much active, I think it should show all the time, not move the "show hidden icons" group.
I'm afraid that the user decide how “icons and notifications appear in the notification area” and not the application itself. Most icons are hidden by default in Windows 7, but can be promoted to the notification area manually, by the user. To keep users in control of their desktops, there is no way for your program to perform this promotion automatically. Windows still displays notifications for hidden icons by promoting them temporarily.

You can take a look on the Notification Area - Design concepts article which may be useful to you.

Please let us know if you have other questions.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Re: Updater causes reboot

Hi Dan,
It seems that the modal message box causes this behavior. Can you please tell us why do you have a custom dialog when the updates are applied? The Updater already has an User Interface where the user is informed with the download and installation progress.
The reason is that during the start-up of our application we (potentially) show a modal MessageBox (for instance when the application has expired, say one year after receiving an update), then (potentially; user can configure this) followed by another modal selection box to Open a new document or Open from the MRU list of recent documents. It is during our application start-up that we check to see if it's the most current version, so that is why the Auto Updater is running and a dialog might be showing at the same time.

I'm surprised that a modal dialog forces the machine to reboot, that doesn't make sense to me why that would be the necessary...is that an MSI restriction or an AI restriction?

I suppose we will have to change where/when our application checks to see if it is the most current version since our user's are already accustomed to the modal dialogs we show.

Thanks.

Return to “Common Problems”