Why is it when I double click a MSP file it works fine but if I use MSIEXEC to install it I get a "this pactch package could not be opened" error. What am I doing wrong?

I have an MSP file that if you double click on it and follow the prompts it runs great.  but if I try and install it via Command line I get the "package could not be opened error"  I have tried using msiexec /p and misexec /update to no avail.

2 Comments   [ + ] Show comments
  • What was the complete command line you tried using? Add a verbose log file so you can review the information. - vjaneczko 2 years ago
  • Sorry for the delayed response, I was out of town. Here is the command I am running: msiexec /p BbRevu2018x64_Update2.msp REINSTALLMODE=omus REINSTALL=ALL BB_SERIALNUMBER=XXX BB_PRODUCTKEY=XXX BB_EDITION=2 /qn

    Again if I run this it fails on the same computer that works if I just double click. I noticed that worzie mentioned having the full path to the MSP file. I didn't think I needed it but I didn't try it either. My goal is for this to be deployed via SCCM so full path is not really an option if I still want SCCM to deploy this. - acpowell 2 years ago

Answers (1)

Posted by: worzie 2 years ago
Third Degree Brown Belt
msiexec /p <full path to msp required> or with package installation: msiexec /i msi patch=<full path to msp> (could try with /a for administrative as well; I've never had to).

Most patches have requirements too, such that a certain version needs to already exist.  So be sure to run the msp like you mentioned on a target PC where the cmd line is failing to verify that.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ