Exact setup behavior description, when prerequisite needs a reboot
Using InstallShield 2018, I added Visual C++ 2015-2022 Runtime prerequisite to InstallShield setup project. When VC++ Runtime is installed first time on some computer, it may request reboot. The behavior of the setup is defined in InstallShield Prerequisite editor:
I selected the last option: Reboot the machine and resume on reboot. Resulting behavior: VC++ Runtime is installed, and computer goes to reboot, even without user prompt. After reboot, setup resumes.
I want to have the following behavior: If prerequisite needs a reboot, setup continues. In the end, when the product is installed, setup should ask user to reboot, user may accept or reject this.
What option in the list should I select, to get desired behavior? Their description is not clear enough.
Third option should get the desired behavior.
Note it, fail to resume if the machine is rebooted, and reboot after the installation.
For artificial reboot, you might play with 'PendingFileRenameOperations' value in the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
- InstallShield 2023 Basic MSI: How to change the value of INSTALLDIR at runtime?
- MS Access DB Engine (32-bit) with Office 64-bit
- InstallShield InstallScript-MSI vs. InstallScript-non-MSI
- Installshield major upgrade doesn't uninstall old version
- Accessing command line arguments Installshield Installation Designer UI
- Updating InstallShield .ism (MSI) file with beatifulsoup and maintaining its formatting
- Copyright details doesn't show Organization name
- Managed Code custom action in .Net Core 6 or later
- How to set Required Execution Level to Administrator for Basic MSI project type with MSI file
- WIX Toolset - Custom Action command doesn't correctly detect Windows 10 version
- Using Inno Setup to patch an Install Shield Application
- Signing in Inno Setup fails with "Sign Tool failed with exit code 0x1"
- Is there a good alternative to Install Shield?
- The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception
- How to create a custom installshield dialog skin?
- How to pre-set MSI SecureCustomProperties that are not defined in Properties to allow silent installation?
- How to prevent restart dialog caused by MSI 1610 error
- How do I avoid triggering MSI self-repair with my WiX / MSI package?
- Windows Installer can't find registry entry
- How to add a prerequisite check for .NET framework 4.5.2 in InstallShield Basic MSI project
- Prerequisite condition for VC++ x86 runtime
- Exact setup behavior description, when prerequisite needs a reboot
- Environment variables and other features are missing in InstallShield project
- Installshield Silent Uninstall not working at Command Line
- ISRegSpy error on Image Build that contains a VFP / COM / OlePublic DLL
- Installshield Installer MSI Error : Could not load assembly by name "abcd", Version : 6.0.0.0
- ISEXP : fatal error -6017: Internal build error
- InstallShield Dynamic File Linking can't overwrite
- Registry changes in patch moved to WOW6432Node key for 64-bit msi in Installshield QuickPatch project
- Command line arguments for msiexec break on PowerShell if they contain space