Just taking a guess here but it appears to me that in looking at your log it looks like you used dynamic links for some components which will generate separate GUIDsfor all your files in the component. Perhaps it's not the files, its the component GUIDs that are not matching up. Use the MSI Diff tool to compare MSI's and see how the files table matches up. When creating minor updates it is extremely important to keep these GUIDs the same. This is most likely why when you uninstall - some files are remaining because the new installer does not have the same GUID in it. I had similar issues when a new folder was added to a dynamic-linked component - threw all the generated GUIDs off.  ... View more

What do you mean install on a 1.2GB disk? How big is the installer? Do you have access to other drives from this system? If I remember correctly, you can change the temp folder for the installer to extract to before installing but it's been many years since I've dealt with MP installers. ... View more

Short answer, yes, fully automated. IS does have a pretty robust Automation Interface as well (I've never had to use this). However, this can be very simple if you are automating an install process to just uninstall and re-install everything - no need to worry about versioning rules, updating product codes, etc...to very complex if you are going to be running Major/Minor upgrades or even worse, automate patching especially if you are constantly adding or removing files. Things can go array in a hurry if you are missing components in minor updates/patches. ... View more

Try uninstalling and reinstalling InstallShield. I had something similar to this although my installer did not fail, it just didn't include any merge modules, or maybe it was the "NET scan at Build" option where it wasn't including any dependencies, I forget. I have no idea what caused it. I first thought perhaps a windows update but we run all updates once a month and an update had not run on the build server since last successful build. ... View more

Unfortunately, just having the "Enable Logging Support" doesn't actually create the log.  I have not tried to do this myself but, for the MSI's, what happens if you add something like to the Install "MSI Command Line"? /L*v [PATH_TO_WHATEVER]installLog.log Do the logs get created when you run the Suite with "setup.exe /debuglog" A fail-safe option that I tend to do with a custom action is actually set the MSI logging option in the registry: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer] "Logging"="voicewarmupx" This will create an MSI***.log in %TEMP%% ... View more

Interesting. Check your installer log file and search for property "BIN", see if it gets changed during installation.   ... View more