One dll in our installation can end up in the rundll32 process launched by Chrome. During un/install, install detects and prompts (prompt 1) that rundll32 need to be closed and that the install will attempt to close it. Upon clicking OK however, the installer says it can't close rundll32 (perhaps due to some permission issue) and tells user (prompt 2) that process should be terminated before continuing. When user clicks OK and proceeds with the install, the dll get unloaded from rundll32 process and gets replaced anyway.
This is fine, but would be confusing to most users since they would think that the installation did not complete properly. So my question is, is there a way that we can detect if the process that's unable to close is rundll32 and if so, upon failure to close (which is usually the case when our dll is involved) we customize the prompt 2 above to append hint that Chrome/rundll32 has our dll in use and it may be okay to proceed or if the user wants, he can manually terminate rundll2 or close Chrome before proceeding?
FOLLOW US
Get the latest news in Application Packaging