This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- MsiInstallProduct, system reboots after install despite REBOOT="ReallySuppress"
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 04, 2014
10:01 AM
MsiInstallProduct, system reboots after install despite REBOOT="ReallySuppress"
I have a frontend that launches our installs using the function MsiInstallProduct(), and I pass into the command line REBOOT="ReallySuppress". Yet, some customers are having their systems reboot at the end of the install process without warning. Looking at one of their logs there are a couple of shared dlls under C:\Program Files\Common that are locked. I looked at a log for another customer and did not find anything that indicated a problem requiring reboot.
What I would like to do is to find a way to completely suppress reboots, but I don't think anything short of a hack exists for this. Am I wrong?
Or, I would like to display a message box at the end of the install if the system needs to restart. Am I able to do this when I use MsiInstallProduct()?
What I would like to do is to find a way to completely suppress reboots, but I don't think anything short of a hack exists for this. Am I wrong?
Or, I would like to display a message box at the end of the install if the system needs to restart. Am I able to do this when I use MsiInstallProduct()?
- Tags:
- file locked reboot
- msiinstallproduct()
- reboot without warning
- reboot="reallysuppress"
- restart
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 06, 2014
03:30 PM
The parameter REBOOT="ReallySuppress" is doing its job. Although I had some files that were locked during installation, the fact that I used that parameter prevented the system from rebooting. However, my frontend launches several setup prerequisites, namely the vc++ 2010 and vc++ 2012 redists, and I realized that I was launching them without passing the /norestart switch. It turns out a few customers had one or more dlls associated with these redists locked during installation, and that is what caused the system restart. Problem solved.
