Combine MSI of a major version and MSP of a patch into 1 MSI - Advanced Installer Community
Zsolt Kollarits
Posts: 409
Joined: Fri May 29, 2015 10:36 am

Combine MSI of a major version and MSP of a patch into 1 MSI

Dear Advanced Installer Support Team,

One of our customers are reported a problem for us, they would like to create a combined MSI file for one of our update packs.

We released a major release as an "MSI resources next to it", therefore the customer has all the files (Prerequisites, CAB file, MSI files) on his side.
Later we released an update pack (Update 1) for the product as a patch, therefore the customer has all the MSP files as well.

Based on the customer's description, he'd like to create a combined MSI file which directly installs Update 1. He's trying to use the following command for creating the combined MSI:

msiexec /a Major.msi /p Update1.msp

Theoretically this line creates a combined MSI file out of the 2 files in the argument list. On my side it's working perfectly fine only if the CAB file belongs to Upadte 1 is copied in the same folder where Major.msi and Update1.msp files are. In this case if I execute the line above, some installation procedure begins and the Major.msi file gets updated (its size is changing as well). The new Major.msi file contains all the changes of Update1.msp too.

That's what our customer would like to achive, but obviously he can't, because he does not have the CAB file belongs to Update 1. On purpose we just release the CAB file belongs to the base product.

Have you ever used such a command before? Could you please try it out on your side? Do you have any idea whether the customer could somehow create a combined MSI file without having Update 1 CAB file?

Thanks in advance for your answers!

Best regards,
Zsolt
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Combine MSI of a major version and MSP of a patch into 1 MSI

Hi Zsolt,

I'm afraid that the user must, indeed, have all the resources (MSI and CAB files) in order to combine the packages with the command line you mentioned. The resources of a package are stored in the related CAB files, so the two packages cannot be combined into a new one without having access to the resources related to one of the packages.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”