On September 10, Google released a new version of Chrome that includes fifty-two fixes for security vulnerabilities. The full change log lists almost seventeen thousand changes in all, so I’m going to assume that there’s nothing in there worth mentioning, aside from the security fixes. Presumably, if Google wanted to highlight any of the changes, they’d be outlined in the official release notes for Chrome 77.0.3865.75.
As is often the case with Chrome security vulnerabilities, many of those addressed in Chrome 77.0.3865.75 were discovered and reported by independent security researchers. There’s a list of those fine folks in the release notes, along with the rewards they earned from Google for their work.
To update Chrome, click its ‘three dots’ menu and navigate to
About Google Chrome. If there’s a newer version than the one you’re running, you should see an update link.
The latest version of Chrome (Google’s browser, not the open source Chromium project upon which it is based) is 76.0.3809.132. The new version provides fixes for three security vulnerabilities, some of which were discovered and reported by independent researchers.
If you love digging into dry technical details, the Chrome change log is for you. The new version’s log is at least brief. A cursory scan shows nothing particularly interesting.
Chrome usually updates itself, albeit somewhat mysteriously, since Google’s update schedule is unclear and possibly varies widely from update to update. Google’s update mechanisms also occasionally stop working — silently. It’s a good idea to check which version you’re running and install a new version if it’s offered on the
About Google Chrome dialog (click the ‘three dot’ menu button at the top right of Chrome’s user interface).
Google released another version of Chrome a few days ago, and it includes fixes for four security vulnerabilities. The change log is mercifully brief, but there’s also not much there of interest. The announcement for Chrome 76.0.3809.100 gives credit to non-Google security researchers for discovering two of the vulnerabilities.
Check your version of Chrome by navigating its ‘three dot’ menu to
About Google Chrome. If an update is available, you can install it from there.
On Tuesday, Google released another new version of Chrome: 76.0.3809.87. The announcement highlights sixteen vulnerabilities, discovered by security researchers not employed by Google, that are addressed in the new version. There are forty-three security fixes in all.
Google has chosen not to highlight any other changes in Chrome 76.0.3809.87, so if you want to know whether anything important changed, your only option is to read the thirteen thousand, five hundred and forty-three entries in the full change log. Good luck with that.
Chrome, uh, finds a way to keep itself updated, and fighting against that is a never-ending and ultimately pointless exercise. What you can do is check your version and thereby trigger an immediate update, by navigating Chrome’s ‘three vertical dots’ menu (at the top right) to
About Google Chrome. That way you don’t have to wait for Chrome to update itself, which happens “over the coming days/weeks” according to Google.
Two security fixes for Chrome were released earlier this week in the form of Chrome version 75.0.3770.142.
The change log for Chrome 75.0.3770.142 lists one hundred and twenty-eight changes in all, but other than the two fixes for security vulnerabilities, none of them are particularly interesting.
By default, Chrome will update itself in the days following a new release. You can encourage it by navigating its ‘three dot’ menu to
About Google Chrome, where an option to update will be shown if one is available.
The latest Chrome release features a fix for one security vulnerability. There are about forty-five actual changes listed in the full change log, none of which are particularly noteworthy.
There’s not much of interest in the release announcement for Chrome 75.0.3770.90, although it does point out that the vulnerability was discovered and reported by a non-Google researcher.
Unless you’ve gone to the trouble of disabling Google’s persistent automatic update processes, your installation of Chrome will likely update itself over the next few days.
You can check your version and trigger any pending updates by navigating Chrome’s menu (the ‘three-vertical-dots’ button at the top right) to
About Google Chrome.
A new version of Chrome includes fixes for forty-two security vulnerabilities.
The full log for Chrome 75.0.3770.80 lists over fourteen thousand changes, so good luck reading all that.
Google did not highlight any of the changes in the announcement for Chrome 75.0.3770.80, which only provides this somewhat cryptic message: “Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 75.”
Check your Chrome version by navigating its ‘three vertical dots’ menu icon (at the top right) to
About Google Chrome. If an update is available, it will be offered to you.
A new version of Chrome fixes a single security bug. Chrome 74.0.3729.157 was announced and made available on May 14, so it may have already found its way to your computer by way of Google’s rather insistent update mechanisms.
If you’re not sure which version of Chrome you’re running, click that little ‘three vertical dots’ menu button at the top right, and navigate to
About Google Chrome. Besides showing you the version of your current installation, this will usually prompt Chrome to check for available updates and offer to install a new version.
The latest Chrome browser, version 74.0.3729.131, includes fixes for a pair of security vulnerabilities. Fifty-four changes are listed in the full change log, of which about half are actual changes and not just bookkeeping.
As usual, you can let Chrome update itself on its own mysterious schedule, or trigger an update by navigating its ‘three dots’ menu to
About Google Chrome. There are other ways to obtain the latest version, but that’s the most straightforward.
According to the release announcement, Chrome 74.0.3729.108 fixes thirty-nine security vulnerabilities. The full change log lists almost fourteen thousand changes in all. Good luck absorbing all that information.
Chrome generally keeps itself up to date whether you want it to or not, which is arguably a good thing, given that a lot of malware makes its way onto computers via unpatched security holes in web browsers. You can check which version you’re currently running, and — if an update is available — trigger the update process by navigating Chrome’s ‘three dot’ menu to
About Google Chrome.