Hello and welcome to our forums,

Unfortunately this error is a generic one and it can have multiple causes. Here are some scenarios when this error can occur:

1. during a patch installation. To avoid this error during a patch install you can build EXE setup packages and enable the "Do not delete extracted MSI and CAB files" option from "Builds" page -> "Configuration" tab.
2. during an upgrade installation if you are building EXE setup packages and use the same extraction path for all versions of your setup. In this case you should make sure that each version of your EXE setup has a different extract location; just go to "Builds" page -> "Configuration" tab and set in the "Extract location" field a path including the "ProductVersion" property reference, for instance: 3. when the setup package is built with a specific language code page (of the project language) and the installation runs on a system with a different language including unknown characters for the setup language; for instance if the setup files extraction path includes a character which doesn't belong to the current setup language codepage, the the WIndows Installer service won't succeed to process the related path, thus the above error will be thrown; to avoid this situation you can go to "Builds" page -> "Configuration" tab and under the "Database Encoding" section select the "UTF-8" encoding type
4. when on current machine there is an Antivirus program which blocks the installation process; there are situations when an antivirus program falsely detect the installation process as a malware and blocks it; in this cases you can ask your customer to add an exception for your setup package in the Antivirus exception list or to temporarily disable the antivirus during the setup installation
5. when you are using an EXE package type and the installation files were not extracted before the installation reaches file copy action; check the "Installer stuck on "Extracting files from archive"" topic for more details and a workaround

If you have further questions let us know.

All the best,
Daniel

Hello Charles,

Yes, we received your email.

After analyzing your sent files it seems there is a problem with the installation files extraction at install time. A possible solution is to set the setup to extract the installation files from the setup whet it is launched. This can be achieved by going in "Install Parameters" page and set the "ExtractFilesFirst" property to value 1 like this:

• Name: ExtractFilesFirst
  Value: 1

By default, our EXE bootstrapper extracts the embedded installation files asynchronous. When you run the setup the files are extracted at the same time you are going through the installation process. If the installation reaches the file copy action and the files aren't yet extracted you may encounter this issue.

More details are found in "Installer stuck on "Extracting files from archive"" topic.

Let us know if this helped.

All the best,
Daniel

Hello Charles,

The above error is not related with the workaround I suggested you. This is an UI error. This kind of error is thrown by the installer UI when an UI control is not correctly rendered on the current machine. Unfortunately we cannot investigate them because almost every time this is a sporadic error and on a second setup launch the error cannot be replicated at all. Usually on a subsequent try everything works as expected.

We've just add a major improvement in our setup UI feature and starting with the next version (14.0) of Advanced Installer we hope this kind of UI errors will never occur.

All the best,
Daniel

You're welcome.

All the best,
Daniel

I am facing the below issue while installing UFT 14.5. Please help me to solve the problem.

Hello and welcome to Advanced Installer forums,

Have you tried the workaround that my colleague Daniel has suggested above?

The workaround would be to go to "Install Parameters" page and add the following property to your project:

Name: ExtractFilesFirst
Value: 1

Hope this helps.

However, If that does not help, please forward me the following by e-mail at support at advancedinstaller dot com:

- a copy of your .AIP file used to build the setup
- a download link for the setup that reproduces this behavior

All the best,
Catalin

Hello. I'm migrating an older installer project that has this issue for a few customers. This is an old thread and refers to "Install Parameter", of which there is no way to add this. Do you mean "Properties" like below?

Hello,

Yes, the properties now have a dedicated "Properties" page on the left menu.

Let us know if you have any questions.

Best regards,
Liviu