Flexera Community

I'm having the same issue with a setup built with InstallShield Premier v12. During a major upgrade, if the path for the existing installation is not used, Error 1001 occurs. Did you ever resolve this?

I get the same error (2705) under the following conditions:Scenario 1 (works without errors)1. Create patch using an existing msi2. Existing msi has ProductCode ABC and PackageCode XYZ3. Installed product has ProductCode ABC and PackageCode XYZScenar...

You could use the Install Exec Sequence to control when the custom action executes. Then, the custom action could check for the existence of the file before running the script.

Is this an InstallScript project? If so, try using SetFileInfo to remove the hidden attribute and then delete the file.

Why not add a conditional statement to Feature_X and set the install level to 0 if the registry value exists (the value for Feature_Y)?