Now, the company’s help pages contained the following: “Warning: To prevent abuse of this policy, if a device is not joined to an Active Directory domain, and if this policy has been set to 0 or to a value greater than 77 hours, this setting will not be honored and replaced by 77 hours after August 2014. It was no longer sufficient to set the “Auto-Update Check Period Override” to 0, as it had been. It turns out that Google had made changes to its own update process.
Last August, I logged into my system and found that Chrome had been updated. Luckily, I have Windows 7 Pro, so I disabled the update process and went on my way. By default, that restricts auto-update control only to Windows 7 or Windows 8 Professional. Google felt this was insecure, however, and mandated that you have to be able to edit group policies in Windows in order to make these changes. Originally, you could disable Chrome’s Auto-Update via registry values. Unfortunately, Chrome’s auto-update policy is deliberately difficult to use. In the end, I downloaded a beta version of Chromium.Īfter my experience with Chrome 32, I wanted to make certain I wasn’t caught by surprise again.
I found a few downloads for the early version of Chrome, but all I wanted to do was step back to version 31 - and at the time, I couldn’t find it anywhere. FileHippo has a notice that states Google’s policies disallow the site from offering downloads. File aggregation sites like and FileHippo don’t archive Chrome. That’s when I discovered that Google monitors the Internet and forbids anyone from offering old versions of Chrome to download.
0 kommentar(er)
