This section describes a few of the many available customimzation options. Refer to the Wizard user interface and the Preference Reference for more options.

• Adobe Acrobat Reader Dc 19.012
• Adobe Acrobat Dc Download Windows 10
• Adobe Acrobat Reader Dc 19.012 Download
• Adobe Acrobat Dc 19.008 Download

Adobe Acrobat DC is a Shareware software in the category Miscellaneous developed by Adobe Systems Incorporated. It was checked for updates 7,257 times by the users of our client application UpdateStar during the last month. The latest version of Adobe Acrobat DC is 20.013.20066, released on. Acrobat Reader DC is connected to Adobe Document Cloud, so you can work with your PDFs anywhere. You can even access and store files in Box, Dropbox, Google Drive, or Microsoft OneDrive. Say hello to easy file access. Discover all the things your PDF can do. Adobe Acrobat DC helps you keep business moving. Convert, edit, share, and sign PDFs. Explore all the features and tools below.

See also:

Note

Macintosh users should refer to the Admin Guide for Mac. While most examples are Windows-based, Mac supports almost all of the same configurations.

Tools and tool set configuration¶

Tools appear in two main areas: The Tools tab (sometimes called the “Tools Center”), and in shortcuts in the right hand tools pane. You can configure both via the following options:

• User interface: Configure new tools as shown in the screen below.

• Wizard: In the Tools pane, check Disable Apps in Tools tab.

• Registry: Set a FeatureLockdown preference that maps to the tool’s AppID. For examples, see the Preference Reference.

Use this feature to standardize task-specific tool views, reduce training costs, and improve employee efficiency by grouping related tools into a common view. This feature allows:

• Creating or import custom tool sets.

• Switching between different tool sets.

• Creating and managing tool sets across the enterprise via the Wizard or .aaui files.

Tool configuration files¶

Tool set files reside in these locations:

• A local user directory (full access): Files which are stored and imported by the current user are placed in the default current user’s directory. For example: C:Users<username>AppDataRoamingAdobeAcrobat<version>UICustomization<anyname>.aaui

• A local, product directory (read only): Files in this directory are visible to any user on the machine. For example: C:ProgramFiles(x86)AdobeAcrobat<version>AcrobatUICustomization<language><anyname>.aaui

You can find a list of tools and their available properties in the .aapp configuration files at %installdir%(productname)AcroApp(languageID). While it is possible to modify these files and leverage their rich configuration options, this technique is not officially supported since such options cannot be tested by Adobe.

Note

If you’re customizing shortcuts in the right hand pane, you can determine the a(index) value to use for cDisabled and cFavorites by looking in the .aapp file. For example, the Create PDF tool is named CreatePDFApp.

Custom tools¶

Note also that custom entries for 3rd party plugins added post deployment are overwritten on the next product update. To assure that your settings remain in place, add them via the Customization Wizard during the initial install. For details, see https://www.adobe.com/devnet-docs/acrobatetk/tools/Wizard/tools.html.

Example tool set list¶

• AccessibilityApp: Create and verify PDF files to meet accessibility standards for people with disabilities

• ActionsApp: Use guided Actions to complete PDF tasks quickly and standardize routine tasks

• CertificatesApp: Digitally sign or certify documents and validate authenticity

• CollectSignaturesApp: Get signatures from others and track results

• CombineApp: Combine and arrange files into a single PDF

• CommentApp: Add comments with highlights, sticky notes, and mark-up tools

• CompareApp: Compare and highlight the differences between two versions of a PDF

• CreateCustomUIApp: Create a customized collection of Acrobat features and share with others

• CreatePDFApp: Create a PDF from any format

• DeveloperApp: Enhance PDF forms and connect to databases with JavaScript

• EditPDFApp: Edit text and images in PDF files

• ExportPDFApp: Convert PDFs to Word, Excel, PowerPoint and more

• FillSignApp: Fill and sign documents and forms electronically

• FormsApp: Quickly convert Word, Excel or scanned forms into PDF forms

• IndexApp: Index PDF files to speed search across document collections

• MeasureApp: Measure distance, area, and perimeter of objects

• OptimizePDFApp: Reduce PDF file size, enable fast web view, control image and font options

• PagesApp: Delete, insert, extract, or rotate pages

• PaperToPDFApp: Turn scans or photos of paper documents into searchable PDFs with selectable text

• PrintProductionApp: Preview, preflight, correct, and prepare PDF files for high-end print production

• ProtectApp: Prevent others from copying, printing & editing the information in PDFs

• RedactApp: Permanently delete sensitive text, graphics, or hidden data

• ReviewApp: Automatically collect comments from reviewers in a single PDF

• RichMediaApp: Add audio, video, and interactive objects

• StampApp: Add stamps such as ‘approved’ or ‘draft’

• StandardsApp: Create PDF/A, PDF/E, or PDF/X files to comply with ISO standards

• SendAppFull: Send documents, track views and downloads

Preferences Synchronization (DC)¶

When preferences synchronization is enabled (the default), desktop preferences sync across machines where Acrobat and Reader are installed and when the user is signed in with an Adobe ID. This feature allows users to leverage their customizations and streamlined workflows on any machine. Syncing is controlled by the preference:

• bTogglePrefsSync disables preference synchronization across devices. This new feature which synchronizes desktop preferences across machines with Acrobat and Reader on which the user is signed in with an Adobe ID.

Corporate fonts & printing¶

You can set printing options via joboptions files. This example shows how to set corporate fonts.

1. Open the PDFMaker’s settings panel (method varies by the software product you are using to access it.

2. Choose Advanced Settings.

3. Add your font to the Always Embed list.

4. Save the settings as a new joboptions file.

5. Distribute the file:

   • Predeployment: Use the Customization Wizard’s distiller feature: http://www.adobe.com/devnet-docs/acrobatetk/tools/Wizard/distiller.html

   • Post deployment: Distribute the file to C:Users<username>AppDataRoamingAdobeAdobe PDFSettings and set the default joboptions file to use for the PDF printer and Distiller in the Registry. You will need to set the JobOptions registry entry for each PDFMaker used by specific software as well as for Distiller. For example:

Browser integration¶

Acrobat and Reader ship with browser plugins that enable viewing and creating PDF files in a browser. However, behavior as well as customization options vary across browsers.

Note

For manual browser configuration details, see http://www.adobe.com/go/pdfinbrowser.

Internet Explorer add ins¶

Disable the IE PDF viewer add-in via one of the methods below.

For more detail provided by Microsoft, see:

IE config on the command line¶

You can use the command line property DISABLE_BROWSER _INTEGRATION to prevent the installation of (or uninstall) the PDF Viewer ActiveX control.

IE config via the registry¶

Create the following preference if it does not exist, and set its value to 1.

Chrome PDF viewer extensions¶

Registry configuration options for Chrome include:

Disable the Chrome PDF viewer

Disable the first time startup screens that prompt for the Chrome extension install

Note

For Chrome details about the end user experience and associated UI, see https://helpx.adobe.com/acrobat/kb/open-in-acrobat-reader-from-chrome.html

PDF Maker extensions¶

When installing Acrobat, block the installation of PDFMaker’s browser extensions for Firefox and Chrome with the Wizard’s Features panel:

WebMail¶

Features include support for:

• Sending PDFs as email attachments using any mail account that supports SMTP/IMAP protocols. In addition to existing desktop email clients, users can now configure these mail accounts by providing User Name, Password, IMAP and SMTP details.

• Gmail and Yahoo mail accounts (Yahoo mail accounts that end with yahoo.co.jp are unsupported).

• Using Webmail in various Acrobat workflows like Shared Reviews and Forms Distribution. Users can send emails for inviting participants to a Shared Review or distribute PDF forms using the above-mentioned Webmail or other mail accounts. Users can also retrieve their contacts list while composing the mail (Gmail only).

For configuration details, see the Preference Reference or the Wizard Guide.

AATL and EUTL certificate download¶

As part of the Adobe Acrobat Trust List program, Adobe periodically pushes vetted trust anchors (certificates) for use in digital signature workflows. In the Wizard, use the Load trusted root certificates from Adobe drop down list to specify how trusted root certificates are loaded:

• Enable & Ask before installing

• Enable & Install silently

• Disable

Alternatively, set this preferences manually:

Custom file deployment¶

Custom files are one of the primary ways an enterprise can improve business efficiency and lower the Acrobat’s total cost of ownership. This feature is often under utilized, and workflow owners may find it beneficial to review the list below as well as the directories under the product’s root install location. Some of the customizable files include:

• Files that improve workflow efficiency such as those for Actions, combining files, eEnvelopes, Quickbooks templates, forms templates, etc.

• Files that customize application behavior such as JavaScripts and plugins.

• Digital signature files: digital IDs, trusted identities, LDAP server list, custom signature handlers, certificate revocation lists, etc.

• Printing and Distiller files.

• Document backgrounds, headers, footers, watermarks, stamps.

• Document security files, redaction codes, custom security handlers, etc.

• Multimedia skins, navigators, preflight, color swatches, and many more.

Deployment options¶

IT can deploy custom files before or after product installation.

Deploy files with initial installation

Adobe Acrobat Reader Dc 19.012

Prior to product deployment, IT typically uses the Customization Wizard to add files to any requisite directory or to set configure the registry to scan custom, shared directories. To do so:

1. Use the Wizard’s Files and Folders feature to add files to the requisite locations.

2. Save the modified installer and deploy normally.

Deploy files using Group Policy Objects

Admins that use GPO and Active Directory deployments can use their standard methodologies for deploying files and custom registry settings. At a high level, the steps include:

1. Do one of the following:

   • Create a Group Policy which runs a file copy script at system log on or log off or at a scheduled time.

   • Place the files on the target machines via UserConfigurationPreferencesWindowsSettingsFiles or UserConfigurationPreferencesWindowsSettingsFolder.

2. Verify the files are copied to the standard product or user directory so that Acrobat can find the files.

Platform considerations

Most files are applicable to both Windows and Macintosh. Except for the root path, file locations are identical under the product install directories. Where registry or plist preferences provide file-related configuration options, corresponding registry preferences can typically be used on Macintosh by specifying equivalent plist settings in /Library/Preferences/com.adobe.Acrobat.

Refer to the Preference Reference for registry and plist details.

Plug-ins¶

Many organizations use plug-ins to customize workflows for particular needs. The Customization Wizard allows you to specify custom plug-ins for automatic installation. You can use plug-ins from third-party suppliers or develop your own using the Acrobat Software Developers Kit (SDK). For more information, see the Acrobat Developer Center: http://www.adobe.com/devnet/acrobat/.

JavaScripts¶

JavaScript can be used to add and remove items from menus, automate Actions, and perform an almost limitless variety of other tasks that can improved workflow efficiency. You can use scripts from third-party suppliers or develop your own using the Acrobat Software Developers Kit (SDK). For more information, see the Acrobat Developer Center: http://www.adobe.com/devnet/acrobat/.

10.1.1 introduced changes that affect the use of global variables and user scripts. If you are migrating to a newer version, refer to the Application Security Guide for details.

Custom Actions (macros)¶

Actions provide a way to reduce repetition, automate common tasks, and enable batch processing on one or more PDFs. Actions are similar to macros in other popular software applications and lower Acrobat’s total cost of ownership by increasing business efficiency. They also allow organizations standardize document preparation, minimize errors, reduce training costs, and improve employee efficiency by combining repetitive multi-steps tasks into guided Actions. Actions provide a way for the enterprise to:

• Improve compliance by guiding end users through a set of tasks ensuring that no step is missed.

• Simplify and speed up document preparation by optimizing the user experience.

• Centrally distribute and update Actions.

• Increase value and flexibility by integrating guided Actions with local and hosted repositories.

Integration with other products¶

Actions are integrated with PDFMakers so that they can be invoked from other applications. For example, when saving a file as a PDF in Microsoft Word, the PDF tool bar now displays a Create PDF and Run Action button. The drop down list of Actions show all the available Actions that the product can find. The list is populated from these directories:

• The default Actions user directory.

• The default Actions product directory.

• Any custom directory IT has configured the product to scan for action files.

Action file locations¶

Action files can be stored in three locations:

• A local user directory (full access): Actions which are stored and imported by the current user are placed in the default current user’s directory. For example: C:Users<username>AppDataRoamingAdobeAcrobat<version>SequencesMyAction.sequ.

• A local, product directory (read only): Files in this directory are visible to any user on the machine. For example: C:ProgramFiles(x86)AdobeAcrobat<version>AcrobatSequences<language>MyAction.sequ.

• A shared directory (read only): Custom Actions that are created for and shared across the enterprise can reside in any location visible by the product. Deployment should include configuring the product via registry preferences to look for the files that reside in any non-default location.

Shared directory configuration¶

Deploy custom Actions before or after product deployment. After creating custom Actions as described in the Help documentation, configure Acrobat to read action files from one or more shared folders in addition to the installed Sequences folder and the user-level Sequences folder.

To do so:

1. Deploy the action files to some shared location.

2. Use GPO or some other method to push new registry settings across your organization that enable the product to scan the custom action directories. To specify directories that should be scanned for action files, configure the registry as follows:

3. Navigate to [HKEY_LOCAL_MACHINESOFTWAREPoliciesAdobeAdobeAcrobat<version>FeatureLockDowncWorkflowcBaseFolders].

4. Create new keys under cBaseFolders. The names of the keys must follow the sequence c0, c1, c2, etc.

5. Create two REG_SZ values according to the specification in the table below.

Registry setting for directories to scan for Actions

Preferences format for caching action information

The following preferences are product-generated and are described for informational purposes only.

For each action that Acrobat finds when it scans the standard and administrator-deployed action directories, the following values are cached under the [HKEY_CURRENT_USERSoftwareAdobeAdobeAcrobat<version>WorkflowcRegistered] key.

Note

Although you can add and update such cached action information by hand, it is not necessary nor advisable. Acrobat can overwrite the information at any time.

Offline Help access¶

The Reader Help system is only available online. If the product does not have online access, configure installs to point to a local version on your Intranet.

To configure local access to Help:

1. Download the Help in PDF format.

2. Install it in some accessible location.

3. Place the JavaScript in in the JavaScripts directory of each installed client. For example, (C:ProgramFilesAdobeReader<version>ReaderJavascripts). This script replaces the existing Help link with your custom link.

Note

The easiest way to place this file prior to deployment is by using the Customization Wizard’s Files and Folders feature. The Wizard allows you to create an MST file that will modify the installer with any of your customizations.

Help menu JavaScript

Accessing Help behind a proxy¶

The online help system can be made accessible when users are behind an authenticating proxy by setting the following preferences:

• 32-bit: [HKLMSOFTWAREAdobe<productname><version>FeatureState]'3179427'=dword:00000001

• 64-bit: [HKLMSOFTWAREAdobe<productname><version>FeatureState]'3179427'=dword:00000001

EMF and XPS conversion to PDF¶

The December 2018 Acrobat release disabled XPS and EMF file conversion to PDF.

At Adobe, we build security into our products and we implement numerous security processes and controls to help us comply with industry-accepted standards, regulations and certifications. Some examples of overall security improvements specific to Acrobat and Reader include: sandboxing (Protected Mode and Protected View), fuzzing high value targets like the broker process, finding memory corruption bugs via ASAN/GFlags, and running continuous static analysis on the codebase. Additionally, as an added security measure, where we see features with low usage, like XPS and/or EMF to PDF conversion, we disable these features. However, if you trust the document origin, you can enable the feature by creating and setting the following preferences:

Customization Wizard overview¶

The Adobe Customization Wizard tunes the Acrobat and Reader installer prior to mass deployments. The Wizard is a free utility designed to help IT professionals take greater control of enterprise-wide deployments.

Download the Wizard to:

• Modify the installer via a transform file (MST file) without altering the original download.

• Optimize installer and installation workflow by including silent installation, pre-serialization, reboot, multilingual, and custom setup choices, including suppressing the EULA, registration prompts, and the Getting Started window.

• Customize application preferences such as collaboration, security settings, Acrobat.com integration, printing, and most other features.

• Leverage existing installations by drag and dropping registry settings and files from existing installed applications.

• Prevent users from modifying certain preferences by locking them.

• Feature configuration-Registry: Install and configure the application to suit your environment and the use the Wizard to leverage you changes. Many application preferences and directories do not exist until the code is exercised from an installed application. While you could build the paths and add the values manually, simply configuring an installed application and using it as a template does most of the work for you.

• Files and Folders: Many template files won’t exist unless you have installed and configured the application. For example, the easiest way to create a directory server file is via the application’s GUI. Use the Wizard to add these files to the installer.

Although many tools such as Orca and Admin Studio can be used to customize Microsoft transform (MST) files, Adobe only supports the Adobe Customization Wizard.

A typical workflow which uses an existing reference install could include the following:

1. Configure the application via its user interface. In particular, go through the menus under Edit > Preferences. Product UI configuration provides a simple way to configure features.

2. Use the Wizard’s Registry feature to drag and drop the configured template registry to the installer.

3. Use the Wizard UI to configure application preferences not already configured manually.

4. Lock down features so that settings can not be changed by end users: You can use the Wizard’s UI or the manually set lockable preferences.

5. Use the Wizard’s Files and Folders feature to drag and drop your enterprise files to the installer.

6. Save the installer changes to an MST file and install the customized product.

7. Use MSI and Adobe properties to further modify the install during deployment.

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

Issues and errors¶

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: http://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.

Adobe Acrobat Dc Download Windows 10

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 http://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.

Adobe Acrobat Reader Dc 19.012 Download

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 http://forums.adobe.com/message/6106294#6106294.

Installation FAQs¶

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

Adobe Acrobat Dc 19.008 Download

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 http://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 Suite 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 http://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?