Yes, there is another way, even though you may consider it equally complicated Create an admin install of your base version using msiexec qn a ltmsifile. Download location, MSP slipstreaming, link to autopatch tool. There is builtin MSI support for file extraction admin install MSI or Windows Installer has builtin support for this the extraction of files from an MSI file. D_V7xdks4/UHXEaxRhmGI/AAAAAAAABvg/_GSZ18we174/s1600/scomcumulativeupdate5.png' alt='Msiexec Install Patch Msp' title='Msiexec Install Patch Msp' />Well, I believe that the msp file is just a patch, so it only contains the changes that you made using the admin utility. Sorry that this may not be a particularly. Msiexec Install Patch Msp' title='Msiexec Install Patch Msp' />Windows cmd line and msiexec Enterprise Administration Guide. MSI supportAdobe Acrobat and Adobe Reader installers are developed using standard Windows Installer technology. Microsoft Installer MSI commands were not invented by Adobe. Adobe provides this information as a courtesy, but Adobe technical support can not help you craft a command line syntax to fit specific situations and environments. Required MSI versions are as follows For 9. DC products 3. 1. MSI best practicesWhen installing over an existing product, remove the old product first in a separate action. When scripting MSI actions, do not use Remove. Existing. Products after Install. Finalize. Doing so results in the installer updating files before removing the old application, and in the event of application removal failure, the installation may be incomplete. Do not use REINSTALLMODEamus which forces all files to be reinstalled regardless of checksum or version. Such usage could result in a mixture of files from the old and new products. The recommended properties are vomus. Use TARGETDIR on the command line or the AIP user interface to specify an install location other than C when creating an AIP. MSI usageAdobe has tested and supports the installation of Acrobat products using the command line. MSI usage Adobe has tested and supports the installation of Acrobat products using the command line. You can use command line methods to install software in many. You can use command line methods to install software in many ways, such as typing commands at a command prompt, in a batch script. Microsoft Systems Management Server deprecated for 1. Note. When using the bootstrapper, command line parameters can be sent to msiexec from Setup. The syntax for msiexec is as follows Windows Installer command line options are not case sensitive. Msiexec Install Patch Msp' title='Msiexec Install Patch Msp' />Brackets Optional items. Braces Set of choices separated by a from which the user must choose only one. For example blackwhite MSI switchesFor Microsoft documentation, see http msdn. Aa. 36. 79. 88. msiexec command line parametersCommand. Description hDisplays the Windows Installer version and copyright information. Applies the administrative installation option. For product repair. Enables one or more of the command line options below p Reinstalls only if file is missing. Reinstalls if file is missing or if an older version is installed. Reinstalls if file is missing or an equal or older version is installed. Reinstalls if file is missing or a different version is installed. Reinstalls if file is missing or the stored checksum does not match the calculated value. Forces all files to be reinstalled. Rewrite all required user specific registry entries. Rewrites all required computer specific registry entries. Overwrites all existing shortcuts. Runs from source and re caches the local packageg. Identifies the language. Syntax g Language. IDi. Installs or configures a product. Advertises a product. If you want to install the application with elevated privileges, use jm. Syntax msiexec j u m Packagemsiexec u m Package t Transform. Listmsiexec u m Package g Language. IDm Advertises to all users of the computer. Advertises to the current user. LSpecifies the path to the log file. To include the v option in a log file using the wildcard flag, type Lv at the command prompt. The Windows Installer log file options can also be used with the uninstall and repair processes. For example, use L to set verbose logging. Syntax msiexec L iwearucmpvLog. File. txti Logs status messages. Logs nonfatal warnings. Logs all error messages. Logs startup of actions. Logs action specific records. Logs user requests. Logs initial user interface parameters. Logs out of memory. Logs terminal properties. Logs verbose output. To use v, specify L. Appends to existing file. Flushes each line to the log. Purpose Of Program Counter In Microprocessor there. Logs all information except for the v option. This is a wildcard. Applies an update. Sets the user interface level. The modal box is not displayed if the user cancels the installation. Syntax msiexec qn b r f n b b qn Displays no user interface. Displays a basic user interface. Displays a reduced user interface with a modal dialog box displayed at installation end. Displays the full user interface with a modal dialog box displayed at the end. Displays no user interface, except for a modal dialog box displayed at the end. Displays a basic user interface with a modal dialog box displayed at the end. Displays a basic user interface with no modal dialog boxes. Indicates the user interaction level for this installation. Applies transform to advertised package. Syntax t Transform. Listx. Uninstalls a product. Calls the system API Dll. Register. Server to self register modules passed on the command line. Calls the system API Dll. Un. Register. Server to unregister modules passed on the command line. Package Code. Specifies the globally unique identifier of the Windows Installer package. For Acrobat products, this is the GUID. Package. Not supported. Specifies the name of the Windows Installer package file. MSI propertiesYou can also use Windows Installer functions to set properties on the command line. For example, you can set a company name or suppress rebooting. MSI properties defined by the Microsoft Windows Installer, but you should refer to Microsoft documentation at http msdn. VS. 8. 5. aspx for a complete and current list. Unsupported MSI properties. The following properties are unsupported SHORTFILENAMES is no longer supported. Microsoft has removed this property from the Windows 7 Logo Requirements. ALLUSERS is not working properly in version 9. MSI installer propertiesProperty. Description. ADDLOCALA list of comma delimited features to install locally. The features must be present in the Feature column of the Feature Table. To install all features locally, use ADDLOCALALL on the command line rather than the Property Table to avoid creating an installed package that cannot be correctly removed. ALLUSERSDetermines where configuration information is stored. It is a per machine setting and is set to 1 by default for both Acrobat and Reader. COMPANYNAMEThe name of the company installing the product. INSTALLDIRSpecifies a non default installation directory. INSTALLLEVELThe property specifies an installation level threshold. A feature is installed only if the value in the Level field of the Feature table is less than or equal to the current INSTALLLEVEL value. REBOOTForce or suppress rebooting. REINSTALLList of features to reinstall. Setting this property results in a required reboot for 9. For 1. 0. x products, let the MSI engine decide what to reinstall doing so should result in fewer reboots. REINSTALLMODEA string containing letters that specify the type of reinstallation to perform. Use of the vomus switches is the recommended configuration. REMOVEList of features to be removed. You can pass either Reader. Browser. Integration or Acrobat. Browser. Integration to REMOVE when a product is already deployed and a subsequent deployment requires disabling browser integration. TARGETDIRSpecifies the root destination directory for the installation. TARGETDIR must be the name of one root in the Directory table. There may be only a single root destination directory. During an administrative installation this property specifies the location to copy the installation package. Do not create an AIP at the root directory. Use the AIP UI or this property on the command line to install from a directory other than C, D, etc.