Patch and self repair
Hi all,
Here is my problem:
- I create a msi package (APP-1.0-R2.MSI) and a patch file (MSP) for an application already deployed (APP-1.0-R1.MSI)
- I have the new package (APP-1.0-R2.MSI) in a new folder (same name)
- I apply the MSP from this new folder and everything seems ok, the files and registry keys are correctly updated BUT... when I try the self-repair function in ARP, the Windows Installer search for the CAB file whithin the R1 folder.
Any idea ?
Thanks !
---
kEEp cOOl...
Here is my problem:
- I create a msi package (APP-1.0-R2.MSI) and a patch file (MSP) for an application already deployed (APP-1.0-R1.MSI)
- I have the new package (APP-1.0-R2.MSI) in a new folder (same name)
- I apply the MSP from this new folder and everything seems ok, the files and registry keys are correctly updated BUT... when I try the self-repair function in ARP, the Windows Installer search for the CAB file whithin the R1 folder.
Any idea ?
Thanks !
---
kEEp cOOl...
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
WiseUser
19 years ago
Windows Installer maintains separate records for the source locations of the original MSI and any patches that are applied (under "HKCR\Installer\").
You might have your original MSI in one folder, patch "A" in another folder, and patch "B" in yet another.
You might have your original MSI in one folder, patch "A" in another folder, and patch "B" in yet another.
Posted by:
s2w2k2
19 years ago
When you try to do self-repair, the msi will search for the source for the already deployed MSI. Since the source files for the MSI is within the R1 folder, the Windows Installer will search for the CAB file whithin the R1 folder. Your best solution is to move your msp within the folder of the msi which is already deployed
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.