About Chromebooks

Chromebook, ChromeOS and Google Chrome browser news

It appears Google has pulled the Chrome OS 86 Stable Channel update from most Chromebooks

About two weeks ago, Google announced the Stable Channel update for Chrome OS 86. While many Chromebooks and Chromeboxes received the update, I didn’t at the time. I still can’t get it on the Acer Chromebook Spin 713 review unit. It turns out, neither can most other devices anymore.

Indeed, the majority of supported devices now show Chrome OS 85 as the most recent Stable Channel version available on the official Chrome OS release matrix site. Here’s a sample showing the current state of some devices:

I know that many of the Chromebooks on the update matrix site did actually show Chrome OS 86 as the most recent Stable Channel version over the past few weeks. If it was available for your device and you upgraded, you still have Chrome OS 86. Folks that didn’t though? They can’t update currently.

Google’s Chrome OS Releases blog doesn’t have any information explaining the situation; at least not at the moment. But it’s clear that Chrome OS 86 has been pulled for many devices. Indeed, the blue shading in the above image showing Chrome OS 86 for the Lenovo Duet Chromebook means that its software version is “newer than most”, per the bottom of the release matrix site.

Without any official indication of what’s going on, I’m wondering if this pullback has to do with the Chrome zero-day exploit reported earlier this week. Apparently, the issue was resolved with an update to both Chrome and Chrome OS as part of version 86. I say apparently, mainly because I don’t have Chrome OS 86. So who knows?

If nothing else, this actually highlights why it makes sense for Google to decouple Chrome and Chrome OS updates, which it has begun to do with the LaCrOS effort.

That work-in-progress project uses the Chrome browser for Linux separately but integrated with Chrome OS. This way if there’s a high priority Chrome issue, Google can fix it and push the update out to Chrome without having to work it into a Chrome OS software update.

I’d be curious if anyone who has installed the Chrome OS 86 Stable Channel update on their device now sees that the prior version is the most recent on the Chrome OS release matrix. Let me know!

author avatar
Kevin C. Tofel

30 thoughts on “It appears Google has pulled the Chrome OS 86 Stable Channel update from most Chromebooks

  1. Yikes must be a big issue, I wish they’d slow updates down there does seem to be few problems lately. One about logging in issues recently.

    1. I know they work hard to stick to the 6-week update schedule, which I can appreciate. And everything in Stable passes through Dev and Beta testing, even though even the best development teams see some issue slip through. That’s why I’m thinking this has to do with something that just “popped up” like the exploit or something but could be a regression from more common situations like you noted. Hopefully, whatever it is becomes resolved soon.

    2. Yup I had that issue last week after an update – has now been resolved by the latest update.

    1. You should be fine then; Google won’t downgrade you. According to the release matrix, anyone with a Samsung Chromebook Pro won’t get 86 at the moment as 85 is the most current version for it. Thanks for confirming!

    2. My asus c523 died yesterday after the second patch. Hard reset doesn’t work. Just paperweight. help?! Gunna open it up & unplug the battery to get a reset? Replace battery? Already bought a Duet to replace it but would like the bigger one

  2. I have the Slate updated to 86.0.4240.77. The only issue I have is I don’t like the icon change for Gmail.

  3. We had 86 on our Asus Flip, but had to stop updates and roll those that had updated to 86 back to 85 as the update broke our DisplayLink docks…

  4. I have the Chrome 86.0.4240.112 installed on Lenovo Thinkpad 13, but on the Chrome Updates page, stable is 85.0.4183.133

  5. My very expensive 16 GB Pixelbook seems to be bricked since the update and Google support told me that all of their attempts to revive it were for not, I love that Pixelbook and I am upset! Nothing shows when I attempt to start it now except that it blinks once, by the power in. No display, nothing… terrible. Longtime Google Chome OS users and Google advocate. WOW this is NOT good.

  6. My Pixel Slate updated right away and now has updated again. I’m on version 86.04240.112
    When I got the 86.04240.077 update, the Pixel Slate shutdown when I stopped using it long enough for it to go into sleep mode. I had to connect the power cable to it before it would turn back on. It did not need a charge and was mostly charged when this happened. It did it a second time the next day. That time I hooked the power to it and it did not come back on like the first time. I didn’t even get an indicator that the power cord was inserted. I disconnected it and registered it and the charge light came on and it powered on. It was at about 80% at the time. Now today I got another update to .112. We will see if it helped. I’m not sure what the update was for.

  7. My Pixel Slate updated right away and now has updated again. I’m on version 86.04240.112
    When I got the 86.04240.077 update, the Pixel Slate shutdown when I stopped using it long enough for it to go into sleep mode. I had to connect the power cable to it before it would turn back on. It did not need a charge and was mostly charged when this happened. It did it a second time the next day. That time I hooked the power to it and it did not come back on like the first time. I didn’t even get an indicator that the power cord was inserted. I disconnected it and reinserted it and the charge light came on and it powered on. It was at about 80% at the time. Now today I got another update to .112. We will see if it helped. I’m not sure what the update was for.

  8. The article needs updating.

    The V86 update was reverted for most of the platforms yesterday to 85.0.4183.133 (ANY version of stabke channel ChromeOS can be loaded by the update process.)

    Only a few platforms now have Version 86.0.4240.112 . For all the rest, most are now pinned at the same
    version. A few are pinned at an earlier one.

  9. I’m running a pixelbook (eve) on stable and I received 86 and still have it but the site says 85 for stable .

  10. The article needs updating.

    The V86 update was reverted for most of the platforms yesterday to 85.0.4183.133 (ANY version of stable channel ChromeOS can be loaded by the update process.)

    Only a few platforms now have Version 86.0.4240.112 shown as the Stable Channel release. . For all the rest, most are now pinned at the same version. A few are pinned at an earlier one.

  11. I have a Chromebook Flip C302 and seems that I can’t update to 86.
    Actually I am on beta 87.

  12. I have 85.3.2 (Home Build) stable-channel 64-bit on Dell Inspiron 1545, after update the Bluetooth and the Android phone is green. Why this two option doesn’t work?

  13. I received 86.0.4240.112 yesterday on my Asus C302 flip, although the matrix is still showing version 85 as the most stable. No problems so far.

  14. Have Version 86.0.4240.112 (Official Build) (64-bit on an ASUS C423 coral that is now pinned at 85.0.4183.133 Stable. Haven’t noticed any problems though.

  15. Version 86.0.4240.112 was waiting for me when I decided to check messages after supper this evening. Asus Chromebook Flip C436FA.

    1. Nice! I’ll have to check the update matrix later as I’m in JavaScript class right now. Maybe 86 is moving forward again!

  16. Acer spin 311 and basic 311 updated last weekend 86.0.4240.122 stable channel octopus, no issues.

    1. Yup, mine got it too yesterday. The release matrix still only shows 9 board families getting the update, so roughly 75% of Chrome OS device boards still don’t have it. Very strange!

  17. Crazy article picture think it is wrong though my kids have a school Chromebook and they have good learning stuff blocked on youtube like when they were learning about Satchel Paige in school my daughter wanted to watch something the teacher had in the meet and it was blocked and it was showing Satchel Paige playing baseball I think it is just wrong though my own voice my own opinion.??‍♀️

Comments are closed.

Scroll to top