restartmanager

With Windows installer 4.0 and Restart Manager, would it be safe to assume that "Restart Manager" would take care of shutting down applications and hence there is no need for any sort of custom actions to handle shutdown of processes holding files, meant to be updated? Are there any exceptions where "Restart Manager" might not shut down applications? Ofcourse, i understand that when a policy such as DisableAutomaticApplicationShutdown is enforced, Restart Manager is disabled. Does the process to be shutdown have to satisfy some criteria to be able to be shutdown by Restart Manager? I am

I am experiencing a strange issue with the Restart Manager API: RmGetlist(). To simulate a file locking scenario, i am making use of the following 3rd party file locking utilities: Ez file locker - http://www.xoslab.com/efl.html - File locker http://www.jensscheffler.de/filelocker The strange issue here is that, both these utilities lock a certain file, however, RMGetList() fails with an Access denied error(5) with the first file locking utility(Ez File lock) whereas it works with the second file locking utility. What could possibly be wrong here? Why would RmGetList() fail with one file

I've got the issue, that when uninstalling (or upgrading) the Restart Manager is complaining about a file in use situation, and so is forcing a reboot: RESTART MANAGER: Detected that application with id 7000, friendly name 'javaw.exe', of type RmCritical and status 1 holds file[s] in use. RESTART MANAGER: Did detect that a critical application holds file[s] in use, so a reboot will be necessary. The service that RESTART MANAGER is complainig about, is a java-based service. The service (here called myservice.exe) is recursively starting java child processes: myservice.exe --run ↳ javaw.exe -

When ever there is an update patch of files that have to be replaced with the existing files and if one of the files is being used by any of the processes, then a file in use dialog box pops-up.I wanna avoid that dialog box and get that file queued up for installation so that it can be installed at the time of system reboot. I have read that the queuing the files for update at the time of reboot is the inbuilt functionality of windows installer. Can someone suggest me the way to remove that FileInUse Dialog box. I tried setting up the "MsiRMFilesInUse" property to "0" but it didn't work.