InstallAware

I have encountered a problem that I have been able to narrow down. Unfortunately, this is affecting the installation of our product.

We have to install C++ 11.0 runtimes (minimum and additional) for our product. This works fine. However, because of uninstall issues we were having, I checked the box to Always Cache Setup Sources. Checking this box causes the following failure when installing:



I was able to produce this issue with a minimal test project, which I have attached. Basically, create a new .NET setup, remove the installation of .NET 4 (client and full are selected by default) and select Microsoft Visual C++ Minimal Runtime 11.0 and Additional Runtime 11.0. Check the box that says Always Cache Setup Sources and build. This problem happens whether I build a single file or for CD/DVD. Either way, I get the above message when I install.

I hope to get this problem solved. We need to be able to install the runtimes, and we can't expect our customers to have access to the original setup file for uninstall purposes.

Thanks!

JAB

Dear JAB,

I just tried your project and the resulting un-compressed build works fine when executed on my test machine.

did you try to install the package over a different machine?

I may suggest you to verify if any security policy or Anti-Virus application is causing your issue.

Regards

Francesco,

Actually, I tried this on two different machines with the same result. They are both Windows 7 machines, one 64-bit and one 32-bit. Both are fresh installs of the OS. I was doing this to test the installation of the runtimes. My procedure was to format the partition, install the OS, then install the product.

To my knowledge, there was no anti-virus installed on either machine.

What I don't understand is why the product installs fine on both machines if the box is filled, but not if it is checked.

JAB

Dear Jab,

are you using the same project you sent me?

What I don't understand is why the product installs fine on both machines if the box is filled, but not if it is checked.

I suppose because the process tries to store that file locally for later use (Cache Setup Sources files) ... and this operation is skipped when setup files are not cached.

Regards

Francesco,

Yes, the project I sent you exhibits the behavior I described on both machines. And just to be sure, I filled the "Always Cache" checkbox and ran it again on both machines and the install worked fine.

I assume you tested the project I supplied on a machine that needs the runtimes installed. This is the only case that fails. In other words, the install works just fine as long as the runtimes don't need to be installed.

JAB