HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore\Pending Rename Operations2 HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore\Pending Rename Operationsĭata:CurrentControlSet\Control\Session Manager\PendingFileRenameOperations I searched the registry for "PendingFileRenameOperations" and found no less than 8 occurrances. I ran the installer with the installed application intentionally running so that I got the " This system must be restarted to complete installation." message.
INSTALLBUILDER REPORT JSON FULL
Your answer gave me only the final key but not the full registry path. The place in the registry where the "in-use" files are listed. The location of the list is what I was looking for. What I was asking was where does it put the list of these "in-use" files so we can determine which files are in use and resolve it. So the mechanism is just to try to write the file and the failure to do so, indicates an "in-use" file. It knows from getting an error when it tries to write to the file and as you say it creates a registry entry to have them renamed at reboot. Clearly InstallBuilder knows which files are in use. Your response however did give me some of the answer I was looking for.
Thank you EdT for your response, however I think you misunderstood my question.
INSTALLBUILDER REPORT JSON INSTALL
So fundamentally, there is no simple way to fix this - you are going to have to find out which files are candidates for being locked at install time, and put in whatever remedial measures are required into your install. When you are dealing with a server, you may wish to just provide messages to the operator instead of risking server service by shutting down processes automatically - just in case it is a shared DLL used by another vital process.
There is nothing to stop you writing a check script in any language you prefer, and run this as the first step in your installation, so that you can abort the installation if files are locked, or take the necessary steps to unlock them. You can find out which files are "in use" by interrogating this registry key when the reboot message comes up, and add steps to your install to ensure that those files are not in use when the installation commences, Generally, it ends up being a DLL that is not unloaded, and it may necessitate steps to include an "End Process" command in your installer to ensure that the process is shut down and any DLLs released.
When I think about it, there is no installer tool that provides this functionality (as far as I am aware), as the solution is to create the "PendingFileRenameOperations" registry key and mark the need for a reboot. Installbuilder is an ancient product that does not have any inbuilt mechanism for checking "in use" files.
0 kommentar(er)
