Google does not seem to be taking a break from Chrome OS 91. First, we saw that many users reported their devices using a huge amount of CPU after upgrading to 91.0.4472.147. While Google pulled the update shortly afterwards and rolled everyone back to 91.0.4472.114, it managed to lock out Linux apps. Now we see the arrival of 91.0.4772.1

65, and this update introduces a terrible bug that destroys Chromebooks left and right.

A moderator from ChromeOS subreddit recently tipped us off about this new Chrome OS update that locks users out of their Chromebooks. If you receive a notification in the notification area about updating your computer, do not turn off your Chromebook. Chrome OS would otherwise automatically install it on reboot, which means your device gets stuck with the problematic 91.0.4772.165 build.

While Google is aware of the issue and is downloading the update from its servers, the damage has already been done. A redditor reports that two of their Chromebooks no longer accept the login screen password – one of their laptops started booting. Even a powerwash could not save another user’s Asus Chromebook C436, forcing them to use a recovery USB to get them running again. The updated 91.0.4772.165 update seems to have resulted in a significant loss of important files and many people are outraged.

We are not sure how this big mistake went three developer channels and into Stabil, and we hope not many of you will be affected by it. The whole incident highlights Google’s lack of quality control over Chrome OS releases – it’s certainly not a good look for new users planning to use Chrome OS in the long run.