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
FOLLOW US
Get the latest news in Application Packaging