When an MSI detects some process holding a resource that needs modifying, and user declines to close the process, MSI postpones the modification to the reboot time.
The question is: where to look for the list of such actions scheduled to run after reboot (after I installed the application, and was notified that the reboot is necessary, but didn't reboot yet)? I need to understand what exactly is that in an application's installer that requests closing seemingly unrelated process (on first install of the application in question), and finding the offending DLL/registry key/whatever could hopefully help identifying (and possibly ultimately fixing) the issue in the application's installer (namely, LibreOffice reportedly asking to close Firefox).
I believe that this question is properly asked here at SuperUser as opposed to StackOverflow, since, despite the ultimate goal is fixing an application, the immediate problem is detecting the postponed actions in user space.
Thanks!