Block Reboot

[Gregr]

Is there a way to prevent reboot in SF9?
I know about the possible issues if the system is not reboot. Won't be a problem in this case.
Greg

[Ulrich]

An installer built with Setup Factory can request a reboot if:

• a dependency module needs to perform a reboot before installing the next product, for example a reboot may be required after installing certain versions of the .NET Framework. In this case, the reboot may use the System.Reboot() action to restart the system, as part of the installation script of the dependency module.
• a reboot may be required to replace a file which was in use during the setup. In this case, the global variable _NeedsReboot will be set, which would trigger a dialog to be shown at the end of the install, when g_HandleSystemReboot() is called in the On Shutdown script.

If Setup Factory is requesting a reboot, then most likely it is indeed needed to complete a pending operation. You can override the reboot request, depending where it was created, or by commenting out the action, or by setting _NeedsReboot forcefully to false.

Ulrich

[Gregr]

Hi Ulrich,
Thanks for your suggestions.
In this case there is no dependency module which causes a reset.

In an attempt to block the reboot I have place the following in both the "Post Install" and "Shutdown" actions:
_NeedsReboot = FALSE;
SessionVar.Set("_NeedsReboot", FALSE)
local _NeedsReboot = FALSE;

None of these stop the reboot. Am I missing something?
I'm not sure what you mean by "setting _NeedsReboot forcefully to false."

Thanks for your help,
Greg

[Ulrich]

None of these stop the reboot. Am I missing something?

Apparently there is something being done which you didn't mention so far. That sample code should prevent the request to reboot - if the installer wants to reboot the computer.

I'm not sure what you mean by "setting _NeedsReboot forcefully to false."

I mean setting _NeedsReboot to false, ignoring the previous value. You could check if it was actually set to true before you force it to false. If it is not true, this would mean that some task performed during the install triggered the request, which can't be ignored - it not NOT the installer who is requesting the reboot, but the OS itself. This can happen, for example, if you do things like messing with the configuration of the UAC, which obviously you aren't doing, right?

If you don't want to post your project file publicly, you can contact me privately for consulting.

Ulrich

[Gregr]

Thanks for the advice.
I have found:
1. After normal installation, the computer does not reboot.
2. After silent installation, the computer always reboots.

The problem is that the customers IT department wants to distribute the application using the silent install but does not want the users computers to reboot.
Any suggestions?
Greg

[Ulrich]

It appears that you are doing something differently during an interactive install, which is not done in a silent install. I cannot guess what this might be, you have to figure this out by yourself, make your project file available.

Ulrich