Don’t Update Your Chromebook OS, Pulled Update Leaves Behind More Issues

Google Chrome OS 91’s newest replace appears to have created one other difficulty when it was pulled for degrading efficiency. Google launched the model 91.0.4472.147 replace on the finish of June for Chrome OS, however customers reported that it was inflicting efficiency points on their laptops after which it was pulled. However, this appears to have created one other difficulty whereby customers are unable to make use of Linux container which permits set up of Linux functions.

The newest incremental replace for Chrome OS — model 91.0.4472.147 — was released on June 30 with a number of options, safety updates, and bug fixes. A couple of days later, customers began to report efficiency drops as some course of precipitated the CPU to remain at 100% utilization, as noted by Android Police.

Google then pulled the replace from the server, however in doing so it blocked entry to Linux container for Chromebook customers. The Linux container permits Chromebook homeowners to make use of Linux functions.

According to a report by Chrome Unboxed, this difficulty occurred as a result of Linux container first identifies if the most recent model of Chrome OS is put in and prompts to replace to the most recent model if it does not discover it. Since Google pulled the replace from the server, Chromebooks confirmed that they’re on the most recent model — model 91.0.4472.114 — however the Linux container nonetheless thinks there’s an replace out there.

This appears to be a easy oversight, one that may be simply mounted. As of now, there does not appear to be a repair for this difficulty and Google’s hasn’t launched a brand new replace both. Those who’re utilizing Chrome OS model 91.0.4472.114 ought to ideally keep on with it until Google confirms the difficulty with the incremental replace has been mounted. Those who have already got up to date and are experiencing stated points ought to report the bug which is able to deliver extra consideration to it. You can go to the Chrome OS forum or file the bug to submit your suggestions.