Shay's answer is correct. Recent versions of Windows Installer behave like this. The Windows installer faces many problems to make sure that you can avoid a reboot during uninstall by re-matching the used DLL files, etc. Typically, a running application can continue to work after uninstallation, and some cleaning will occur when the application is turned off, the rest after the next reboot. The fact is that if the Windows installer can move the executable files to another place, start all the applications and replace the ones that were in use (but the memory backup has been redone), and all that is required removes a little unnecessary garbage on the next reboot, why force restart the computer? There is no need to display the Files In Use dialog box, so the situation does not occur.
This can cause problems if the application tries to access the file being deleted, but I assume the risk is considered low. If the application should know that the uninstallation is ongoing, then work with Restart Manager should work - Windows will inform you that the uninstallation is in progress. Otherwise, Shay is correct. Write, if necessary, deleting user actions to inform the application to close.
Phildw
source share