Chrome OS Build 60, the latest version of the platform, is now rolling out to most devices. Build 60.0.3112.80 (Platform version: 9592.71.0) contains a number of bug fixes, improvements and other enhancements to device. The release of the Chrome OS update to Build 60 comes after updates to the Chrome browser and Chrome for Android apps over the course of the past week.
There is a rather extensive list of device that will not be seeing this update, at least not yet.
- Google Chromebook Pixel
- ASUS Chromebook Flip C302
- HP Chromebook 13 G1
- Samsung Chromebook Plus
- Dell Chromebook 13 3380
- Chromebook 14 for work (CP5-471)
- Acer Chromebook R13 (CB5-312T)
- Lenovo N23 Yoga/Flex 11 Chromebook
- Samsung Chromebook 2 11″
- AOpen Chromebox Mini
- AOpen Chromebase Mini
- AOpen Chromebox Commercial
- Lenovo Thinkpad 11e Chromebook
- Acer Chromebook 15 (CB3-532)
- Samsung Chromebook 3
- Acer Chromebook R11
- Chromebook 11 Model 3180
- ASUS Chromebook C202SA
The devices on the list not getting the update are generally those which are able to run Android apps natively (i.e. in the Stable channel) and are on a slightly different train. If your Chrome OS device is not on the above list, the easiest way to get the update is to open up the browser and type chrome://help and check for the update. I’ve already updated my Acer Chromebook 14 to this new build and it took about 5 minutes to download and install.
As for what is fixed or added in this updated version of Chrome OS, there are a handful of things.
-
Improved support for Auto updates over cellular networks
-
Location and Timezone selection enhancements using cell tower information
-
GPU Rasterization support
-
Device wide support for EAP-TLS Networks
There is also a critical security flaw fix in the update
- [740776] Critical CVE-2017-9417: Fix BroadPwn security bug.
Google is still in the process of bringing Android app support to a number of devices and while the hope was that by the time we got to Build 60, the majority of them would have the support, it does not appear to be the case.
The devices not getting the 60 release with the rest generally were NOT ones with “native” Android support. They were models using older platforms, mostly released for manufacturing in 2015.