Updater-Win (Windows Updates)
These preferences control how the Updater works for the Acrobat family of products 9.2 and 8.1.7 and later. Earlier product versions used the Adobe Update Manager (AUM); for those versions, see AVGeneral.
For an Updater Quick Key, refer to the
Quick Key Library.
This preference category contains the following subfeature(s):
Updater (basic settings)
These preferences turn the Updater on and off.
- There are two bUpdater preferences: One for disabling services plugins and one for other product updates.
- DC Continuous track web and desktop updates are released in tandem to ensure cloud and desktop features
and functionality remain synchronized and compatible. Failure to update desktop components while leaving
services enabled may lead to an unsupported configuration. In other words, set both bUpdater preferences to the same value.
- Updater preferences in the UI have been changed to only show the "Auto" and "Off" options. The Continous
track of Reader does not provide any UI options and the default is "Auto".
- Both bUpdater and Mode can be used to disable the Updater, but only bUpdater removes the update UI.
- Most other updater registry settings have been deprecated and only apply to 11.x and earlier.
Summary table
| Check |
Specifies the default time interval in hours to check for updates. |
|
|
| Data type |
1 (int)
|
| Default |
72 |
| Version # |
DC |
| Lock Path |
Not lockable |
| Summary |
Specifies the default time interval in hours to check for updates. |
| Details |
Interacts with Mode. An example path: HKLM\SOFTWARE\Wow6432Node\Adobe\Adobe ARM\Legacy\Acrobat\{AC76BA86-1033-FFFF-7760-080F0F000400}. Possible values include:
- 72: The default value can be manually changed.
|
| GUI mapping |
Preferences > Updater > Automatically install udpates |
Updater (other settings)
These preferences control when the updater is invoked, how and when a check for updates should be made, and other behaviors. Note that while the Updater is often disabled in enterprise settings, it's also possible to leave it enabled and configure whether updates happen automatically or silently.
For 12.x and later products, the web component updater can be configured independently of the product updater. Most of these preferences are deprecated and do not apply to 12.x and later products.
For an Updater Quick Key (not updated for 12.x and later products), refer to the
Quick Key Library.
See also
bDeclined
in the
ARMUser
key.
Summary table
|
Records the last year the Updater checked for updates; iLastD records the day. |
|
Records the last day the Updater checked for updates; iLastY records the year. |
|
For 10.1 and later, records the last date the Updater checked for Reader updates. |
|
For 10.1 and later, records the last date the Updater checked for Acrobat updates. |
| FirstTimeAppHasRun |
Specifies whether to check for updates the first time the application runs. |
|
|
| Data type |
0 (bool)
|
| Default |
0 |
| Version # |
7.0-9.3.2 and 8.2.2 |
| User Path |
Updater |
| Lock Path |
Not lockable |
| Summary |
Specifies whether to check for updates the first time the application runs. |
| Details |
This is an Adobe Update Manager setting which is deprecated since 9.3.2 and 8.2.2. Possible values include:
- 0: Don't check for updates.
- 1: Do check for updates.
|
| GUI mapping |
N/A |
|
|
| Data type |
1 (int)
|
| Default |
null |
| Version # |
9.2-10.1 |
| Lock Path |
Not lockable |
| Summary |
Records the last year the Updater checked for updates; iLastD records the day. |
| Details |
By default, the Updater performs an update check every 3 days and records the year and day of that check if 1) no updates are found in the Manifest for the user's current product configuration or 2) if updates have been found and successfully installed. Prior to 10.1, the date is recorded in iLastY and iLastD. For 10.1 and later, the date is recorded in tlastT_Reader or tlastT_Acrobat. If 3 days have not passed, the Updater exits. If more than 3 days have elapsed, the Updater looks for updates.
The last and most current value may be written to HKLM or HKCU. Because the Updater doesn't need elevated privileges to initiate a check or download updates, it will write to HKCU. However, on systems where elevated privileges are required, it writes to HKLM. Therefore, when checking and troubleshooting the last check date always verify the values in both locations.
This value is not customizable as the value is written at runtime.
|
| GUI mapping |
N/A |
Updater Logging
The log file is a file generated and appended to at runtime with status, operational, and error information describing what the Updater is doing. This information helps diagnose runtime problems and should be included with any support requests. Logging behaves as follows:
- Logging cannot be disabled.
- Log file size is not limited during an update.
- Log files are appended to each time the Updater runs, there is a 1MB limit on old logs.
- Log files are only backed up once; therefore, there should never be more than two logs on the system.
Summary table
