Followup to this post.

There should be 4 categories of users here;

• (a) Didn't download the update.
• (b) Downloaded the update but didn't restart to install.
• (c) Installed the update and are now stuck on the login screen
• (d) Installed the update and your device is now bootlooping/won't reach the login screen.

Here's what to do if you fall into one of those categories.

(A) You're fine. Don't worry about it. Proceed as normal.

(B) You'll either have to wait for a new update to be pushed (hopefully soon!) and can check by refreshing the page from the guest account, or you can follow the steps I've given for section C.

Alternatively, you could switch to the Beta (or Dev/Canary channels but they would not be recommended) channel for the meantime. You will still have to powerwash if you wish to move back to stable though.

(C) You'll have to do a powerwash and revert to the previous version.

You can powerwash by signing out of any accounts you're logged into (which should be none, if you have this issue) and press Ctrl Alt Shift R twice, then select Powerwash and Revert, and follow the on-screen prompts. More info here.

It may be possible to wait to a new update to be released and then download and install that from guest mode, but I have no evidence of that working. (Now confirmed to be workable by Google).

If guest mode is disabled, then you can update by leaving your Chromebook on the login screen and waiting for auto-update to do its thing. More info in this comment.

(D) Yikes. You got very unlucky and fell into the worst group. Don't worry, it's fixable. I had to do this too!

First of all, you can try powerwashing using the method I used above for the (C) group.

If that doesn't work, then you'll need to follow these instructions. It has you enter Dev Mode, which automatically wipes your device (you will lose ALL YOUR FILES) through a powerwash. This should fix the issues from the update.

Unless you know what dev mode is and are okay remaining there, then remember that you must follow the instructions exactly and EXIT DEV MODE AFTERWARDS.

Hopefully that covers every subset of issues. If you've other questions or issues then leave a comment.

EDIT: Official response and reccomendations from Google.

EVEN BETTER EDIT:

A patch is rolling out, the version number should be 91.0.4472.167.

Group A can now install any new update downloaded.

If you're in group B, you can download the update as you normally would, and restart to install.

If you're in group C, then you can enter Guest Mode, and download and install the update from there.

Due to the bootlooping, group D will still need to follow the instructions listed above.

It would be wise to check the version number available for your device on this table or cros.tech before updating. It should end with **.167. If it doesn't then the patch isn't available for you yet.

^{Source: tracking the version for each board [here](https://cros-updates-serving.appspot.com/})