Please also refer to the sections pertaining to specific deployment methods.

Issues and errors¶

Download Adobe Acrobat XI Pro is a very efficient application that gives you the possibility to create and edit PDF documents that include rich media and share them securely.Adobe Acrobat XI Pro is featuring a streamlined workflow, helps you protect your data, allows you to keep track of your forms and is able to include multiple multiple. Free acropro.msi 7.0下载 download software at UpdateStar - A software utility which is used to convert postscript print files to the adobe acrobat.pdf file format. 1,746,000 recognized programs - 5,228,000 known versions - Software News. I have ERROR Missing Acropro.msi file when install adobe. Any suggestions? Best Answer 100% (1 rating) Previous question Next question. 'installation package AcroPro.msi' where can i get that file to install adobe acrobat x pro 10 gema54321. Download and installation help for Adobe links. Acronis disk director download, Acid glitch original mix download. Tested virus free, Professional customer service support, Rhode Island For your own protection ALWAYS check downloaded files for., Adam levine mp3 download, Across the universe ita download.

General problems, FAQs¶

System errors or freezes for DC products

Perform the following steps if Acrobat Reader DC crashes:

1. If there are any third party plugins present, disable them.

2. Turn off AppContainer:

   1. Quit Acrobat Reader DC.

   2. Open the registry editor.

   3. Disable bEnableProtectedModeAppContainer:

I want either Acrobat Pro or Standard, how come I only see a single installer?

Acrobat Professional and Standard DC are delivered as a single installer. Product behavior and features become enabled based on the entitlements granted by the licensing methodology (a user ID or serial number).

Where can I get Acrobat installers?

If you no longer have the installation media of Acrobat DC, Acrobat XI, or Acrobat X, you can download replacement installers from the Licensing Web Site (LWS). If you don’t have access, get recent and legacy versions from the Download Page.

Can I downgrade my product or install an older Acrobat version?

Yes. In enterprise environments that require a legacy product version, contact Support for details about buying a current volume license for discontinued products.

How do I save an Outlook email as a single PDF or PDF portfolio?

By default, saving an email creates a PDF portfolio. This is true whether you choose Adobe PDF > Selected Messages, or right click on an email and choose to Convert to Adobe PDF. You can change this behavior by doing the following:

1. Open Outlook.

2. Go to the Adobe PDF tab.

3. Choose Change PDF Conversion Settings.

4. Go to the Settings tab.

5. Uncheck Output Adobe PDF portfolio when creating a new PDF file.

As an alternative, configure the registry or plist entry that that controls whether PDFMaker creates a portfolio:

1. Go to HKEY_CURRENT_USERSoftwareAdobeAcrobatPDFMakerDCOutlookSettings.

2. Create the new DWord entry OutputPC if it does not exist.

3. Set the value to 0 to create a PDF. Set the value to 1 to create a portfolio.

Can I deploy Adobe Reader via Intune?

Because Microsoft deprecated support for MSP, EXE, and CAB file types with Azure Intune, Adobe does not plan on supporting Intune-based desktop deployments. However, some enterprise admins have reported success with various workarounds for Adobe Reader. For example, see this forum post. Acrobat cannot be deployed via Intune.

Why do I get a Setup.ini not found error?

If you get a Setup.ini not found error, create an empty setup.ini file in the AIP’s root. If you are using the Wizard, make sure you’ve extracted the EXE prior to starting any configuration.

Why am I not getting the right language in the installed product, the logs, or some other feature?

When you are using a transform file, select the language as follows:

What are some common Windows cmd line syntax errors?

• All mst files should be separated by semicolon (;).

• The entire mst string along with separators must be enclosed in ” “.

For example:

• Correct: '<mst1>;<mst2>'

• Incorrect: '<mst1>';'<mst2>'

Why am I getting a “Cannot use this product under a guest account” error?

Acrobat with a volume license will not run for users under a guest account. This error will appear if a local user account is in an administrator group as well as a guest group. Removing the user account from guest group usually resolves this issue. Verify any group policies applied to the user’s profile are not in the “guest” category.

Why does my patch or update result in the product being reverted to an earlier version?

All browsers must be closed. If they are not, it is possible that the updates will fail and the application version will be reverted to an earlier one. For more information, see this thread: https://forums.adobe.com/message/2902858#2902858.

Why does my install fail with a fatal error?

If the application event log generates errors similar to those below every time the PC is started and the installation is started over, verify the license key is correct.

Why doesn’t my install respect the “silent install” settings I specified with the Wizard?

If your command line is something like:

… then you are not using Setup.ini your workflow. The Wizard rewrites Setup.ini when you specify a silent install to include this option. The silent install switch is not saved in the MST. Either run Setup.ini or change your command line to:

Error 16 appears during GPO deployments

This error occurs because one of the product’s subdirectories under Program Files does not have the correct group permissions. To fix the problem, modify your GPO policy so that the Everyone group has write permissions on the “Adobe PCDcache” folder.

I modified the installer tables directly, and now my install fails. Why?

Using the Wizard’s Direct Editor does not modify the original MSI. The Wizard operates on temporary copy which is later used to create MST.

Why do I see a “The upgrade cannot be installed by the windows installer service” error?

Error: “The upgrade cannot be installed by the windows installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.”

If you see this error in the log file, you may be updating the product in an unsupported order. For example, 10.x installers are cumulative. You cannot install 10.1.1 over 10.1. 10.1.1 should be installed over 10.0.

Setup has detected that you already have a more functional product installed. Setup will now terminate.

This error appears for various reasons:

• A lesser product is being installed over a more functional product; e.g. Acrobat Standard over Acrobat Pro or 10.1.1 over 10.1.2.

• An AIP deployment is attempting to use an unsupported install order.

• The uninstall of previous versions and products you did in order to avoid this issue was not clean. In this case, try Microsoft’s cleanup tool or Acrobat’s tool on LABs.

Error: Cannot use this product under a guest account

Guest accounts are not officially supported either by Acrobat or CS products, though workarounds have been reported in the forums.

Why do I get a serial number-LANG_LIST error?

When language values which the serial number does not support are provided as arguments to LANG_LIST, this error appears: “LANG_LIST contains values which does not match the serial number.”

Why do I get a Visual C++ 2010 SP1 (x64) runtime error during install?

Visual C++ 2010 SP1 (x64) is required on 64-bit machines during Acrobat installs unless you use IGNOREVC10RT on the command line.

Why do I see Error: 213:11 during install or first launch?

First launch requires write access to a temp file in C:ProgramDataAdobeSLStore. For more information, see the Acrobat help.

Why does my 10.1.5 and later install invoke the UAC dialog?

This is not a common scenario in enterprise settings since admins typically disable UAC or deploy via methods that provide elevated privileges. 10.1.5 and later requires such methods. When UAC is not disabled, the dialog will always appear on Windows 7/Vista machines.

Why does my new Acrobat installation on WTS result in a crash?

Some users have experienced issues where Sophos Anti Virus software conflicts with Acrobat’s licensing components (e.g. PDApp.exe). If you are experiencing problems, try uninstalling Sophos.

What is the error “EmiOrientation: Verified that it is NOT a volume binary?”

The installer is expecting a volume installer but thinks you are using a retail installer. Possible reasons include:

• You are using the wrong installer and may be entering a volume serial key in a retail binary. 9.x products have separate installers for Retail and Volume.

• A volume serial number requires that it be used with a volume installer with its signature intact. For example, if you change the installer tables in the MSI via Orca, Admin Studio, or some other tool, the installer logic will mark that MSI as RETAIL build instead of volume build. It is unlikely (but possible) that the MSI’s digital signature was lost for some reason or that CryptQueryObject failed because the Crypto library on the system is missing or not functioning.

• Verify you are updating in the required order. If using an AIP, throw away your old AIP and start over since you cannot slipstream updates in most cases. For 9.x products, slipstreaming the patches into a volume license version changes it into a retail copy and the volume license is no longer valid. See https://forums.adobe.com/message/2602438#2602438 for other reports of the same issue.

Why do I get the error “Offline grant exception process failed.”?

For DC products, this error will appear if you are not using the correct serial number for your track. Continuous track serial numbers do not work with classic installers.

Anti-virus programs - error 1321

Some users have reported conflicts with security software (such as McAfee’s on-access scan v.8.8) where installation fails with error 1321. If you experience this error, try testing the install with your security software disabled.

Flash is unsupported

Acrobat DC products no longer use Flash in any part of the product.

10.x and 11.x products only use a special, secure version of the Flash player to display certain parts of its user interface. To display SWF content in PDFs, Acrobat relies on the user’s system player. For organizations that need to allow such content, admins should deploy the latest and most secure version of the Flash player. For details, see this Help content.

iFilter and PDF indexing

Adobe’s iFilter has been end-of-lifed as Microsoft provides alternative ways to index PDF. While iFilter does work with DC products, keep in mind bugs are no longer fixed and there may be non-functional scenarios. For details, see the Legacy Admin Guide.

MSI errors (Windows)¶

Error 1327 - Invalid Drive [drive letter here]

See the Acrobat Help

It might also be worthwhile to check these registry values:

• HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders

• HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders

Errors 1402 and 1406

• See https://helpx.adobe.com/acrobat/kb/error-1402-error-1406-acrobat.html.

• In some cases, it may be necessary to download a Security Update for Windows 7 for x64-based Systems (KB3072630) from Official Microsoft Download Center.

Error 1603 and installation or upgrade failures

1603 is an MSI error code that can be thrown as the result of a file conflict or permissions issue. This error also may appear if a previous uninstall was incomplete. If you see this error, try:

• The suggestions on the Microsoft support site.

• Using IGNOREAAM=1 in a command line installation.

• Using the Cleaner tool to completely remove Acrobat, and then reinstall.

Error 1730, Broken-missing icons, and other issues appear after a GPO deployment

If you are attempting a per-user install, change the install to per-machine. Per-user installs are not supported.

Error 1935. An error occurred during the installation of assembly

See the Acrobat Help

Error 2203: Database: C:<productName>.msi cannot open Database file

AIPs should not be created on the drive root. Use TARGETDIR on the command line or the UI to specify another location.

Sharepoint¶

Why can’t I check out a file directly from SharePoint but can when I open a document library with IE?

Microsoft has confirmed a bug in the March 2013 update. There are other workarounds. To track this issue, see https://forums.adobe.com/message/6106294#6106294.

Installation FAQs¶

For FAQs about a particular deployment method, refer to the documentation for that method.

Why does my installation of one product over another fail with a file- related error?

When installing a product of one type over another type, always uninstall the other product first. For example, when installing Acrobat Pro Extended on machines where Acrobat Standard is already installed, it is a best practice to uninstall the existing product first. You should not rely on MSI parameters such as REINSTALLMODE=amus (where “a” forces all files to be reinstalled), as this may result in a mixture of product files on the target machines.

Why am I getting a license prompt when Acrobat is installed from a licensed image?

Admins who configure machines that have been purchased from vendors with Acrobat preinstalled may not be able to use a single image across multiple machines. This is true when vendors provide machines with unique retail activation serial numbers rather than a single volume licensing serial number

For example, in the past the Dell factory preinstalled Acrobat Standard with a volume licensing serial number. Dell is now providing Acrobat XI Standard via their cloud distribution method (Dell Digital Delivery) retail activation serial numbers. These machines cannot be used to create an image that can be used on other machines.

For related information, see https://forums.adobe.com/message/5460079.

How can I find the PRTK tool?

If you have the Adobe Customization Wizard DC installed on your machine, go to C:ProgramFiles(x86)AdobeAcrobatCustomizationWizardDC.

Can I mix and match installs with serial numbers and named users?

Yes. On both Macintosh and Windows.

Where can I get legacy product installers for Acrobat?

See https://helpx.adobe.com/acrobat/kb/acrobat-downloads.html

Conflicting processes¶

DC products offer a fully automatic update mode. This mode is enabled by default for both Acrobat and Reader on both tracks and usually delivers a “silent” install experience. To avoid reboots and requests to close certain applications, the updater tries to detect which files and waits for their release. In some cases, installs and uninstalls may require closing conflicting processes to avoid “files in use” errors. Conflicting processes are partially governed by the installer tables AppsInUse (Acrobat) and AppsinUseEx (Reader). However, there is internal logic, so a review of the tables does not yield a complete list of items that must be closed in silent and manual workflows.

It is generally a good idea to close potentially conflicting processes. As a best practice, close everything. Note the following:

• Uninstalls require closing Acrobat and Reader.

• While you can install a patch in /qn (silent) mode without closing the application, users will be required to reboot.

• The Windows Installer may also invoke a Files In Use dialog when the installer tries to replace or uninstall certain modules.

• Acrobat (Acrobat.dll) and Reader (Acrord32.dll) load on product launch, when a browser is using the product plugin to display a PDF, or it is used for thumbnails, property sheets, and the preview handler.

• A first time installation should not require closing anything.

• An uninstall may invoke a Files In Use dialog with Ignore and Don’t Ignore options depending on the open files/processes. If the install should be silent, plan accordingly.

Miscellaneous¶

How do I stop the 11.x “End of Life” messages from appearing on application startup?

Set bShowMsgAtLaunch to 0 and thereby disable in-product messaging. For details, see the Preference Reference.

I deployed a DC product in my enterprise, and end users are still be asked to sign in. Why?

When a DC product is licensed correctly, end users should not need to sign in. There are several ways to license/activate Acrobat:

• Use the Wizard to grant an offline activation exception and disable registration.

• For imaged deployments, use APTEE.

• Follow the supported licensing methods.

• When Acrobat DC is deployed with the Creative Cloud Packager (CCP), use the SUITEMODE=1 property during deployment. This is only needed for CCP deployments.

How do I identify Acrobat Standard and Pro DC installs?

Refer to the documentation here.

Note that for DC products, Pro and Standard are delivered as a single installer, so using both the SWID tag and LEID together is required to properly ID what’s installed.

After a fresh Acrobat 11 install, why does double clicking a PDF not result in the PDF opening?

Even when registration is suppressed and the EULA has been accepted, Acrobat needs to be open at least once before double clicking a PDF will directly open that PDF in Acrobat.

Why do I see two processes running?

• When protected mode or protected view are enabled, two AcroRd32.exe processes will run on the machine (one broker process and one sandbox process). This is a normal aspect of those security features.

• The Acrobat (or Reader) CEF process is a helper application for rendering HTML-based services views. Acrobat and Reader use CEF(Chromium Embedded framework) for rendering the HTML views. Like Chrome, all CEF-based applications are multiprocess, with one main process and a separate renderer process for each HTML view. Therefore, there might be more than two AcroCEF.exe depending on how many HTML views are visible.

Using the AcroCleaner on Windows¶

The Adobe Reader and Acrobat Cleaner Tool removes a standalone installation of Reader or Acrobat, including any preferences and settings that may be preserved during a standard program uninstall.

While most installs, uninstalls, and updates operations happen without incident, there are cases where a user may not be able to complete such tasks due to some registry or file conflict on the machine. This is particularly problematic when permissions set on plist entries or files prevent the successful installation of new installs and/or updates. The Adobe Reader and Acrobat Cleaner Tool is designed to fix such issues by cleaning up corrupted installations, including removing or fixing corrupted files, removing or changing permissions registry entries, etc. The tool provides options for removing problematic Acrobat items only while leaving Reader untouched and vice versa.

Note the following:

• The tool cannot be used with any Creative Cloud products or Acrobat delivered with CS products. It can only be used for standalone versions of Acrobat and Reader.

• The Windows version of the tool only supports cleanup of DC products (both Continuous and Classic tracks). If you want to remove any older versions of Acrobat and Reader products then please refer to “AcroCleaner for 10.x and later”.

• In some scenarios Cleaner tool for Windows might affect some preferences common between Acrobat and Reader. Hence it is advised that if both Acrobat and Reader products are installed on machine then the installed product be repaired after running the cleaner Tool.

User interface usage¶

1. Double click the AdbeArCleaner.exe file.

2. Verify you want to continue, and choose Next.

3. Accept the EULA and choose Next.

4. Choose the standalone product to clean and choose Next.

   • If the product to be cleaned is installed on the machine, tool directly proceeds to cleanup.

   • If the product is not found, then Acrobat/Reader is cleaned from the default installation location at ProgramFilesFolderAdobeAcrobat*.* folder. The user is also given an option to select and add any other additional installation.

5. If more than one product is detected, choose which product to remove and whether or not to remove any files that may be shared between Adobe Reader and Acrobat.

6. Choose Clean Now. Cleanup begins.

7. When finished, restart the machine.

Command line usage¶

1. Open a command prompt.

2. Run the tool with the command line parameters as shown below.

3. When finished, restart the machine.

Properties

• ProductId: Identifies the product:

  • 0 = Acrobat (Default)

  • 1 = Reader

• InstallPath: Specifies the product installation path. Default = the product’s default location; e.g. C:Program Files (x86)AdobeReader (version). You must use this parameter when using ScanForOthers = 0.

• CleanLevel: Specifies the level of cleanup; i.e. shared components should be cleaned or not:

  • 0 (Default) = clean only components for the selected product.

  • 1 = clean components for the selected product as well as shared components.

• ScanForOthers: Specifies whether to search for and delete only the installation directory identified by InstallPath or all directories on the machine:

  • 0 = Search for and delete only directories found on the path specified by the InstallPath parameter.

  • 1 (Default) = Search for and delete installation directories system wide. This search includes non-default paths as well as default paths such as C:Program FilesAdobeAcrobat 10.0.

• /?: Invokes the tool’s Help; for example: AdbeArCleaner.exe/?

Troubleshooting¶

Acrobat Process Monitor¶

The AcroMonitor Tool on LABs helps you troubleshoot problems such as crashes, error dialogs, and non-working features that occur when Acrobat and Reader is running. It collects information about running processes, your system environment, and other log details, and allows you to collect:

• Process dump

• Process monitor Log

• Registry dump

• List of installed applications

Once the data is automatically collected and stored on your computer, you can examine it yourself or send it to someone for further analysis.

Generating a crash dump file¶

If you are experiencing application crashes, it may be useful to create a dump file. To do so:

1. Install WinDbg from https://www.microsoft.com/whdc/devtools/debugging/installx86.mspx.

2. Launch WinDbg via the shortcut.

3. Choose File > Open Executable.

4. Select the program exe. For example, choose Acrobat.exe from C:ProgramFilesAdobeAcrobat10.0AcrobatAcrobat.exe.

5. Choose OK.

6. Press g and Enter when you encounter the first breakpoint. You should see the text Debugger is running, and the application should launch.

7. Open the file that produces the crash.

8. After you successfully reproduce the crash scenario, enter the following in the WinDbg terminal: .dump/mac:temp.dmp.

9. Choose Enter.

These steps produce the crash dump at C:temp.dmp. Use this file for troubleshooting or provide it to your support contact. Support may also need the PDF file that cause the crash.

Collecting logs; script¶

The following sample should be modified to suit your environment.

Note the following for Windows:

• Irrespective of the current drive, the batch file saves the file in where the batch file is located.

• Winzip needs to be installed at the default path (i.e Program Files).

Updater and installer logging¶

If you’re having trouble with the updater, enable Adobe Reader Updater (ARM) and Windows Installer verbose logging:

1. Verify no AdobeARM.exe instance is running.

2. Verify the product is not running.

3. Enable The Adobe Updater (ARM) verbose logging:

   • 64-bit: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeAdobeAdobeARM1.0ARM[iLogLevel=1] (DWORD)

   • 32-bit: HKEY_LOCAL_MACHINESOFTWAREAdobeAdobeARM1.0ARM[iLogLevel=1] (DWORD)

4. Enable Windows Installer verbose logging. See https://support.microsoft.com/en-us/help/223300/how-to-enable-windows-installer-logging

5. Open C:ProgramFiles(x86)CommonFilesAdobeARM1.0 (on 64bit OS), and launch AdobeARM.exe.

6. Wait for the full update to finish (can take up to 15 minutes). AdobeARM.exe process running in the Task Manager finishes (if needed, enable viewing all processes)

7. View the AdobeARM.log file and the Windows Installer log in in the User Temp folder.

Note

ARM and MSI logs also appear in WindowsTemp when ARM performs the update in the LocalSystem context

List of log files¶

Contacting support¶

If you need to contact Adobe Technical Support, please prepare answers to the following questions:

• Server software:

  • Management tool software version (e.g. Citrix, SMS, WTS, etc):

  • Operating system:

  • Service Packs:

  • Are the system requirements met?

• Client software:

  • Operating system:

  • Service Packs:

  • Adobe product

  • Are the system requirements met?

• Problem details:

  • Type of problem:

  • Error message (if any):

  • Logged on as administrator or user?

  • Problem persists as administrator?

  • Can you reproduce the problem when you test the problem on the server?

Deployment details

If you are having deployment problems, also record the following:

• Base version

• Any patching/chaining?

• Using MSI or EXE?

• Using the Customization Wizard?

• Deployment method (AIP, GPO, SCCM, ARD?)

• Installing over other products?

• Did you attempt to install any third-party scripts or application programming interfaces (APIs) with Acrobat during deployment? If so, does the problem reside with these elements? (To find out, create a test package containing only Acrobat.)

• How did you create the package?

• Does the problem occur when you install the application from a DVD? If so, does the problem occur when you copy the contents of the DVD to a local or network drive?

MSI support¶

Adobe Acrobat and Adobe Reader installers are developed using standard Windows Installer technology and Microsoft Installer (MSI) commands were developed by Microsoft.

The required MSI version for DC is 3.1 or higher.

MSI best practices¶

• When installing over an existing product, remove the old product first in a separate action.

• When scripting MSI actions, do not use RemoveExistingProducts after InstallFinalize. 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 REINSTALLMODE=amus 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 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 ways, such as typing commands at a command prompt or in a batch script. When using the bootstrapper, command line parameters can be sent to msiexec from within the Setup.ini as well as on the cmd line.

The syntax for msiexec is as follows:

• Windows Installer command-line options are not case-sensitive.

• Brackets ([]): Optional items

• Braces ({}); Set of choices separated by a | from which the user must choose only one. For example: {black|white}:

MSI switches¶

For Microsoft documentation, see https://msdn.microsoft.com/en-us/library/Aa367988.

MSI properties¶

You can specify MSI properties at install time; for example, to set a company name or suppress rebooting. For a complete list, refer to Microsoft documentation.

Supported MSI properties¶

Unsupported MSI properties¶

• SHORTFILENAMES is no longer supported. Microsoft has removed this property from the Windows 7 Logo Requirements.

Troubleshooting msiexec¶

When using msiexec, if you receive an “Incorrect command line parameters” error message, verify that:

• Your syntax is correct.

• There is a space before the log file name if you use the syntax for writing a log file.

• You have not placed a /qn switch between the /i switch and the name of the MSI file.

Note

For more information about msiexec options, refer to https://technet.microsoft.com/en-us/library/cc759262(WS.10).aspx#BKMK_Install.

Bootstrapper installation¶

The bootstrapper Setup.exe file uses setup.ini as its configuration file. As you customize the installer with the Wizard, the Setup.ini file automatically updates. The Setup.exe file uses Setup.ini as it’s configuration file. Before deployment, open Setup.ini, verify it contains all the properties you need, and edit it as neccessary.

Setup.ini contains two sections:

• [Startup]: Setup.exe first executes the Adobe flags for CmdLine. Do not place Adobe properties or MSI switches here; for example, you can use /sAll but not /qb!+ in this section.

• [Product] Setup.exe then reads the [Product] section. There may be multiple [Product] sections depending what the EXE should invoke (other MSI’s or EXE’s). The CmdLine should only contain values supported by the item the EXE invokes. For example, when invoking an MSI (msi=AcroPro.msi), you can only use space-separated Adobe properties (flag/value pairs connected by an = sign) and MSI switches; for example, you can use /qb!+ but not /sAll in this section.

MST usage in Setup.ini

Command line examples¶

These examples demonstrate different ways to install Acrobat products using the command line. Keep in mind the following:

• The examples use specific products and versions. Modify the command line to suit your environment, changing paths and file names as appropriate.

• It is possible to apply patches during an initial installation.

• For multilingual installers, use the selected language transform in the command line (for example, 1036.mst for the French language).

• Transforms in the installer media directory do not require fully qualified paths in the command.

• Patches do require fully qualified paths.

Note

As of July 2010, Reader update installers on the Reader Download Center for Tier 1 are chained by default. If you are downloading the product from the RDC rather than the download site, just download the latest file and you’ll get all patches in one file.

Listing installed updates¶

Occasionally, certain bugs or features may be impacted by a specific OS version. You can use a Windows utility to list installed Windows udpates.

After installing the utility, run the following:

Adobe Acrobat Pro Dc Msi

Installing Acrobat 2019 with logging¶

The silent install below creates an install log. Note that IGNOREVCRT64 can only be used when the C++ x64 Runtime is not required.

Language selection¶

You can use the LANG_LIST property to specify languages. Specify both the language code and the language-specific MST:

For details, see Adobe Properties

Creating an AIP¶

To create an administrative installation for a customized installer, use /a and TRANSFORMS. For example, the following installs Acrobat Pro with an MST file created with the Customization Wizard:

To create an administrative installation for a major release installer and a patch, use /a and /p. For example, the following installs Acrobat Pro 10.0 with the 10.1.0 patch:

Note

It’s always a good idea to keep the files in the same directory and cd to that directory so that you can run the commands from there.

TRANSFORMS and .mst¶

Installer modifications created in the Customization Wizard are saved to an MST file. The MST must be referenced in the .ini file or on the command line. This example installs a customized version of Acrobat Professional, displays a basic user interface, and enables verbose logging.

Installing with an MST

LEIDs and post-install prtk usage¶

Once an ETLA serial is provided, the LEID changes for unserialized commands. For both tracks, it becomes V7{}AcrobatETLA-12-Win-GM (on Windows) and V7{}AcrobatETLA-12-Mac-GM (on Macintosh). For example, you would use the “ESR” LEID version to initially serialize, and you would use the “ETLA” version to deactivate or perform any other action with the prtk utility.

Silent uninstalls¶

A silent removal runs without any dialog boxes to show the user that the removal is running. All products use the same command line and the same installer file for silent updates:

Note

You must include the braces in the command line. An MSI package name (e.g. AcroRead.msi) can be substituted for the Product Code. For Acrobat products, the Product Code is the GUID.

Browser integration¶

Pass either ReaderBrowserIntegration or AcrobatBrowserIntegration to REMOVE when a product is already deployed and a subsequent deployment requires disabling browser integration. For example:

To re-enable Browser Integration, use ADDLOCAL:

Removing product features¶

Because Acrobat products support MSI technology, it is possible to the use the REMOVE property to uninstall any component as described in the Microsoft documentation: “The value of the REMOVE property is a list of features delimited by commas that are to be removed. The features must be present in the Feature column of the Feature table. Note that if you use REMOVE=ALL on the command line, the installer removes all features having an install level greater than 0. In this case, the installer does not remove features having an install level of 0. For more information about the install level of features see https://msdn.microsoft.com/en-us/library/windows/desktop/aa371194%28v=vs.85%29.aspx.”

Removing any feature via REMOVE that is not specifically identified as a unique component in the user interface during a custom install is not supported. Moreover, some components have subcomponents which don’t appear in the UI, and admins are advised to inspect the installer tables and test their installs prior to deployment.

Adobe Reader Dc Extract Msi

The command line is in the form of:

Where <Package.msi|ProductCode> is either the full path to the original MSI file or the ProductCode of this product.

APTEE example for DC products¶

For standalone Acrobat deployments which not part of a Creative Cloud packager install, download the Adobe Provisioning Toolkit Enterprise Edition (APTEE). The APTEE is a platform-specific executable file:

DC Consumer track¶

For more details, refer to the PRTK documentation.

Serialization; machine online¶

Use following PRTK command to serialize Acrobat with ETLA serial number:

Un-serialization; ETLA serial license; machine online¶

Note

Once an ETLA serial is provided, the LEID changes for unserialized commands. For both tracks, it becomes V7{}AcrobatETLA-12-Win-GM (on Windows) and V7{}AcrobatETLA-12-Mac-GM (on Macintosh). For example, you would use the “ESR” LEID version to initially serialize, and you would use the “ETLA” version to deactivate or perform any other action with the prtk utility.

Type 1 Exception; machine offline¶

The command to generate request code for both Windows and Mac is:

Type1 Exception; machine offline¶

The command to get an accept request code for both Windows and Mac is:

Type 2 Exception; machine offline¶

On Windows and Mac, serialize Acrobat using the prov.xml as follows:

DC Classic track¶

Serialization; machine online¶

Use following PRTK command to serialize Acrobat with ETLA/Perpetual serial number:

Type 1 Exception; ; machine offline¶

Generate a request code with the following (both Win and Mac):

Type1 Exception; machine offline¶

Command to accept request code