vulgrin
Posts: 40
Joined: Fri Jan 11, 2008 9:49 pm

Repair failures

Hi there, when I try to do a repair of my installed package, windows pops up and asks for the MSI that originally installed the package. It's looking for it in its original location though - not in the C:\Windows\Installer folder.

In my package, I'm zipping the three setup files into an autoextracting / auto-running EXE file. This expands the files to a temp folder, runs the installer, then cleans up after itself. Even if it didn't, I can't imagine that most users would keep the installer around.

Reading through another post here on the board, the installer is supposed to be in the Windows\Installer folder, and it is - but it gets renamed to something like 271b11.msi. When you try to run the repair, it pops up a file open dialog that is looking for the full and proper .MSI filename... not this renamed file.

So - what do I do? How can I reasonably ensure that a customer can repair the software? Or do I need to advise them to redownload the file and rerun the setup, which WILL make a repair possible.

Thanks
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Repair failures

Hi,

When performing a repair Windows Installer may need to use the original installation package. This is because the cached MSI (in the "C:\Windows\Installer" folder) does not contain enough information to repair the installed application.

Since you are using the "Include install files in EXE" option, the MSI and CAB files will be included in the EXE bootstrapper. When the EXE is launched, these files are extracted (usually in the Application Data folder) and the installation starts. After the installation is complete, the MSI and CAB files are deleted automatically. If the user tries to repair this installation, the MSI will not be found in the extract location and Windows Installer will prompt for it.

The solution is to make sure that the extracted MSI and CAB files are not removed when the install process is finished. This can be done by checking the "Do not delete extracted MSI and CAB files" option in the Bootstrapper tab of the Media page. If these files are not removed, the repair process will find them and it will be able to repair the installation.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
vulgrin
Posts: 40
Joined: Fri Jan 11, 2008 9:49 pm

Re: Repair failures

Ah, I'm not using AI to do the packaging of the files. Instead, I'm using WinRAR to make a self extracting EXE.

There was a reason I wasn't having AI do this, but I can't remember now. I think it was because I was trying to get the MSI out so that I could save it for patching purposes later. Maybe I need to revisit the way I have this set up and give it another try.

Thanks as always for your excellent support Cosmin.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Repair failures

Hi,
I was trying to get the MSI out so that I could save it for patching purposes later.
Please note that the Advanced Installer bootstrapper can use the /extract command line parameter. This will make the bootstrapper extract all of its contents (including the MSI) to the specified path.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
vulgrin
Posts: 40
Joined: Fri Jan 11, 2008 9:49 pm

Re: Repair failures

Brilliant - that worked great. Thanks.

Return to “Common Problems”