This is a quirk of the Windows Installer. Normally the MSI packages are cached in case they're needed for removal. In this case it looks like the MSI was not cached or was removed from the cache.
If you aren't able to find a copy of this install package, please let me know and I can get it posted on the FTP site temporarily for you to download.
The file will be removed automatically after 72 hours so please download it as soon as you can.
Based on your screenshot, it looks like the installer file was renamed before it was installed (a "64" was added after AvamarClient) so make sure you give the file the name that Windows Installer is expecting.
Feel free to try FabianKessler's suggestion as well. That might be as fast or faster.
Also thanks to FabianKessler's, As i was not the owner of affected machine, i was afraid to use your solution. I felt Lan Anderson's solution was much safer. One again thanks a lot for suggestion.
ionthegeek
2 Intern
•
2049 Posts
2218
0
Posted November 29th, 2013 05:00
This is a quirk of the Windows Installer. Normally the MSI packages are cached in case they're needed for removal. In this case it looks like the MSI was not cached or was removed from the cache.
If you aren't able to find a copy of this install package, please let me know and I can get it posted on the FTP site temporarily for you to download.