I think MSI's are packages that extracted first, then the Windows Installer service does it's thing. Once the files are extracted, I believe the MSI goes away and the Windows Installer service writes information to the registry about the extracted files which then can tell the Windows Installer service how to rebuild the package in the event something happens. The original source is probably kept on the computer somewhere and you maybe able find it by tracing from the registry. Once you find the source you would have to use Visual Studio or something to rebuild the MSI file. Someone may know more then me about this so there may be other options. For now, I would say search through the registry to find the package information, but from what I have observed once you run an MSI it no longer exists on the physical machine as that archived content. Steps I would take: 1) search through the registry for a key word or a specific file from the application 2) when you find something of interest, note the registry structure. If it is the uninstaller information it should have a unique id that looks something like {0DDE947E-27D5-44A6-83E2-98B7F2B620E7} and it should be in a child directory of "installer," "Microsoft Installer Service," or "Windows Installer Service" (something to that affect). 3) Once you find the unique id search through some folders and see if you can find a folder with that unique id on it and maybe you can track down the source files in there and reconstruct an MSI if the app isn't too complex. Was this installed via gpsi? Jonathan Finkbiner <mailto:jfinkbiner@xxxxxxx> Information Services Support Analyst Lifestyle Family Fitness <http://www.lff.com/> ________________________________ From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Minesh Pandya Sent: Wednesday, March 05, 2008 11:58 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Lost MSI One of our servers has died, one MSI which came from that server was never backed up, and so i dont have a copy of it. The msi is still installed on a machine and I am able to change/repair the application. I have searched for the msi by name and generally *.msi on the machine and cant find it. If the msi can repair itself then it must be stored locally - does anyone know where? ************************************************************************ Barlow Lyde & Gilbert LLP Beaufort House, 15 St. Botolph Street, London EC3A 7NJ. Telephone : +44 (0)20 7247 2277 Fax : +44 (0)20 7643 8500 Web Site : http://www.blg.co.uk VAT Number: 243202705 CONFIDENTIALITY NOTICE This e-mail may contain confidential or privileged information.If you have received this e-mail in error, you must not disclose to any other person, nor take copies of, the contents of this e-mail and/or any attachment to it. We try to ensure that our communications are free of viruses but do not accept responsibility for any loss or damage that viruses may cause. You should take your own steps to ensure that communications are free of viruses. Barlow Lyde & Gilbert LLP is a limited liability partnership, registered in England and Wales with registered number OC325641. Barlow Lyde & Gilbert LLP is regulated by the Solicitors Regulation Authority. The applicable rules can be found on the Authority's website. The term partner is used to refer to a member of Barlow Lyde & Gilbert LLP or an employee or consultant with equivalent standing and qualifications. A list of the members of Barlow Lyde & Gilbert LLP is open to inspection at the registered office, Beaufort House, 15 St Botolph Street, EC3A 7NJ. ************************************************************************