GoogleUpdate.exe runs continuously after 14 days without an update check even if update check period is > 14 days

[GoogleCodeExporter]

As part of the fallbacks to help ensure the new version of Omaha 
(1.2.183.7) is as reliable as when the core ran continuously, Omaha checks 
whether it has been more than 14 days since the last successful update 
check. If so, it falls back to running continuously as before.

The problem is that it does not take into consideration that there may be a 
legitimate reason for not having a successful update check in the last 14 
days. The legitimate reason is that a user or network administrator have 
set the AutoUpdateCheckPeriodMinutes Policy to > 14 days or 0 (update 
checks disabled).

Reproduction Steps:
1. Install Omaha
2. Apply Group Policy to disable update checks using GoogleUpdate.adm in Group 
Policy Editor.
3. Move the clock ahead 15 days.
4. Run the core scheduled task

Other variations:
 * Set the update check period to 20 days in step 2 instead of disabling 
updates checks.
 * Swap steps 1 and 2.

Expected Result:
The GoogleUpdate.exe /c process exits.

Original issue reported on code.google.com by ddor...@google.com on 17 Jul 2009 at 5:46

[GoogleCodeExporter]

The workaround for AutoUpdateCheckPeriodMinutes > 14 days is to set to less 
than 14 days.

Workaround options for update checks disabled (AutoUpdateCheckPeriodMinutes == 
0) include:
 * Checking for updates once every 14 days.
 * Enabling update checks but setting the default update behavior to manual only. This has essentially the 
same effect in disabling automatic silent updates. 
 * Update the LastChecked value in Software\Google\Update (in the HKLM and/or HKCU hive) to the current 
"Unix time".

Note: If a user has disabled update checks, he or she may not have received the 
version that does not run 
continuously anyway.

Original comment by ddor...@google.com on 18 Jul 2009 at 2:17

[GoogleCodeExporter]

Original comment by ryanmyers@google.com on 19 Aug 2011 at 7:43

• Changed state: Fixed