WiX: Avoid showing files-in-use dialog and just prompt for reboot at end of install

Question

I am using <MajorUpgrade> in WiX 3.6 to force an uninstall of the previous version of my application when installing a newer version. My application installs an extension DLL file into Windows Explorer, so on uninstall the Files In Use lists Explorer and defaults to shutting down the listed application. This does kill Windows Explorer as my shell goes away (which is somewhat jarring for the user), however I still get an error saying that not all applications could be shutdown and states a reboot will be necessary. My preference is to avoid this thrash and skip the Files-In-Use dialog just inform the user of the required reboot at the end. Is there a way to tell WiX to skip the Files-In-Use dialog?

Answer 1

 <Property Id="MSIRESTARTMANAGERCONTROL" Value="Disable"/>

This works for me but I'm not trying to kill any system services.

Did you try "DisableShutdown" as well?

"Windows Installer uses the FilesInUse Dialog. This setting disables attempts by the Restart Manager to mitigate restarts when installing a Windows Installer package that has not been authored to use the Restart Manager. The installer still uses the Restart Manager to detect files in use by applications."

http://msdn.microsoft.com/en-us/library/aa370377%28v=vs.85%29.aspx

-Robin

Answer 2

You can disable the Restart Manager integration by setting the MSIRESTARTMANAGERCONTROL property equal to "Disabled" (from MSI SDK). You can also try to remove the FilesInUse dialog, but the static Internal Consistency Evaluator (ICE) validation will complain. My hope is that disabling the Restart Manager will be enough to stop trying to pull the resources out of explorer.exe.

Answer 3

I also have a situation where the attempt to close and reopen applications will always fail. A reboot is required. I attempted to use all of the solutions offered here. None of them worked. I was able to resolve the issue simply though. This article was the clue. https://msdn.microsoft.com/en-us/library/aa369546(v=vs.85).aspx

I added a condition to the InstallValidate standard action that always resolves to false. The action never runs. The standard action only deals with disk costing and open processes, Stopping the action from being called stopped all offers to close things. I also had to set the Windows Installer REBOOT property to FORCE to get the prompt to reboot at the end of the install.

My application has a small disk footprint. If having my install fail later in the process because the disk is full would be a big problem, I would find a way to do costing myself.