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.
The release announcement for Chrome 73.0.3683.75 links to a list of sixty security issues which are fixed in the new version.
Many of the vulnerabilities addressed in Chrome 73.0.3683.75 were discovered by external security researchers, once again demonstrating the value of Google’s open attitude towards bug submissions.
Although Chrome usually updates itself within a few days of a new release, you can expedite this process by checking for available updates. Do that by navigating Chrome’s three-dot menu (by default at the top right), to
About Google Chrome. This will trigger an update, if one is available.
The latest Chrome browser release is version 72.0.3626.121, and it fixes a security vulnerability for which exploits have been observed ‘in the wild’. So this is an important update.
When I try to look at the full change log using the link provided by Google, I get a blank page. Not sure what’s going on there.
If you use Chrome, it’s almost certainly updating itself on Google’s somewhat mysterious schedule. But you can check your version and initiate an update by navigating its ‘three dot’ menu to
About Google Chrome.
A single security fix prompted the release of Chrome 72.0.3626.96 last week. The full change log for this release lists forty-one changes in all, but most of them are not significant.
Chrome usually updates itself, but on its own mysterious schedule. So if you want to make sure you’re up to date, navigate its menu to
About Google Chrome to see the version you’re running and install any available updates.
There are at least fifty-eight security fixes in the latest Chrome browser, version 72.0.3626.81. Released on January 29, the new version contains more than fourteen thousand changes in all. If you have a few days to kill, you can read the full change log.
Chrome will generally update itself whether you want it to or not, but if you’re not sure, navigate its menu (three dot icon) to
About Google Chrome to see which version you have installed, and trigger an update if one is available.
I’m not sure why Google didn’t see fit to mention any of the changes in this version on the announcement page, but it’s hard to imagine that none of them were at all interesting. Besides listing about thirty of the security fixes, all they’ve done is point to the Chrome blog, which currently doesn’t show any posts related to this new version.
A lone security vulnerability is addressed in the latest Chrome, version 71.0.3578.98. The full change log documents about twenty changes in all.
Chrome keeps itself up to date, mostly whether you want it to or not. I’ve long since stopped fighting Google’s automatic updates on my own computers, partly because those updates never seem to cause problems, which is refreshingly different from Microsoft’s sad history.
On the other hand, Chrome may not get around to updating itself for a while; Chrome release announcements usually include boilerplate text saying that the new version “will roll out over the coming days/weeks.” You can get it up to date right now by clicking its menu button and choosing
About Google Chrome.