Description: Prior to 6.2 when windows setup encountered a locked shared file it identified the program using this file and prompted to terminate the offending program. 6.2 no longer does that, if it encounters a locked file it displays an information message and prompts for reboot after the installation even when all usual suspects where killed before the installation was allowed to proceed. win 10 64 Please restore the pre-6.2 handling of locked files. Steps to Reproduce: 1. make sure that some LO files are locked by running programs - in my case it usually where ms outlook and mozilla seamonkey 2. start setup Actual Results: a message box informing that files are locked and PC will have to be rebooted after the installation will pop up and after the installation setup will prompt to reboot Expected Results: a message box listing programs locking the files should pop up with options to either terminate these programs or continue and reboot afterwards Reproducible: Always User Profile Reset: No Additional Info:
No change in this regards was made in installer. I believe that there was something else on your system that was not possible to resolve by closing applications, and thus led to reboot request. Windows Restart Manager (the component of MSI that is performing the function discussed) has limited abilities, e.g. it cannot restart a service if it's a service that locks something. I let it UNCONFIRMED though, to see if someone is able to reproduce some consistent change in behavior in 6.2.
Yes, I tried installing 6.1.5 and it now behaves the same way - my bad, sorry. It was not a service however - when re-installing 6.2 I closed all programs which usually lock the files and it installed without requesting a reboot.