What's covered

The Adobe Acrobat 8.1.1 update corrects issues identified in both 8.1 and 8.0 of Adobe Reader as well as Adobe Acrobat Professional, Standard, and 3D software. Adobe recommends that all Adobe Reader 8, Acrobat 8 Professional, Standard, or 3D users apply this update.

The update can be downloaded from the Adobe website, and will be distributed through the automatic product update system. A full English Adobe Reader version 8.1.1 installer is available from the Adobe Reader page.

Issues addressed by the Acrobat 8.1.1 update

The 8.1.1 Update includes corrections to the following issues:

General

#1613501 Closes a security vulnerability (APSB07-18). This update addresses a potential vulnerability in Adobe Acrobat and Adobe Reader on the Windows platform in conjunction with MS Internet Explorer 7. In order for this vulnerability to be exploited, Internet Explorer 7 must be installed on the computer, but it does not have to be the primary browser.
Root: fixes issue in version 8.1, 8.0. This vulnerability also exists in version 7.0.9 of Adobe Acrobat and Adobe Reader and will be addressed by a separate update. It does not exist in the 6.x code base. A prior work-around for this issue was published as APSA07-04.

#1571809 Corrupt updater preferences will cause Reader 8.1 or Acrobat 8.1 to crash when attempting to check for updates. An older updater library (AdobeUpdater.dll) was not properly deleting corrupted preference files in certain instances. Applies only to Windows, not Mac OS versions.
Root: fixes issue in version 8.1, not present in earlier versions.

#1581323 The FedEx Kinko's menu item is removed. This update will remove the FedEx Kinko's menu button in Adobe Reader 8.1 and the Adobe Acrobat 8.1 Family. This menu item only is present in version 8.1 of these products; versions 8.0 and earlier do not have this entry.
Root: fixes an issue in version 8.1, not present in earlier versions.

#1597907 Custom button(s) do not appear in the toolbar when a PDF opens via the browser plug-in. Corrects the use of the app.addToolButton function when used to add custom buttons via the trusted method to Reader. Symptom may occur only when viewing PDF in a browser.
Root: fixes an issue in Adobe Reader 8.1, not present in earlier versions.

#1572280 Type 3 fonts with missing operators. PDF documents that contain Type 3 fonts with missing operators are non-compliant with the PDF specification. These non-compliant PDF documents are typically generated by third party products. When trying to opening the document, users see an error message, "Cannot extract the embedded font 'F0'. Some characters may not be displayed or printed correctly." PDF documents open correctly in Reader/Acrobat 7.x, but not 8.0 or 8.1. The root cause is Type 3 fonts that do not comply with the PDF specification, which requires either the 'd0' or 'd1' operator in every Type 3 character procedure. In version 7.x, if the offending character was not displayed, the PDF document opened normally. Version 8.0 catches this error even if the character is not displayed. The updated behavior will ignore the missing operator when the character procedure is empty.
Root: fixes an issue in versions 8.0 and 8.1, not present in earlier versions.

Minor translation corrections in several localizations of Adobe Reader 8.

Japanese, Chinese and Korean versions only:

#1574492 Error message when opening a PDF document in Reader 8.1 in a Hanko approval workflow. When users open a rights-enabled PDF in Adobe Reader 8.1 as part of a Hanko-approval workflow, they receive an error message that prevents them from applying Hanko stamps to the document. This affects only the Japanese, Korean and Chinese localizations of Adobe Reader 8.1.
Root: fixes an issue in Adobe Reader 8.1, not present in earlier versions.

Japanese (Windows) only:

#1589257 Acrobat 8.1 crashes when performing OCR text recognition for Japanese text. Users may experience a crash in Acrobat when attempting to recognize text. This occurs if the OCR text recognition language is set to Japanese; other languages will not cause the crash. This does not occur on the Mac OS version of Acrobat 8.1 Professional.
Root: fixes an issue in version 8.1 of the Adobe Acrobat Family (Japanese/Windows only), not present in earlier versions.

#1584040 OCR update for the Japanese version of the Acrobat Family is correctly applied. Updates to the OCR text recognition capabilities of the Acrobat Family are correctly applied, including when running on Windows 2000, Windows Vista, and 64-bit versions of Windows XP.
Root: fixes an issue in version 8.1 of the Adobe Acrobat Family (Japanese/Windows only), not present in earlier versions.

PDF Forms-related issues:

#1567564 Scripts that remove multiple sub-forms could cause a crash. If two or more different instances of different sub-forms are removed by script before Acrobat can refresh the screen, a crash could occur if the application tries to reference the now-deleted sub-forms.
Root: fixes an issue in version 8.1, not present in earlier versions.

#1575734 Drop-down lists in dynamic forms are not visible in Reader 8.1. Dynamic forms with drop-down lists whose font size is set to zero will not display correctly in Reader 8.1; earlier versions will display the drop-down list correctly.
Root: fixes an issue in Adobe Reader 8.1, not present in earlier versions.

#1592222 Acrobat 8.1 may crash when the xfa.host.importData function is used in a custom button on a PDF form. In certain circumstances, a combination of scripting techniques could cause a crash when attempting to import data.
Root: fixes an issue in version 8.1 of the Adobe Acrobat Family, not present in earlier versions.

#1546101 Data selected in a drop-down list is not displayed after the form is submitted. After a form is submitted, prior selections made in drop-down lists are not displayed when a user re-opens the form. Note that the data is retained in the actual PDF file and has been submitted correctly.
Root: fixes an issue in Adobe Reader 8.1, not present in earlier versions.

#1546101 In a PDF form, a click or MouseUp event does not execute for a CheckBox object that is embedded in a table row when Direct/AGM rendering is enabled.
Root: fixes an issue in version 8.1, not present in earlier versions.

#1539165 Changing the data types of some nodes could cause a crash when opening certain PDF forms. In certain instances when input data in a PDF form does not match the data description derived from the XML schema, a crash could occur when the data type of a node is changed to correct to the mismatch. Symptoms that may highlight this issue can include forms generated by Designer 8.1 that may cause Reader, Acrobat and Designer 8.1 to crash when opening the form, and Designer 8.1 could crash with certain XDP-based PDF forms generated from Designer 8.0 and 8.0.5. In some instances, forms created in Designer 7.x may also generate a crash in version 8.1 of Adobe Reader or the Acrobat Family.
Root: fixes an issue in version 8.1 of Adobe Reader and the Adobe Acrobat Family. In addition, Adobe LiveCycle Designer 8.1.1 (which ships as part of the LiveCycle ES Family) includes a correction for form authors related to this issue. Customers that use Designer 8.0.5 or 7.x (bundled with Adobe Acrobat Professional) can upgrade to version 8.1.1 of Designer here. This upgrade includes new features.

#1565403 Error message when re-opening saved dynamic form. If forms saved in Adobe Designer 7.1 and subsequently rights-enabled with ARES were saved as a copy and re-opened with Reader 8.1 or Acrobat 8.1, users would see the error message "The element [min] has violated its allowable number of occurrences." This error did not occur with versions 8.0 or 7.0.x of Adobe Reader or Adobe Acrobat.
Root: fixes an issue in version 8.1, not present earlier versions.

#1564575 Form data submitted from dynamic forms created with Designer 7.x may not be correct when submitted via Reader 8.0 or 8.1. In Reader 8.0 or 8.1, in some instances the XDP data sets in the saved PDF are incorrect. Data entered in the sub form is lost when filled, saved and re-opened with Reader 8 because data was not being saved under the correct node in the data file, causing the data to not populate correctly.
Root: fixes an issue in versions 8.0 and 8.1 of Adobe Reader and the Adobe Acrobat Family.

#1571684 Missing JavaScript error exception. A JavaScript error that should have created a warning to the developer was not flagged as an error prior to version 8.1.1. Specifically, attempting to reference an object via script when the object has already been removed will now throw an exception. The JavaScript object clean up code has been corrected in this update to catch and scripting errors of this type.
Root: fixes an issue in versions 8.0 and 8.1 of Adobe Reader and the Adobe Acrobat Family; not present in earlier versions.

#1573821 Certified forms fail validation due to empty <formstate> packets. Certified-forms that contain empty <formstate> packets will fail certification validation when opened in Reader/Acrobat 8.1. This update addresses the issue in Adobe Reader and Adobe Acrobat. Note that an issue in LiveCycle Forms Server produces <formstate> nodes for any form that has a dropdown list, which in turn could invalidate the certifying signature if there is one.
Root: fixes issue in version 8.1 of Adobe Reader and the Adobe Acrobat Family. In addition, Adobe LiveCycle Designer 8.1.1 (which ships as part of the LiveCycle ES Family) includes a correction for form authors related to this issue. Customers that use Designer 8.0.5 or 7.x (bundled with Adobe Acrobat Professional) can upgrade to version 8.1.1 of Designer here. The server-side issue will be addressed in the future LiveCycle ES 1.5 release.

#1594513 Drop-down list buttons in a PDF Form may not display with Direct/AGM rendering enabled. The height of a drop-down list could be smaller than the threshold to display the button. The threshold for drawing small buttons has been reduced from 6 to 1 point.
Root: fixes an issue in version 8.1 of Adobe Reader and the Adobe Acrobat Family, not present in earlier versions.

#1601373 PDF form floating-point field will not accept decimal point value. In certain instances when an integer-based field precedes a floating-point field in the order of entry, users would not be able to enter the correct value in the floating point numeric field. This update corrects an initialization issue with the input filters.
Root: fixes an issue in version 8.1 of Adobe Reader and the Adobe Acrobat Family, not present in earlier versions.

#1613530 Error message when processing altered XML data. This involves a rare scenario where server-side processing has altered the XML data in a PDF form by removing the xml namespace declarations associated with an empty field. In this situation, Acrobat 8 may generate an error message when trying to process the altered data file.
Root: fixes an issue in version 8.1 of Adobe Reader and the Adobe Acrobat Family.

Products affected

Adobe Community Help