Skip to main content
ronaldl83434680
Participant
February 9, 2018
Answered

MSI Install error 191

  • February 9, 2018
  • 1 reply
  • 610 views

I have downloaded the full CC package and am having some troubles getting it installed by running msiexec /i "adobecc.msi" /q

Whenever it is ran as the MSI I get an error in the logfile of Exit Code 191 when it goes to install the UWPAssets. No matter what I try I still get this error.

However, when I run it just via Setup.exe the entire package installs as it should.

I have looked all over and have not found a solution yet. We are not blocking anything via AppLocker, Not blocking the Windows Store, Firewall is on, just disabled for domain.

I really need to be able to install using the MSI to get good exit codes reporting back to my SCCM environment.

During all my tests, I am running the installs manually, not via SCCM yet.

    This topic has been closed for replies.
    Correct answer alisterblack

    Hi,

    Not everything within a full CC package can be installed via the msi file in the Build folder of your package. In particular it will not install Acrobat as that has its own msi. There are also some 'exceptions' (very few these days). Using the setup.exe installs both the Acrobat and Build msi's.

    To silently install using MSI files, install Acrobat first, then the remaining packages:  

    For example:

    cd Build\Setup\APRO15.0\Adobe Acrobat\

    msiexec /i AcroPro.msi /qn

    cd ..\..\..

    msiexec /i {package name}.msi

    Currently the following applications are present in the Exceptions directory:

    Adobe Help Manager – for downloading offline help content

    Adobe Scout – profiling tool for Adobe Flash games

    Edge Code – lightweight text editor for web developers and designers

    Microsoft .Net Framework 4.5 – Required by Adobe Muse on Windows 7

    Gaming SDK – for developing ActionScript games across multiple devices

    Edge Reflow – design responsive websites

    These applications can be installed with the ExceptionDeployer tool as follows:

    ExceptionDeployer.exe --workflow=install --mode=post

    Note also that some applications (Adobe XD and Dimension) are Windows 10 only and will give an error on Windows 7 - error 191 is one of the errors I would expect to see. Deploying Adobe XD for Enterprise: Issues and Limitations

    1 reply

    alisterblack
    alisterblackCorrect answer
    Inspiring
    February 9, 2018

    Hi,

    Not everything within a full CC package can be installed via the msi file in the Build folder of your package. In particular it will not install Acrobat as that has its own msi. There are also some 'exceptions' (very few these days). Using the setup.exe installs both the Acrobat and Build msi's.

    To silently install using MSI files, install Acrobat first, then the remaining packages:  

    For example:

    cd Build\Setup\APRO15.0\Adobe Acrobat\

    msiexec /i AcroPro.msi /qn

    cd ..\..\..

    msiexec /i {package name}.msi

    Currently the following applications are present in the Exceptions directory:

    Adobe Help Manager – for downloading offline help content

    Adobe Scout – profiling tool for Adobe Flash games

    Edge Code – lightweight text editor for web developers and designers

    Microsoft .Net Framework 4.5 – Required by Adobe Muse on Windows 7

    Gaming SDK – for developing ActionScript games across multiple devices

    Edge Reflow – design responsive websites

    These applications can be installed with the ExceptionDeployer tool as follows:

    ExceptionDeployer.exe --workflow=install --mode=post

    Note also that some applications (Adobe XD and Dimension) are Windows 10 only and will give an error on Windows 7 - error 191 is one of the errors I would expect to see. Deploying Adobe XD for Enterprise: Issues and Limitations