The Beta channel has been updated to 61.0.3163.51 (Platform version: 9765.31.0 ) for most Chrome OS devices(*). This build contains a number of bug fixes, security updates and feature enhancements. Systems will be receiving updates over the next several days.

I guess I'm more ignorant then I thought, I was hoping to moveebooks and/or mp3s from acer r11 ( beta channel m61) sd card to android storage so thatI can read or play this data with various android apps.

Black screen after updated Toshiba chromebook2 ( PLM02E-00K004N5 ), same problem as reported in dev channel about a month ago. Was able to fix the problem by connect external monitor and than switching to the stable channel.

I have Acer Chromebook 14 CB3-431 and playstore is working very well..I dont know why but for me it's working even better when you make a powerwash after updating...But beta still don't have same features as the Dev channel..But anyway it's working and we're going somewhere..So it did come even as some people told me it would never happen..Thanks.

Yup -- this update is problematic on the Toshiba Chromebook 2 "Swanky." The primary device screen goes black on boot after the update, and one either has to perform a recovery, or plug it into a secondary display and revert to the stable channel.

It's a little disconcerting that this bug made it from the dev channel to the beta channel without getting squashed, if that's indeed what happened.

I can confirm the same black screen problem after update for my Toshiba Chromebook 2. Occurred about a month ago while on the developer channel and two days ago while on the beta channel. Used USB Recovery Stick to recover to stable channel and chromebook is running fine on that channel. Tried a test of changing to beta channel and also developer channel, both result in black screen upon reboot.

For those who had their Toshiba "Swanky" machines hosed: If you have an HDMI cable and another display, you don't have to do a recovery. Hook up you TCB2 2014 to a monitor, boot up, then press shift + fullscreen. You can then drop back to the stable channel -- but before you do that, the devs would like you to submit a report from the affected system.

I am on Samsung Chromebook Plus. I was on the dev channel until recently. When the version with the new log in screen came up, I started getting freezes and random reboots, in particular when using Android apps. Reverted to beta channel because it was frequent enough to be annoying. Now the new log in screen is on the beta chan, and the same problems are showing up.

I'm with the Toshiba group that had a blank screen after this update. BUT THANK YOU to all of you who commented. Glad I could resolve the issue by plugging in my tv as an external monitor and going back to stable.

Same here. I am lucky that my Toshiba Chromebook 2 did not go directly into black screen, but still my screen have gone crazy from time to time. Tabs and windows overlap one another and jump both horizontally and vertically so the only thing I can do is to reboot. But the problem comes back again and again. I thought it was just my chromebook, but it seems that everyone using the same model has problems with this update. Fix it please. This is seriously slowing down my work progress.

On my toshiba cb2 (swanky, n2840) the screen still works but is fixed on maximum brightness for all positions on the brightness slider except the first, where the screen goes blank. If I leave it in that position for too long, or if I allow the screen to turn off from inactivity then I cannot get the screen back on and have to power cycle or connect an external cable.

Same beta channel issue on my Toshiba Chromebook 2 as others, reverted to Stable Channel and ran fine. Today I decided to try the latest Developer Channel Build (Version 62.0.3193.0 (Official Build) dev (64-bit)) from August 22nd and I can report it works fine on my Chromebook.

My Chromebook is Acer CB3-131-C3SZ. After update beta Version 61.0.3163.51 the screen runs wildly-each tab suddenly gets frenzied and falls apart like a random pattern of block patterns after some minutes of use.Then Reboot, but the problem returns again!!

I would suggest to avoid playing with the brightness controls on the beta channel as I couldn't get my screen to work after turning it off. I was saved by the fact that my dev channel update was started in the background before I started fiddling, all good now.