After pulling it, Google pushes the Chrome OS 86 Stable Channel to Chromebooks again

Earlier this week, I reported that the latest Chrome OS 86 Stable Channel update stopped flowing to Chromebooks. Indeed, even two weeks after news of the software update was announced, many Chromebooks weren’t seeing the new software. I’ve been keeping an eye on the update matrix and it now shows the Chrome OS 86 Stable Channel update is once again available for nearly all Chromebooks and Chromeboxes.

A few readers have commented in the past 24 to 36 hours that their devices were now getting updated. And my own Acer Chromebook Spin 13 finally got upgraded to the Chrome OS 86 Stable Channel late last night.

So even though there’s been no official communication from Google on this subject, I think it’s safe to say the update process is moving forward. Bear in mind that Google typically rolls out Chrome OS software over several days, so you still might have to wait for just a bit.

Now the question is: Why was Chrome OS 86 released, halted and then re-released?

We’ll never know unless Google decides to share that information. However, over the past few days, I did see several Chrome OS 86 bugs reported, many of which I’d consider “high priority”. Some folks were experiencing major Family Link issues, others lost all ability to print and still others experienced Android app crashes. And those were just the bugs I could publicly find.

Regardless of the reason, I’m looking forward to using some of the new Chrome OS 86 features that I had tested previously in the Dev and Beta channels. Hop over here for a list of what’s new in Chrome OS 86 while you wait for that update!

2 thoughts on “After pulling it, Google pushes the Chrome OS 86 Stable Channel to Chromebooks again

  • October 28, 2020 at 8:54 pm
    Permalink

    To me, v86 has very questionable quality. It won’t let me turn off the settings switch called, “Allow windows to span displays.” This makes using my attached display with my built-in display nearly unbearable. What a mess.

    Reply
    • November 1, 2020 at 2:14 pm
      Permalink

      My bad. I had forgotten that I had set the span-displays flag. Doh!

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.