In our project we silently call multiple sub-installers from the main installer [also to keep in mind, the sub-installers can be standalone installers by themselves]. On some windows machine we see this "file is locked" issue during installation. There are some common third-party executables being called by the runProgram in some of the sub-installers. When a runProgram exits without error (exit code 0), is there a possibility that windows process is still using that executable?
When the 2nd sub-installer begins its execution it unpacks the same 3rd party executable to the same location and consistently on few machines we see error unpacking the file since the file is locked by the previous process or something. Can that happen? Any solution?
Please sign in to leave a comment.