Re: [WiX-users] Reboot and ReallySuppress

2015-05-01 Thread Henri Hein
Phil Wilson: Thanks for taking a look at the log. After some trial and error, I tracked the issue down to code inside my custom action executable. I called InstallHinfSection(), and that was the cause of the restart prompt. I replaced this with DriverPackageInstall(), and I no longer see the re

Re: [WiX-users] Reboot and ReallySuppress

2015-05-01 Thread Phil Wilson
I couldn't see anything in that log either, except an error 16 with no obvious source - "The directory cannot be removed. " but no clear indication that it is causing the reboot. I have noticed that it can be hard to suppress reboots during an upgrade when they are caused by the old uninstall. REBO

Re: [WiX-users] Reboot and ReallySuppress

2015-04-28 Thread Henri Hein
Thanks, Phil. Here's a link to the full log file: http://1drv.ms/1JyRdgH I should have mentioned as well that this particular log was from an upgrade, though the problem happens on both upgrades and clean installs (installs where I uninstall first, reboot, then install). Thanks, - Henri --

Re: [WiX-users] Reboot and ReallySuppress

2015-04-28 Thread Phil Wilson
You should probably post a link to the entire log for others to see. For example, I don't know if you've looked at the possibility that a custom action is resetting the REBOOT property somewhere. --- Phil Wilson On Tue, Apr 28, 2015 at 1:15 PM, Henri Hein wrote: > My message went ou

Re: [WiX-users] Reboot and ReallySuppress

2015-04-28 Thread Henri Hein
My message went out prematurely, but I think the question is clear enough. Does anyone have any ideas why the reboot might be happening, and how I can really suppress it? There wasn't anything immediately obvious before the last "Decrementing counter" log line. Thanks, - Henri On Tue, Apr 28,

[WiX-users] Reboot and ReallySuppress

2015-04-28 Thread Henri Hein
My installer keeps prompting for a reboot, and I am trying to find out why. I set the Reboot property to 'ReallySuppress' with the following XML: I have run the installer with verbose log, trying to look for the clues listed on this helpful blog post: http://blogs.msdn.com/b/windows_installer_