Another major Chrome OS update bug is leaving users locked out of Chromebooks | #firefox | #chrome | #microsoftedge

Source: Ara Wagoner / Android Central

Somehow, a major bug has slipped through three experimental channels and made its way into a Chrome OS stable channel — AKA the channel that the vast, vast majority of Chromebook owners are using. This bug is in Chrome OS 91.0.4472.165, and it is not allowing users to log back into their Chromebooks after the update, and in some cases, their laptop is bootlooping so they cannot access the lock screen. In these cases, you’ll need to create a Chromebook Recovery USB stick using the Chromebook Recovery Utility and use that to re-image your Chromebook.

If the update has downloaded but installation has not finished, do not shut down your Chromebook. The update will install on your next reboot or system shutdown.

VPN Deals: Lifetime license for $16, monthly plans at $1 & more

Google seems to be aware of the situation and should be working on a fix soon, but the update hasn’t been pulled yet, it seems, so don’t go to the About Chrome OS screen, do not check for updates, and do not shut down your Chromebook if you can help it.

Users who unfortunately got the update first are currently locked out of their machines, at least until they Powerwash them. Once impacted users factory reset their Chromebook, they can set it back up and get back in, but keep in mind this is a factory reset and will erase all local data and the Linux program data. If you can wait for a fix, you might be able to wait and then update your Chromebook from Guest Mode, but we have no timetable for a patch.

We’re reaching out to Google to ask when they might have a timeline for the fix and how this has happened twice in such a short amount of time. We’ll update this story as things progress.

var fbAsyncInitOrg = window.fbAsyncInit; window.fbAsyncInit = function() { if(typeof(fbAsyncInitOrg)=='function') fbAsyncInitOrg(); FB.init({ appId: "291830964262722", xfbml: true, version : 'v2.7' });

FB.Event.subscribe('xfbml.ready', function(msg) { // Log all the ready events so we can deal with them later var events = fbroot.data('ready-events'); if( typeof(events) === 'undefined') events = []; events.push(msg); fbroot.data('ready-events',events); });

var fbroot = $('#fb-root').trigger('facebook:init'); };


Original Source by [author_name]

Leave a Reply

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

5 + = six